It’s time to check in your changes in VS.NET 2003. You’re working on a solution with a Web project. You notice that an .aspx file is checked out.
You can’t remember changing the file, so you right-click and choose ‘Compare Versions...’ VS.NET says:
That’s ok, because sometimes when you open an .aspx page with VS.NET, it’ll get marked as modified (and hence checked out) even though you didn’t change anything. This is probably just VS.NET being buggy then...
The next thing you might do is to ‘Undo Checkout...’. This will tell you that the file is modified, but you know about the above bug, so you let it continue. You don’t notice it’s talking about the code-behind file now, whereas earlier it was referring to the .aspx.
Bad move. You had made changes, but VS.NET wouldn’t tell you because you had changed the code-behind file, not the .aspx. If you want to see these changes, you have do something like switching on ‘show all files’, which you normally keep switched off because it’s annoying and pointless. You then have to expand the tree from the .aspx file to get to the code-behind.
Just one of many reasons you should never trust your IDE, especially when it’s been written without due care and attention.