Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post May 03, 2012 06:52 AM by FightAsABull
May 01, 2012 10:29 PM|LINK
I'm running into an issue when opening a solution (.sln) where Visual Studio forces a .NET upgrade. The upgrade fails but it appears to fail only on the .aspx pages. All of the vb pages associated with those pages upgrade without issue. From what I can find
in the upgrade logs the solution is updating from either version 2 or 3 to version 4.
Is there a way to stop visual studio 2010 or 2008(happens in both) from forcing the update? If not has anyone experienced issues with just the aspx files being unable to update? Any suggestions would be great!
May 02, 2012 09:47 AM|LINK
You can check box to keep backup while conversion?
May 02, 2012 04:48 PM|LINK
Gave that a try but the ascx files don't actually show up there as well...i was able to confirm the project is updating from .NET 2.0 to 3.5
May 03, 2012 06:52 AM|LINK
Hi, hope this helps: