Hi i want to move Visual Studio 2008 C#.NET project to Visual Studio 2010. My existing VS2008 project Solution have multiple projects.My vs2010 is a WPF project , i moved some core project VS2008 to VS2010 WPF project. Successfully convert and added into VS2010 project but i am not able to reference converted project.
You should be able to just open the project in Visual studio 2010. It will prompt you before it upgrades. I recommend making a backup (there is a checkbox in the upgrade wizard). Just follow the instructions in the wizard. It is fairly straightforward.
The upgrade only changes the solution/project file. You can still have the app be a .net 2.0 or 3.5 application by choosing the target framework in the project properties. When you upgrade to 4.0, however, is when you will need to do lots of regression testing. We upgraded an MVC 1.0 app to .net 4.0 and had problems with the renderpartialtostring approach. We had to rewrite portions of the app just to upgrade into 4.0.
Also, don't forget that if you upgrade a project, certain behavior of the newer version will be suppressed by means of property sheets. You can get back the proper (new) behavior by removing the InheritedPropertySheets element of each Configuration in the .vcproj files.
Related
Goal:
I try to open a visual studio project (c#) with CLR code for SQL Server from the Pluralsight course.
Issue:
I get no error messages just warnings below after One-way upgrade on Visual Studio 2017.
Your project is targeting .NET Framework 2.0 or 3.0. If your project
uses assemblies requiring a newer .NET Framework, your project will
fail to build. You can change the .NET Framework version by clicking
Properties on the project menu and then selecting a new version in the
'.NET Framework' dropdown box. (In Visual Basic, this is located on
the Compile tab by clicking the 'Advanced Compiler Options...'
button.)
When I open a solution with single project inside I get message below
The Project Needs to be migrated
or
The Project Needs to be loaded
Tried:
I tried editing csproj files with newer/older version numbers.
I tried different PCs with Visual Studio 2017 and Visual Studio 2015
Idea: Install Visual Studio 2010 as course was released in 2010 BUT I really do not want that.
When I got this issue, I tried reloading the project and when I did, it told me that I did not have an SDK installed and then it offered to install the SDK. Once I had the SDK installed, the project loaded and I was able to work with the project.
Just installed Visual Studio 2017 – Enterprise Edition with the following workloads:
Universal Windows Platform Development
ASP.Net and Web Development
.Net Desktop Development
.Net Core cross-platform Development
After this installation, when I create a new .net core or .net standard project, the visual studio restarts while loading the project template.
Steps to create the behavior:
File ⇒ New Project ⇒ .Net Core ⇒ Asp.Net Core Application (.Net Core)
Visual Studio tries to load the selected template then suddenly it disappears and the windows show the dialogue box to Check online help, debug or close it.
Next, visual studio reboots to the start page.
This only happens when I select any .Net Core or .Net Standard project templates.
Much appreciate your help in advance.
I had the exact same issue. It turned out that when a .Net core or .Net standard project template is selected, it tries to restore the packages from NuGet and somehow it was unable to do that or clear the NuGet’s local cache.
Here are the steps to fix it:
Download NuGet
https://dist.nuget.org/win-x86-commandline/latest/nuget.exe
Open the command prompt as “Administrator” – this is important other
cache may not get cleared due to permission issues.
Navigate to the folder where the NuGet is downloaded
Run the following command to clear the cache
nuget locals all -clear
Open Visual Studio 2017
Create a new ASP.Net core project with default templates
Hope this helps!
Now that Visual Studio 2015 RC is out, has anyone installed it and opened Visual Studio 2013 projects/solutions?
Does it ask the files to be changed?
If yes, are the changes it makes backward compatible?
Take a look at the Porting, Migrating, and Upgrading Visual Studio Projects article for Visual Studio 2015. All of the various caveats are described there.
Not all types of project are supported. I tried the following 4 project types:
Vb.net Class project, OK.
Vb.net Web Services project, OK.
Cordova JS project, not OK, need to migrate manually, by moving the sources from root directory to the www directory and install all API again.
C#.net winform project, OK.
Yes, though you sometimes will have to change the version (single number) in .sln file, no other differences found yet.
We resolved this by typically excluding this file from check in and only check it in when there really was a change (added project, ...) - and then to fix the version before checking in. (Different developer machines with different versions of VS.)
See question Visual Studio 2015 solutions backwards compatibility with Visual Studio 2013 and answer https://stackoverflow.com/a/31540590/586754.
(Assuming you are having basic projects that are supported by both versions, like C# and .net framework that is supported by lower version VS.)
I have a project written in visual studio 2008. I want to upgrade to a newer .NET framework. But everytime I open the project and try to change the target Framework it changes back to .NET 2.0.
Let me know if you need more info.
I open the project in Visual Studio 2013.
Thanks.
The solution was to open the project in Visual Studio 2008. Change the target framework to the newest and after that open the project in Visual Studio 2013 and then change the Target Framework to the newest version.
I was hoping there would an option somewhere that would just let me open my VS 2008 projects and continue working in .Net 3.5 - while using some of the neat new VS UI enhancements.
Yes, Visual Studio 2010 allows you to target previous versions of the CLR/.NET framework at the project level.
When you open the Visual Studio 2008 project file in Visual Studio 2010 it will convert the project file for you. Once this is done, it will be smart enough to target the proper framework and runtime version for you (.NET 3.5 and CLR 2). If it doesn't, you can change this yourself on the property sheet for the project.