Is there any simple way to determine Project Template (the one developer picked initially) of an existing project? I am using Visual Studion Community 2022
Related
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).
Is it possible to build single rdlc file without creating the project in visual studio?
Check out Report Builder 3.0. My team never uses Visual Studio to create/edit reports.
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
Ok, i already know how to create a new project template using export template feature from visual studio 2010. Now, what I'd like to know is how can I create an item or add a reference to an dll dynamically based on user selected option in wizard interface.
I know that is possible to use conditional and loops within visual studio project template, but how can I change the output project?
Is it possible to build a Debugging Visualizer that can be used in multiple versions of Visual Studio?
A Debugging Visualizer has to reference Microsoft.VisualStudio.DebuggerVisualizers.dll and there is a separate version of the assembly for every version of Visual Studio. It seems that these versions are not compatible. For example, if I built a visualizer that references Microsoft.VisualStudio.DebuggerVisualizers v9.0, it can be used in Visual Studio 2008, but not in Visual Studio 2010.
I am looking for a way to target at least Visual studio 2008 and Visual Studio 2010 while maintaining only one project for the visualizer. Duplicating the project and changing only references to Microsoft.VisualStudio.DebuggerVisualizers will work, but it creates a maintenance horror.
If your code base is exactly the same for both referenced assemblies then I would suggest the same approach as I've suggested in this question: Visual Studio Installer -- Change application resource
The idea is to have 1 project where you will have a MSBuild property which VS to target and depending on this property you may reference either VS 2008 or VS 2010 DebuggerVisualizers assembly.
The only other solution I see is the one you've mentioned - having 2 separate project files to target different VS version. I do not think it will be that difficult to maintain two versions if you will not duplicate code. And you can avoid duplicating code by including code files as links into your projects.