Here’s a quick ASP.NET development question for you. I’ve talked a lot about me focusing on doing a variety of website application projects using Visual Web Developer Express 2005 and teaching myself ASP.NET and VB and SQL along the way.
We get this error fairly regularly when we make an edit to one of our master pages in a project and forget to rebuild the entire site. Normally a quick rebuild and update of all the files on the server will fix the problem and we don’t have to worry about again.
It seems to only really occur when a change is made to one of the master pages.
One real oddity with this error is that with one client they would get the error when someone would be viewing their pages internally on their network via an IP address, but anyone accessing the site through the Internet via a remote office wouldn’t see the error. That could make sense initially to me, but both internal and external sites are pointed to the exact same directory of files.
Here’s my two questions:
- What’s the root cause of this error?
- Why would the error impact differently based on internal/external access to the pages?
