Friday, February 22nd, 2013
After an upgrade to Visual Studio 2012, a user reported this error while trying to build a project:
The project file ‘ ‘ has been renamed or is no longer in the solution.
It turns out VS2012 is a little more strict about missing references. Go through and clean them up and the build will work.
There was a forum note on MSDN as well.
Monday, February 18th, 2013
Migration to Visual Studio 2012 has started. We had a couple incidents of the upgrade hanging at the splash page.
The previous version installed was 2010. Nothing obvious and there were no errors.
After digging around, it turned out to be the video drivers. They were upgraded and the install continued.
Sunday, September 16th, 2012
I saw an email exchange about issues surrounding visual studio 2010 and using network shares for work. Previously, there wasn’t an issue with 2005. Microsoft was contacted and they basically said it’s a “feature.”
I did some searching on the Net and found an interesting discussion on a similar problem. As it’s explained; Microsoft .NET framework is not fully trusted but you can modify it. One person explained he followed the directions from another post.
It’s an interesting approach and it kind of makes sense depending how often visual studio does security checks.
In my situation, I passed on this information but the users thought it would not address their problem. Even if it doesn’t; this was interesting to read so I will keep it for future reference.