I developed an application into Visual Studio 2012. Now I installed Visual Studio 2015 and run the same application into Visual Studio 2015. but i found an error "this project is incompatible with the current edition of visual studio" I searched it again and again and found many solutions but these solutions are not working for me.
The problem was that I wasn't select Microsoft Web Development during installation period so that whenever I opened my ASP.net MVC project in that installed IDE. It showed me error this project is incompatible with the current edition of visual studio. So I updated this installed 2015 Visual Studio by Control Panel\All Control Panel Items\Programs and Features. Now it is working
This stackoverflow provides better answer for various other project file failures which cause same error as above.
Related
I am following the Microsoft official documentation to build development environment for D365 F&O.
Unfortunately, I couldn't find Application Explorer anywhere in the Visual Studio IDE. (I am using the latest 2019 community version from Microsoft).
Is there any way to turn it on or maybe any more understandable guide I should try?
https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/dev-tools/introduction-visual-studio
In which Workload of the Visual Studio 2017 Community 15.9 installation would I find the VS2017 BuildTools component?
I am looking at the workloads in the installer options and there seems not to be any workload that has such a thing.
I even searched in the component in the Individual Components tab also but couldn't find anything matching the exact string.
The reason I am looking for it is that when I try to build the source code for ASP.NET MVC v5.2.6, I get the error message as follows.
> build
Could not find MSBuild.exe. Please install the VS2017
BuildTools component or a workload that includes it.
*** BUILD FAILED **
I had written to the ASP.NET MVC team earlier about this message before I had installed Visual Studio 2017. I had had just Visual Studio 2019 then and they asked that I install Visual Studio 2017.
I already have MS Build at various locations. I had multiple versions of MSBuild even before having installed VS 2017.
Build Tools for Visual Studio 2017 is still available as an online installer. You can get the current version here: https://visualstudio.microsoft.com/thank-you-downloading-visual-studio/?sku=BuildTools&rel=15.
I am having difficulty using Ionide on Visual Studio code, after following tutorials and reinstalling to no avail, one problem still persists - this is that Visual Studio Code cannot find Microsoft Build tools 2013 - I have both the extension and the zip on Microsofts website installed.
edit: when attempting to run f# in VScode I am prompted to install MS build tools 2013
Any ideas people?
Many thanks,
Elliot
I have Visual Studio 2013 Professional, and I'm trying to get an installation of VS Express for Desktop 2013 with F# support. I installed VS Express and the Visual F# Out Of Band Release 3.1.1 as indicated on fsharp.org, but after both completed, nothing F# shows up in VS Express. No F# Interactive window is available and no templates for creating an F# project. Is this because of a conflict with Visual Studio 2013 Professional? Is there a way to get F# support in VS Express with VS Professional installed side by side?
I simply uninstalled and reinstalled Visual F# and that seemed to fix the problem. I have no idea what caused it in the first place. :S
I have opened a project created in visual studio 3 in visual studio 5 unknowingly. So when I am trying back to open that project in visual studio 3, it is not getting opened and also showing an error saying
THE SELECTED FILE IS VISUAL STUDIO SOLUTION FILE, BUT WAS CREATED BY A
NEWER VERSION OF VISUAL STUDIO AND CANNOT BE OPENED.
What can I do to open the file in visual studio 3?
Thanks in advance!!!!
If you don't have a backup of the project files, perhaps you can use the Visual Studio Project Converter to recover your project.
From the link:
I have to say that these versions of Visual Studio are now very much out of date - it might be better to just upgrade everything to VS2013.