Web forms makes it really easy to create a simple website, but it is also really difficult to crate a complicated website. These are some of the things you will need to know sooner or later.

Over fifteen years of developing for the web, I've learned some lessons the hard way. There are some things they don't teach you in books and tutorials.

Looking for an inexpensive web hosting company for a ASP.NET (or Classic ASP) website? I have experience with five of the most popular hosting company's shared hosting plans: Hostek, Arvixe, SmarterASP, ASPnix and RDO Servers.

I was really excited when I first found fiverr.com. Here was a site where you could get almost anything done for $5 (US).

This is a list of ASP server side controls that require or do not require to be nested inside of a server form (form runat="server").

Personally I can never remember which of the Request object properties I need to use to get the requested URL or certain parts of the requested URL.

On database-driven websites it is commonplace to execute multiple database queries to generate just one page. For example, on the home page of an ecommerce website you might get a list of categories, a list of banner advertisements to display, a list of featured products, and a list of top selling products. I investigate whether it was more efficient to put these multiple queries into one stored procedure and use the SqlDataReader's Next Result method to get the data all in one go.

If writing database queries in SQL in Classic ASP for SQL Server, rather than using ADO or parameterised queries, you can use these functions to correctly format your data and protect against SQL injection.

If you are using Entity Framework and have received this error message and have been frustrated by not being able to see what the actual problem is in Visual Studio then there is a simple solution.

Developing a secure membership system can be complicated as there are many potential danger areas that you must be aware of. In this post I hope to cover all of the areas you need to think about and plan for.

If you use ASP.NET UpdatePanels, most of the time you want to maintain the window scroll position but there are occasions when you don't want to scroll back to the top or to a specific control.

I often use the standard ASP.NET ValidationSummary to display form validation error messages but often struggle what to write for the Headertext property.

I have put up with a bug in Visual Studio for some time, but recently finally got around to reporting it. I need your vote to get this bug fixed.

Looking at the Google search results, it seems that there has been plenty of demand to share Session values between Classic ASP and ASP.NET. This is usually a result of supporting legacy Classic ASP.NET with new development in ASP.NET.

Review of webSupergoo's ABCPDF.

Solution to the ASP.NET UpdatePanel lost focus on post back issue.