I'm trying to work out the dependency of the web control pages when the server is set in compiled mode. The server always refers to the compiled version of the page and ignores any changed markup in the external pages.

If I remove the pages from the virtual the application fails? Is there a way to avoid the need to include these pages when the server references them internally? If not, can the markup be removed from the file and the ASP.NET header code left in?

I want to avoid publishing the markup when the pages are read from the compiled versions. I see no need for the markup to exist externally in production. Any tips on this?

Thanks

Richard