Here is the summary of what was going on:
I had VS 2015 RC Enterprise installed. When I tried to install VS 2015 Community over it, it was blocked because it had enterprise installed. Tried to uninstall that, said it is not really installed and if I want to just remove it from list of installed products. Uninstalled from command line with /uninstall /force, worked but the community installer still complained. Went few rounds with installing VS 2015 Enterprise RTM, uninstalling that, and then trying to install community edition, but it still thought Enterprise was installed. Finally I fired up procmon and started deleting registry entries from VS 2015 that it was referencing and finally got it to install.
So now I am here - things seem to work except MVC support:
I repaired, modified, uninstalled and installed again a few times, no joy.
ActivityLog.xml says this:
<description>CreateInstance failed for package [Microsoft.VisualStudio.Web.Mvc.Package.MvcPackage]</description>
<guid>{B54016DB-B3E6-4960-8262-81772C777DE9}</guid>
<hr>80070002</hr>
<errorinfo>Could not load file or assembly 'Microsoft.VisualStudio.Web.Mvc.5.0, Version=5.2.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.</errorinfo>
I've run out of ideas as to what else I can do to make this work, any help is very much appreciated.
Did you ever have earlier releases than RC installed, before Ultimate was renamed to Enterprise?
If you have VS RTM (Community, Professional, or Enterprise) installed you can try the following:
Close all instances of Visual Studio
Run the following from a command prompt to forcibly remove MVC: msiexec /x {61A70737-1FE8-E16A-8791-5C8D54990F5B} IGNOREDEPENDENCIES=ALL
Open appwiz.cpl (Add/Remove Programs), click on Visual Studio 2015, select change and then select the Modify option once the installer is launched.
Thanks,
Jacques
Related
When I am trying to install CMake I get the error:
Visual Studio 15 2017 could not find any instance of Visual Studio.
I am using Windows 7 and Visual Studio 2017. The CMakeOutput.log file writes:
The system is: Windows - 6.1.7601 - AMD64
Any ideas?
I ran into the same error and performed the following steps to resolve the issue:
Open Visual Studio
Go to Tools -> Get Tools and Features
In the "Workloads" tab enable "Desktop development with C++"
Click Modify at the bottom right
These steps resulted in the "Visual C++ tools for CMake" feature being installed, but the other optional C++ features included in this workload may also helpful for what you are trying to do.
After the Visual Studio updater finishes installing try re-running the command. You may need to open a new command window.
In my case, I installed Visual Studio, selecting the workloads and modules that I wanted, but I ignored the request to reboot, assuming that shutting down the computer at the end of the day and restarting it the following day would suffice. I was wrong.
The following day I tried a cmake build and got the "could not find any instance of Visual Studio" error. After several attempts to resolve, I re-ran the installer, made no changes to the configuration, and clicked Modify. This time I let it reboot the computer. The reboot took a long time. After which my cmake build worked.
If you have already installed the workload Desktop development with C++ and still getting the following errors while using visual studio 2022 for flutter
Generator
Visual Studio 16 2019
could not find any instance of Visual Studio.
Building Windows application...
Exception: Unable to generate build files"
Solution: Follow these steps,
Edit your_flutter_path\packages\flutter_tools\lib\src\windows\build_windows.dart, and change the constant on line 28 from Visual Studio 16 2019 to Visual Studio 17 2022
Delete flutter_tools.stamp and flutter_tools.snapshot from your_flutter_path\bin\cache\
Run flutter clean in the project
I had the same issue "could not find any instance of Visual Studio"
but with Visual Studio 2019 (Community Edition) and I just had to configure the VS160COMNTOOLS variable so that CMake correctly detects Visual Studio.
export VS160COMNTOOLS="/c/Program Files (x86)/Microsoft Visual Studio/2019/Community/Common7/Tools"
(cf https://cmake.org/cmake/help/latest/generator/Visual%20Studio%2016%202019.html)
With Visual Studio 15 2017, the variable you need should be VS150COMNTOOLS.
(cf https://cmake.org/cmake/help/latest/generator/Visual%20Studio%2015%202017.html)
NB: in my case, in a Travis-CI workflow, I installed Visual Studio using the commands (no need to reboot):
choco install visualstudio2019community
choco install visualstudio2019-workload-nativedesktop # required
With only the first package, CMake detection of VS2019 failed.
I was configuring a Jenkins build node and could successfully run CMake GUI manually but command line use or builds using the CMake plugin would fail with:
Visual Studio 16 2019 could not find instance of Visual Studio.
-A x64 parameter was added with no change in result.
The problem was that CMake could not determine the Windows SDK version.
By adding CMAKE_SYSTEM_VERSION parameter CMake was then able to find Visual Studio.
-D CMAKE_SYSTEM_VERSION=10.0.18362.0 (use your windows SDK version)
Environment:
windows 10 system build: 19042
CMAKE 3.19.4
VS 2019 Professional 16.8.4
Jenkins 2.235.1
Full command line that worked:
"C:\Program Files\CMake\bin\cmake" -G "Visual Studio 16 2019" -D CMAKE_BUILD_TYPE=Release -A x64 -D CMAKE_SYSTEM_VERSION=10.0.18362.0
When using VS 2017, be aware that this is really VS 2015, and CMake identified it as VS 2017 2022 which is not the version of VS 2017 I had, that gave me this error. So the conclusion I offer is to try different versions, specifically the 2015 one.
I had a similar issue where installing libzmq in my npm project was throwing the same error and that wasn't getting solved by enabling "msbuild" under "Desktop development with C++" in the Visual Studio installer.
My solution ended up being to reinstall the Windows build tools for npm with the following command.
npm install --global windows-build-tools
Note: Remember to run the command prompt (or whatever terminal you are using) as admin before running this.
If the CMake used to work with the installed Visual Studio and is broken someday, then the problem could be VS requires system reboot to complete some update.
For quick verification, rename HKLM\SOFTWARE\WOW6432Node\Microsoft\VisualStudio\Setup\Reboot to like HKLM\SOFTWARE\WOW6432Node\Microsoft\VisualStudio\Setup\Reboot.bak, then re-run cmake which should succeed. Don't forget to rename the registry back and reboot the system if this is the problem.
In my case, I was selecting different version of visual studio in that configuration dialog box whereas I installed different version.
Do select the same version.
Above solutions did not solve this issue for me. After installing node.js from https://nodejs.org/en/download/ apparently a correct version of windows-build-tools was installed
I reinstalled the Visual Studio 2019(my former one is 2017 version ) with all those settings required(my cmake version is 3.23.0),and it works. So try to install different versions.
In my case, the problem was gone after I deleted the previous cmake result directory and then ran cmake again.
if you have installed two or more Windows 10 SDK, delete them excluding latest one.
Try downloading the windows-build-tools package.
npm install --global --production windows-build-tools --vs2015
This step should be the end-all-be-all solution to fixing node-gyp problems. For most people, that’s true. NPM has a package called windows-build-tools that should automatically install everything you need to get node-gyp working, including the Microsoft build tools, compilers, Python, and everything else required to build native Node modules on Windows.
I have a problem when I try to reinstall the ODT 2017: I already had it installed, but when I opened Visual Studio and wanted to check the connection it shows the error "The requested .NET Framework data provider is not found. It may not be installed."
I uninstalled it, and then when I wanted to reinstall it, I was amazed at the error that it was still installed, "Oracle Developer Tools for Visual Studio 2017 is already installed. Please uninstall and try again."
I don't know if I have a folder or file in a hidden folder...
Okay, I am not exactly sure why this worked but I don't want to mess with it since it is working great right now.
I had tried all the methods of manually removing Oracle software and none of that seemed to work. I started exploring the command line options and was trying to force an uninstall even though it wasn't installed. I was hoping it would clear something out.
From command line I tried:
ODTforVS2017_122010.exe /V /uninstall
However, instead of uninstalling anything, it launched into the normal install. Only this time, it worked! Go figure.
Just in case this had something to do with it... Just before this, I accidentally started the install for the VS 2015 version which started normally. Was really excited until I realized it was the wrong version. Maybe this cleared something out? No idea...
I have to move on and finish before the deadline. I hope this helps you.
Karl
The accepted answer did not work for me, so I had to investigate further. I was able to solve the problem by manually uninstalling the vsix from Visual Studio (using the Visual Studio 2017 Command Prompt):
vsixinstaller /a /u:"Oracle.VsDevTools.15.0"
Then, I simply ran the installer again and it worked.
In my case the issue was that even after my previous uninstall with the wizard, the extension (ODT) still on VS2017 but it was disabled, so i uninstalled it from VS and then installed it again with the wizard
I've downloaded Umbraco, connected to a database and installed a sample site but when I try to run in Visual Studio, I get this error:
Could not load type 'Umbraco.Web.UmbracoApplication'.
Any ideas?
I usually follow this guide to get Umbraco up and running with Visual Studio: Setting up Umbraco 7 in Visual Studio 2013 for MVC 4 development
You are possibly missing a reference. Also - I found this happens in my version 7.2.4 too.
Check that the install completes - especially if you installed with NuGet. Sometimes powershell doesn't work and the installation is not completed. Look for yellow text during installation. If this fails, try an older version.
I'm trying to deploy to Azure Websites (Preview) from TFS (Preview). The build works and the website is deployed but when my code tries to access the Azure RoleEnvironment the website throws the following exception:
Could not load file or assembly 'msshrtmi, Version=1.7.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its
dependencies. The system cannot find the file specified.
I've tried all solutions proposed in the following thread with no luck. I think it has do to with the TFS.
I have tested this:
Reinstalled Azure SDK and Tools
Removed all PlatformTarget from
projectfiles
Wrote post-build event to delete msshrtmi.dll
Targeted all assemblies to x64 (-> failed all unit tests
on TFS, it seems to be x86, even if allowing x64 in .testsettings)
Could not load file or assembly 'msshrtmi' or one of its dependencies (Azure Table Storage Access)
I've ran out of ideas on how to troubleshoot this issue? Does anyone have any suggestions?
I've encountered a similar issue in earlier versions of the SDK when doing some builds. My solution wasn't entirely intuitive. If I go through each of my build configurations and do a "Clean Solution" then go back to the build configuration I actually care about and do a build this issue goes away.
I have no explanation as to why this works, but after hours pulling my hair out, I was just happy to have a solution.
After 7 hours of mindblowing trial and error I finally fixed this. The problem lay with having Microsoft Windows Azure tools for June 2012 together with Microsoft Windows Azure tools for November 2011.
The steps I followed:
Remove Microsoft Windows Azure tools For Visual Studio 2012 RC - June 2012
Install Microsoft Windows Azure tools for Visual Studio 2010 - June 2012 Edition
Remove Microsoft Windows Azure tools for Visual Studio 2010 - November 2011 Edition
Now re-open the project that was trying to be deployed
Visual Studio will try to convert all the November 2011 binaries to the June 2012 edition
Once this is successfully done, re-check all the Microsoft.WindowsAzure references to see if they are version 1.7.0.0
Publish to Azure!
Hope it helps someone, I'm so tired I'm not coding for the next 24 hours.
I had the same problem where it was always looking for the 32 bit version of msshrtmi in 64bit app causing an error like this. I never found out why but I created build task in my project that would delete the offending 32bit file from the bin so 64bit is found in GAC.
I've just downloaded the ASP.MVC MSI package, but the installation fails with the "There is a problem with this Windows Installer Package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor." message.
I see that other people too have the same problem (http://forums.asp.net/p/1336453/2699267.aspx). Anybody else?
I'm running VS 2008 Professional edition with SP1 on Vista.
Some additional info: entries like Error in Template (C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\ProjectTemplates\VisualBasic\Workflow\1033\StateMachineWorkflowLibrary.zip), file (StateMachineWorkflowLibrary.vstemplate). Unregistered ProjectType (VisualBasic). This can be caused by an incorrect ProjectType or because the project type package is not installed. appear in the event log.
BTW I don't have VisualBasic installed. I'm thinking about reinstalling VisualStudio ... :|
I removed all the bad templates and this didn't resolve the issue for me. I found that removing other Add-Ins I had installed let me install Beta 1. In my case the bad add-in preventing the install was Clone Detective.
I had this exact error message from a completely different MSI package - the DevExpress toolkit - turned out to be caused by one of the "defensive" packages installed on my machine.
Check your anti-virus, anti-spyware, anti-intrusion, firewall, anti-xxx etc etc packages to see if any of them might be stopping scripts from running properly.
Hope this helps.
The installer is trying to add templates to the VB package without checking to see if it exists first (ScottGuuuuuuu!).
If the rest of MVC is installed and working, forget about it. If not, you don't have to reinstall VS. A quick fix is to simply install Visual Basic (e.g, modify your installation rather than reinstall it).
Okey, like Simon said, Clone Detective addin was the troublemaker which prevented the installation of ASP MVC. I deinstalled Clone Detective and now MVC has installed without problems. Thanks guys!