I have been consistently frustrated by this problem and have finally decided to find out what the deal is.  Before VS2005 SP 1 when I would work on a website and remove all compile errors, I could open up another form, and all of a sudden more build errors pop up.  I thought after upgrading to SP1 and going to the web application project, that VS2005 would know where it's bounds are and would compile everything on a build.  This does not seem to be case.  I can still open up aspx files and new build error are popping up.  My understanding is that VS build operations should not be 'compiling' aspx files.  They are set to 'content' not 'compile'.  Can someone explain to me why I am seeing this.  Obviously, I am missing something pretty basic, but others in my shop have the same complaint and no explanation. 

Thanks!!

 Hi,

Can you specify what errors were you getting.

 HTML tag errors.......... <table> can't be inside a <p>.......... tag can not contain uppercase letters........ I know I can turn that off and the pages will not be rendered correctly in some browsers, but I really would like to know what VS is doing.

 Hi,

Please make sure your HTML tags are not violating the HTML Validation Checking in VS 2005.

You can change the validation from Tools->Options->Text Editor->Html->Validation.

For more information, see http://weblogs.asp.net/scottgu/archive/2005/11/23/431350.aspx

Thanks.

 I understand that.  Why does 'building' an application not find all of these errors in a project.  I have to open the page in the editor for VS to flag the errors.

 Hi,

The build of Visual Studio for ASP.NET web application, the code-behind class files and stand-alone class files in the project are compiled into a single assembly, which is placed in the Bin folder.

The HTML validation occurs in the background on idle.  VS might have not checked it yet.

For more information, see http://weblogs.asp.net/scottgu/archive/2005/11/23/431350.aspx and http://msdn.microsoft.com/en-us/library/f940516c(VS.80).aspx

Thanks.