Tom Christian's Blog

Here is another issue that a customer had that I thought would be helpful to others.

So a while ago I posted about how to fix the Validation of viewstate MAC failed error.  There is some really exciting news that is coming with Visual Studio 2008 Service Pack 1 and .NET Framework 3.5 Service Pack 1.  One of the improvements that they made for this Service Pack is to help alleviate this issue by doing something similar to the code change recommended on my blog.  So the form fields will be written out at the beginning of the form.

The next service pack is finally available.  If you are using .NET 3.5, or want to use any of the new features that we have been talking about being added in this service pack, I’d strongly recommend you upgrade to this.  You can download it here.

Just wanted to pass along some really interesting labs that I came across the other day.  These labs cover the following topics:

So there is a very good article that came out in the April 2008 issue of the MSDN Magazine, Scaling Strategies for ASP.NET Applications.  The main things in this article are:

So I wanted to get a read on how people design their web sites.  My thinking is that there isn’t much time spent in planning for supportability.  There are a lot of other concerns that take priority, What is more important – Design or Content.

The first time you run !DumpAllExceptions you will see it print out one full exception for each type of exception that is in the dump.  This will include the message and the callstack of the exception.  For example:

A customer has created a web project which references a class library project.  When deployed to the local machine the web/classes all work fine.  When deployed to a ‘shared’ IIS site, the class DLLs exist in the /bin folder, but the web page generates an error: