Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Feb 14, 2013 01:36 PM by ukandyman
Nov 26, 2012 08:29 AM|LINK
I have opened our asp.net 3.5 website on a Windows 8 64bit 2012 VS Ultimate (formerly 2010 on Windows 7 32bit VS 2010 SP1) and it has migrated the project. Gave me the Upgrade Report with only 2 warnings - no errors.
Now when I open the project I get errors on the most basic classes like DateTime or HTTPCOntext:
"DateTime is not declared" or "HTTPContext was not declared"
I have checked all the references to the DLLs etc but can't see the problem.
I want to run the website on 3.5, not 4 or 4.5 so its not a real migration IMO.
Nov 28, 2012 08:06 AM|LINK
You could refer this document to learn Visual Studio 2012 Compatibility
here, This document provides the following information about compatibility between Visual Studio assets created in Visual Studio 2010 with SP1 and assets created in Visual Studio 2012.
hope it helps you.
Nov 28, 2012 08:16 AM|LINK
If this is Visual Basic project, then you need to check the Option Strict and Option Explicit settings on the project. It's possible that the setting is not correctly migrated in the upgrade process.
Hope this helps.
Nov 28, 2012 08:57 AM|LINK
Hi guys, thank you for the link - a good overview.
It's an ASP.NET Website, Framework 3.5. I will check the Option issue. Also when I double click on an error in the list, the cursor jumps to line 1 where for example it says "Imports Microsoft.VisualBasic" or similiar. Am not in front of the machine richt
WIll keep you posted.
Dec 07, 2012 01:18 PM|LINK
I have rechecked the project now. Also with an eye on the "Option" settings with no luck.
It must be something really basic because I get errors on such simple classes.
Dec 09, 2012 10:56 AM|LINK
Can you try be clean and build the solution?
Please 'Mark as Answer' if this post helps you.
Feb 14, 2013 01:36 PM|LINK
I had the same issue and overcame it by turning off Option Explicit and Option Strict from the Tools --> Options --> Projects and Solutions --> VB Defaults menu and restarting Visual Studio.
After I restarted the erroneous errors went away.