I have a C++ MFC project that was created and built on visual studio 2003. I want to apply modifications on the software. I tried to open it with visual studio 2013 but a lot of dependencies are not fulfilled. If I recompile it with VS2013 will it still be working ?
Is it even possible to migrate the project from 2003 to the latest versions ? If so what do I have to do ?
Related
First of all, this issue has nothing to do with the installation of SSDT. I have the lastest version installed, at the time of writting this.
My issue is that the SSIS package was written some time ago using, I think either VS2005 or VS2008 as I was using Windows 7 with the lastest SSDT package fro the time, and I now need to open it up to view the workings.
I am now using VS2019 on Windows 10, again with the latest SSDT package, and studio refuses to open the project.
Unsupported
This version of Visual Studio is unable to open the following projects. The project types may not be installed or this version of Visual Studio may not support them.
For more information on enabling these project types or otherwise migrating your assets, please see the details in the "Migration Report" displayed after clicking OK.
- Contessa.SQL.SSIS, "G:\Work Stuff\Solution\40 SQL SSIS\TestSolution.SQL.SSIS\TestSolution.SQL.SSIS\TestSolution.SQL.SSIS.dtproj"
Non-functional changes required
Visual Studio will automatically make non-functional changes to the following projects in order to enable them to open in Visual Studio 2015, Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1. Project behavior will not be impacted.
- Contessa, "G:\Work Stuff\Solution\TestSolution.sln"
I have found the answer and it had nothing to do with the SSDT installed.
After finding this article.
visual-studio-2019-open-solution-file-incompatible
It explains the need to make sure that the SSIS Extension is enables. In my case it needed to be installed.
This occurred because I had installed various versions of SSDT which caused Visual Studio to need me to reinstall.
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.
From my understanding Visual Studio 2005 always uses MFC8 automaticly, VS2008 MFC9 and VS2010 the MFC10.
Can use a newer Visual Studio Version and still link to an older MFC Version?
I searched the options and the project settings all over but I could not find any option about the MFC.
VS2010 apparently (I don't have it, so I haven't tried it) has the ability to use both VS2008 and VS2010 toolsets to build the applications, provided they are both installed in the machine.
More here
I would expect Visual Studio 11 to have the same ability, but who knows...
I have installed full version licensed Visual Studio 2010 Professional, .Net 4.0 on my system. Now I am trying to install Active Reports 6 on it and facing the error "no compatible version of visual studio net found on system". My Active Reports build is 6.0.1.1797.0.
So, do I need to install framework 3.5 before installing? I have not installed Service Pack for visual Studio for now.
Thanks.
Active reports 6.0.1797.0 does not support Visual Studio 2010. Active reorts 6.1.2577 or later supports Visual Studio 2010. And any how, Express edition of visual studio does not support active reports.
So my solution, enhances...I installed the later versions...but unfortunately I am getting some errors in my application because of Active reports version change as my application was made in previous version of Active Reports. So, what I did is, installed the latest version, uninstalled it and again installed 6.0.1797.0 version, and it was installed successfully and my application was also working fine.
#rapsalands...You are correct in understanding that support for Visual Studio 2010 started only after build 6.1.2577.0 was released. Also express edition of Visual Studio is not supported. The first thing to note here is that whenever you install/uninstall ActiveReports 6 from your machine, there should be no running instance of Visual Studio as it affects proper integration of ActiveReports with itself.
Also the errors which you were getting are more likely appearing because of the incorrect references in your project. Whenever you open an existing project after upgrading ActiveReports build, you should remove all the ActiveReports references from the project, re-add them (making sure they point to the version currently installed) and finally rebuild your project.
I think you can also check the blogs for ActiveReports as you might find some useful information about different topics there.
I am just wondering on what version of Visual Studio 2010 to install (Professional or Premium) If there are a few people in the team with a mix of VS2010 professional/premium, would opening solution/project files be an issue, ie incorrect version or prompts to upgrade prjects..
Projects include: asp.net mvc, database and silverlight.
In general projects created by the same version of different editions are compatible with one another - if the edition installed lacks features necessary to load a given project, it will inform you of such and simply not load the project.