I just had a bad experience. A user of my vb project showed me an error message:
“Error: Logon failed.”. I had seen this message before, and it was caused by having Crystal Reports which used xml files that were at a different path location in deployment than they had been in development, or xsd files that I failed to include in my distribution.
By process of adding files from a “working” folder to a “broken” folder I finally determined that this new error was caused by an xsd file that I had created, and later deleted from my project. Using a grep tool I discovered that this xsd file was still in my project (.vbproj) file.
My question is how can I automatically clean out my vbproj file to make sure something like this does not happen again?