I have a solution that contains a .deployproj type of project. It seems that Visual Studio 2019 is not able to load that project. The detailed error message is the following:
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.
- Provisioning.Arm, "C:...\Provisioning.Arm\Provisioning.Arm.deployproj"
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.
What can I do in order to load the project within Visual Studio 2019?
It seems that you need to install the Azure Development workload in order for Visual Studio to be able to load .deployproj projects.
So just modify the current installation to also contain this workload. (I don't know exactly what individual component needs to be installed for this to work, I just installed the entire Azure Development workload).
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.
I think I was using visual studio 2017 and wrote a SSIS package. Now I installed visual studio 2019 and can't open the solution file. Error:
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.
- ABC, "C:\Users\XYZ\ABC.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.
- ABC_SSIS, "C:\Users\XYZ\ABC_SSIS.sln"
I tried "Right-click on the project and reload" - didn't work.
I tried to confirm SSDT is installed:
it is installed at the installation interface, but doesn't exist in extension manager:
SSIS is a seperate extension now in Visual Studio 2019. You can install that extension in Visual Studio market place. Choose Online tab and search for "SQL Server Integration Services Projects".Hope it can help your problem
1.Extensions -> Microsoft Reporting Service Project
2.and then close visual studio
3.VSIX installer will complete automatically
4.If your project unloaded, right click on project and reload
Today I faced this issue,
Cause
The reason for issue is,
I saw a yellow bg notification at the top of IDE showing performance issue , with option to "disable this" to improve the performance.
I chose disable, later next day when I opened the project, It showed the project is not compatible.
I did Repair SSIS, Uninstall and Reinstall SSIS, and also updated the SSIS to latest version. None of these 3 ways resolved the issue.
Solution
But, I found Manage Extension submenu item under Extension menu, Under installed tab, SSIS extension was in disabled status. I reverted to Enabled status. Sample screenshot of the same for reference is here. If it disabled, simply enable it. Then restart VS with SSIS project.
Enabling the SSIS in manage extensions solved this for me.
Extensions ... Manage Extensions
Online ... Visual Studio Marketplace
SQL Server Integration Services Projects
Download
Close Visual Studio and then run the download
When finished, open your existing SSIS project and right-click the project and select "Reload" or "Reload with dependancies"
You can also now start a new Integration Services project.
I have a custom language and debug editor extension for Visual studio, that I'd like to be able to distribute using the visual studio integrated shell.
However, I am unable to open the custom project files using the integrated shell application:
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.
- scripts, "F:\path\to\example.myproj"
No changes required
These projects can be opened in Visual Studio 2015, Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1 without changing them.
- scripts, "F:\path\to\example.Example_sln"
Everything works fine when the extension is loaded as part of visual studio 2015 directly.
The custom project type was created using The Visual Studio Common Project System
Thanks to user rodya0 on Github, I have an answer:
Add the following:
$ShellFolder$\Common7\IDE\CommonExtensions\Microsoft\Project; \
to the PkgDefSearchPath section of the .pkgdef file in your isolated shell project
I'm encountering an issue when trying to build .modelproj projects using msbuild via Visual Studio 2017 Build Tools.
This is the error I see:
...[ProjectName].modelproj error MSB4057: The target "Rebuild" does
not exist in the project.
I have found this thread relating to some issues opening .modelproj files via the IDE in VS2017 - Visual Studio 2017 not opening .modelproj - however is there a way to get this fix onto just Build Tools rather than the full IDE? Ideally we'd like to avoid having to install the full IDE when all we require are the Build Tools on the server.
however is there a way to get this fix onto just Build Tools rather than the full IDE? Ideally we'd like to avoid having to install the full IDE when all we require are the Build Tools on the server.
You can not build Modeling projects using msbuild via Visual Studio 2017 Build Tools. Because starting with Visual Studio 2017, the UML Designers have been removed from Visual Studio, If you are a significant user of the UML designers, you can continue to use Visual Studio 2015 or earlier versions.
You can get the detail information from Port, Migrate, and Upgrade Visual Studio Projects and Microsoft Application Lifecycle Management：
I have a project from VS Studio 2010 that I want to work with in VS 2015. When I start this Project with VS 2015 I receive an error saying something like "compatibility-Error (Version)".
How can I successfully convert a Visual Studio 2010 project to use with Visual Studio 2015?
Without you going into any more detail about the actual error. (error numbers / screenshot) it will be very hard for any of us to give a real answer. Therefore I am going to suggest you take a look at Troubleshooting Unsuccessful Project Upgrades.
Something else to check out might be the Porting, Migrating, and Upgrading Visual Studio Projects guide
One of the key things mentioned in the 2nd link I provided is:
The following list describes support in Visual Studio 2015 and Visual Studio 2013 for projects that were created in Visual Studio 2012 or Visual Studio 2010 SP
Therefore I'd recommend upgrading the 2010 version to SP1 first. (if this is still installed that is)
One further thing to note is that if you keep the old version of Visual studio installed you can import a project which is made with an older version and skip the update. Visual studio 2015 will then use parts of the older version itself to open the project.
For details you can read How to: Upgrade Visual C++ Projects to Visual Studio 2015 page and the equally useful Installing Visual Studio Versions Side-by-Side page.
It appears that there are issues when moving from VS 2010.Net to VS 2015.Net and may require that you build the project from scratch and copy the code over. VS 2015 requires a Namespace. There are a number of designer issues on control that require the style page be used since various attributes have been removed. Something still, however, do work but you need to review the HTML, specifically things like Font and alignment. While it's a pain it isn't a big deal since it requires mostly cut and paste.
If you are having issues converting web projects the projects may have originally been created as a "web site" rather than a "web Project" . Try opening the application as a web site and see what happens. At least that may help get you to the point you can actually get to the code to convert it in VS 2015. Hope this helps.
Try to Right-click the solution, then select "Re-target solution".