Profile Picture

Which Nevron version for .NET framework 2.0 in VS2010?

Posted By Chris M 14 Years Ago
Author
Message
Nevron Support
Posted 14 Years Ago
View Quick Profile
Supreme Being

Supreme Being (4,435 reputation)Supreme Being (4,435 reputation)Supreme Being (4,435 reputation)Supreme Being (4,435 reputation)Supreme Being (4,435 reputation)Supreme Being (4,435 reputation)Supreme Being (4,435 reputation)Supreme Being (4,435 reputation)Supreme Being (4,435 reputation)

Group: Forum Members
Last Active: Last Week
Posts: 3,054, Visits: 4,009

Hi Chris,

The problem is that the visual studio IDE integration code differs from version to version and this is why we had to have different installers for VS2005, VS2008 and later for VS2010 in the first place. You can safely use the VS2008 install with VS2010 - it targets 2.0 of the framework and the only drawback is that it will not register the components in the toolbox automatically. You can use the following steps after install to ensure that VS is compiling with the version you added to the project references exactly (e.g. not taking it from gac or other location):

1. After installation remove all Nevron* dlls from GAC.
2. Start regedit.exe and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Mircosoft\.NETFramework\AssemblyFolders
3. Delete all occurances of Nevron.Components.*

Hope this helps - questions or comments please feel free...



Best Regards,
Nevron Support Team



Chris M
Posted 14 Years Ago
View Quick Profile
Forum Newbie

Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)Forum Newbie (1 reputation)

Group: Forum Members
Last Active: 14 Years Ago
Posts: 1, Visits: 1

We target .NET framework 2.0, but are upgrading our dev environments to Visual Studio 2010. Do we have to install the new Nevron Vision suite for VS2010, or is that really meant for .NET framework 4.0? If that's the case, then should we be installing the version that says it is for VS2005? Will there be any problems doing this, or is it really just a naming issue? 

Given that VS2010 (2008 too I think?) allows the developer to target a specific .NET framework, you may want to consider naming your releases to indicate framework rather than Visual Studio version. Unless of course, if I'm wrong and you are tying into specifics of the IDE.





Similar Topics


Reading This Topic