This error does not always show up, and that's why it is weird. For example, we'll be going along, editing our .aspx or .aspx.cs files, saving and running/debugging, and it works fine. Then someone will edit a file and suddenly get the "Object reference not set to an instance of an object" error message. It happened to me just today, when I opened a .aspx.cs file and put a comment into the file. That is all I did; was put a comment into the file. But what makes it even weirder, is if I get out of Visual Studio 2008 and get back in again, and try to run/debug it, all is fine.
Why is that?
...
Go to the complete details ...