If you use subversion for version control, you are probably aware of the .svn issues.
I feel like Studio 2003 is Developing Old School. I’ve fully embraced 2005. Now I can hear you developers that are ten and twenty years older than me talking about programming with buttons and switches and the graduation to teletype and finally dumb terminals. While I haven’t experienced that first hand, I can say that I can still develop with notepad or vi with the best of them.
Still, stepping back to Visual Studio 2003 after a full year of 2005 just feels old.
OK, the point is, that I am doing this. I’ve run into the well known .svn issue, and after some searching I think I’ve come up with a better fix than I’ve seen suggested yet.
My fix:
1. Close the project file.
2. Open in a text editor such a gvim or notepad2.
3. Change the value of the ProjectType attribute to “Local” from “Web” under the /VisualStudioProject/VisualBasic node.
4. Open the new project file in visual studio.
It turns out that the web project is just a class library project with a remote target. Why MS feels compelled to continue to abstract this for developers is beyond me. Developers should have a deep understanding of filesystems, both local and remote. If they do not, then purhaps they need additional training, or should consider a different career.