Re: Upgraded to Visual Studio 2005 - Intellisense/build problem

tocohara — Fri, 01 Feb 2008 22:53:20 GMT

Have you tried making the reference to the assembly in code (i.u using; inherits)???

Upgraded to Visual Studio 2005 - Intellisense/build problem

miriv365 — Thu, 31 Jan 2008 13:45:46 GMT

I have a strange problem and am wondering if anyone has any ideas on how to fix my problem. I have several projects written in ASP.NET 1.1 using Visual Studio 2003. I recently upgraded one of them to ASP.NET 2.0 using the built in wizard in Visual Studio 2005, then converting it into a web application.

My issue is that for some reason, the project still seems to be using all the .NET 1.1 dlls, especially when using Intellisense.

For example, I was going the code and trying to clear out obsolete methods, one of which is ConfigurationSettings.AppSettings("XXXXXXXX") and changing it to System.Configuration.ConfigurationManager.AppSettings("XXXXXXXXX"), however intellisense does not seem to see the ConfigurationManager as a member of Configuration (as it should in the 2.0 framework).

So, thinking the IDE still thinks the project is running .NET 1.1, I went and deleted all references in the project, then reset them and made sure all the references pointed to 2.0 dlls. That doesn't seem to work either.

I also checked the actual project file and opened it in Notepad to make sure there were no lingering 1.1 references, but didn't see anything strange.

Anyone have any ideas?

Migrating from ASP.NET 1.x to ASP.NET 2.0

Re: Upgraded to Visual Studio 2005 - Intellisense/build problem

Upgraded to Visual Studio 2005 - Intellisense/build problem