View Single Post
  #3  
Old 10-08-2014, 10:45 AM
jmmcd jmmcd is online now
Registered User
 
Join Date: 02-10-2012
Posts: 4
Yep, thanks!

The troubleshooting item 4500 explained what was going on. I didn't realize VS no longer forced the .sln upgrade, and that was the problem. The developer first upgraded to VS 2010 and then upgraded again to VS 2013.
Reply With Quote