I have a Visual studio web forms project that is written in vb.net 4.8. It was originally built in VS 2012. At some point, I got a free version of VS 2019 to try and opened the project. After a few weeks, I scrapped VS 2019. Now when I open the project in VS 2012, it churns for a moment and VS crashes.
VS must have upgraded my project to work with 2019 and added some pieces that don't work in VS 2012.
How do I downgrade the project so it opens in VS 2012? or can I rebuild the project so it works in VS 2012?
I tried downloading VS 2019 and opening the project. The project kept crashing VS. I created a new project in VS 2019 and imported the files in. After adding them to the project, I had about 5 warning preventing the program from building. Once those were addressed, I could run the project. I will now have to upgrade to the latest version of VS.
Today I want to create a new project via Visual Studio 2019 Enterprise (V16.7.7). By default, the dependencies are missing:
I cannot start the Project via F5:
The Output Window shows 0 errors:
I can see the same behavior when I create a new Blazor-WA project.
I have re-installed the SDK (Microsoft .NET Core SDK v3.1.403) which not solves the problem.
How can I solve this problem?
Our build environment is VS 2015 (ideally) targeting .net 4.0
We have just re-worked our visual studio plugins based on the Visual Studio extensibility project template in VS 2015. The resulting VSIX works great on VS 2015 & 2017 RC1.
However I would like to target the VSIX at VS 2010 (and ideally 2012). This is where the problems start....
VS 2010 uses .net 4.0.
I drop the compiler to .net 4.0
The VS 2015 (4.5) assemblies wont load (i.e. Microsoft.VisualStudio.Shell.14.0).
Thats OK as I don't use anything in them, so I drop the references to them in favour of the version 10.0 (2010) ones.
Great the code compiles.
But the VSIX package does not
1>C:\Program Files
(x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets(1820,5):
warning MSB3274: The primary reference
"Microsoft.VisualStudio.Imaging, Version=14.0.0.0, Culture=neutral,
PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL" could not
be resolved because it was built against the
".NETFramework,Version=v4.5" framework. This is a higher version than
the currently targeted framework ".NETFramework,Version=v4.0".
So the problem seems to be that if I target VS 2010 I need it to build as .net 4.0, but the VS 2015 build script requires .net 4.5.
I'm wondering if its possible to use the VS 2010 build tools in a VS 2015 project? Or must I convert my VS 2015 project back to VS 2010?
UPDATE
Starting to think this is not possible for other reasons...
https://learn.microsoft.com/en-us/visualstudio/extensibility/faq-2017
The new VSIX v3 format is backward compatible with VSIX v2, so you’ll
still be able to have a single VSIX with a single VSIX ID that
supports Visual Studio 2012 and later. The new VSIX v3 format does not
support Visual 2010 and earlier. To support Visual Studio 2010 onward,
you will need to create a separate extension (with a separate VSIX
ID).
I have ran into similar problem, so I have created a Nuget package called VsixUpdater, which can do the VSIX migration automatically if added to a VSIX project, it even works with older versions of Visual Studio (I tested it with 2012), after adding the package the generated VSIX packages will be V3 and 2017 compatible, see https://github.com/axodox/VsixUpdater for details.
Create a seperate project and VSIX for VS 2010 and another for VS 2012 and later. You can have a look at my source here: https://github.com/ErikEJ/SqlCeToolbox
Notice that I require .NET 4.5.1 for my VS 2010 extension also (simply requires that .NET 4.5.1 is present/installed on the PC, and it is built in to Windows 8.1 and later)
In the end I ended up with 2 projects
A project targeting VS 2010 compiled under .Net 4.0 using a version 2.0 manifest (built using VS 2015).
A project targeting VS 2012 + compiled under .Net 4.5
using a version 3.0 manifest (built using VS 2015).
There has been a certain amount of faffing around with references, but it all seems to work. Our only outstanding issue is the code signing, as VS 2015 will not accept anything below SHA256 and VS 2012 will not accept SHA256....
I updated my Visual Studio 2015 RTM from Update 1 to Update 2 and now my Cordova project won't open. I get the following error message instead of my project files:
This project is incompatible with the current edition of Visual
Studio.
I've installed the following hot fix and rebooted my machine and it made no difference:
https://msdn.microsoft.com/en-us/library/mt695655.aspx
The only option I get for that project is to edit my .jsproj file. But I haven't a clue what I'd have to change to make it work.
Here's my version info for Visual Studio:
How do I get my project to work with the new update to Visual Studio 2015?
For what ever reason, Visual Studio seemed to remove the Tools for Apache Cordova and I had to reinstall them from scratch. Once I'd reapplied version 8.1 of the tools, the project loaded up just fine.
Do I have to install Visual Studio 14 preview to build an MVC 6 app or can I do that using Visual Studio 2013 ?
It is required. The new project system only exists in VS 2015. You can also build it via the command line without VS.