I can build my solution (Rebuild Solution) and it builds ok, but when I pull up an aspx page in the VS 2005 editor, it will have errors in it.  And, the page works when I run the web app.  What is going on?  FYI, I am in the process of migrating from ASP.NET 1.1 to 2.0.  But, this seems more like a general VS 2005 querstion.

Thanks.

What kind or errors? Markup validation, for example, validates your HTML against Web standard. However, even if your HTML is not up to standard, browser may still render it correctly since browsers are forgiving as they must be able to handle all kinds or Web pages, including those authored 15 years ago. Therefore validation error will not necessarily make page render incorrectly in, say, IE, but it may make page render incorrectly in Safari on Mac and page won't pass validation of the W3C validator.

Error 1 Element 'HEADER' is not a known element. This can occur if there is a compilation error in the Web site. c:\inetpub\wwwroot\GPCStoreFront\WebForms\DCHome.aspx 26 18 http://localhost/GPCStoreFront/
Error 2 Validation (ASP.Net): Text is not allowed between the opening and closing tags for element Style'. c:\inetpub\wwwroot\GPCStoreFront\WebForms\DCHome.aspx 38 38 http://localhost/GPCStoreFront/
Error 3 Validation (ASP.Net): Text is not allowed between the opening and closing tags for element Style'. c:\inetpub\wwwroot\GPCStoreFront\WebForms\DCHome.aspx 66 42 http://localhost/GPCStoreFront/
Error 4 Validation (ASP.Net): Text is not allowed between the opening and closing tags for element Style'. c:\inetpub\wwwroot\GPCStoreFront\WebForms\DCHome.aspx 93 38 http://localhost/GPCStoreFront/

I have another post in a different forum here asking about that first error.  But, I don't understand why when I compile, it compiles, but when I load the file into the editor, errors are listed.

Again - those are markup validation errors. They don't mean the browser will necessarily fail to display the page. They mean your page does not conform to Web standards and hence may not render correctly in some browsers since technically browser don't have to support non-standard markup (must most do anyway). I could suggest you how to fix those issues if you posted your page markup (or at least those elements that need to be corrected) here.

Markup validation errors have nothing to do with compilation. Compiler compiles code, not markup.

Thanks for responding.  I am sure I can resolve the validation errors.  I think the concept is really cool.  I like that it is doing the validation.  I see it pointing out some things that are nice to know so that I can resolve them.  But I don't like that it is putting validation errors in the same list as my compiler errors.  Seems to me those should be informational or warnings, not errors.  From as far back as I can remember, an error prevents code from compiliing, warnings and informationals do not.  This seems to be breaking a pattern going back as far as at least 1992, when I started coding.  Seems to me the Error List display should add another class of listing.  It has errors, warnings, and messages.  Maybe they should consider adding a validation issues type.

So, I only see those if I load the aspx page in the editor.  Is there a way to make it show me the validation errors for every page in my project without having to load every one of them into the editor?

Thanks.

for validations error this may work :tools>options>text editor>HTML>validations>select Internet explorer 6.0 from the drop downlist and check and uncheck the checkboxes as u want it to be.