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 am using latest nightly build during developmant of my ASP.NET 5 project and faced following issue.
During publishing I have all previous versions of packages published instead of just latest (that are specified in project.json).
So if I previously used "Microsoft.AspNet.Mvc": "6.0.0-beta1", "Microsoft.AspNet.Mvc": "6.0.0-beta2", "Microsoft.AspNet.Mvc": "6.0.0-rc1" I'll get all of them published to publish_folder\approot\packages\Microsoft.AspNet.Mvc.
How can I avoid publishing packages that are not used in the project anymore?
There is no issues anymore, I believe this bug fixed by Microsoft already. I've upgraded KVM to latest RC version as well as all packages in the project. To install and upgrade KVM and KRE do the following:
Open PowerShell as Administrator
Run command: "Set-ExecutionPolicy RemoteSigned" and confirm changes, this will allow execution of PowerShell scripts
Clone https://github.com/aspnet/Home repository (in my case it's D:\GitHub\Home)
in PowerShell console navigate to D:\GitHub\Home and run "kvminstall.ps1"
Change default feed URL to dev branch to use latest packages
a. Open "kvm.ps1" for editing
b. Go to line 41 and set feed url: $feed = "https://www.myget.org/F/aspnetvnext/api/v2";
If you skip previous step, you will get beta1 version of packages (on time of writing this post) instead of release candidate
Open command promt (Windows -> Run -> cmd)
Navigate to D:\GitHub\Home
Run "kvm upgrade" (it will download latest version of KRE x86 and set it as default
Run "kvm up upgrade -amd64" to do the same for x64 packages version
I installed Multi-Device Hybrid Apps for Visual Studio 2013 CTP 2.0. I then updated VS2013 to update 4. Now I can't upgrade MDHA to 3.0 because it tells me to uninstall 2.0 first, however the uninstaller doesn't work. When trying to uninstall 2.0 from Programs and Features, it just goes through the setup and then doesn't remove the software from the Add/Remove list.
I tried following this however it doesn't work:
http://support.microsoft.com/kb/3014133
I ended up discovering that the package GUID in the the KB article is wrong. I used this to uninstall the 2.0, then I could install 3.0. The package ID may vary so you may need to search the directory for vs2013mda_0.1.exe and replace the command with your package location.
"%ProgramData%\Package Cache\{38f367f1-1468-4f16-a4c4-29747084003b}\vs2013mda_0.1.exe" /uninstall /passive /force /burn.ignoredependencies={53d408db-eb91-43fb-9d8f-167681c19763};vsupdate_KB2829760
Also,be prepared to wait. This takes a long time.
Thank you TechnoTim, the problem is that, every people has its own package GUID.
To solve the problem, you must lunch the command from the root directory, c:\, changing the package GUID with your package GUID.
In my system:
C:\>"%ProgramData%\Package Cache\{dea88246-f74a-4171-ad6c-d9c978bf2973}\vs2013md
a_0.1.exe" /uninstall /passive /force /burn.ignoredependencies={53d408db-eb91-43
fb-9d8f-167681c19763};vsupdate_KB2829760
To find the right package GUID I go to C:\ProgramData\Package Cache\ and search for
vs2013mda_0.1.exe and save the path in the block note, then change in path in the orignal command and lunch it from the root directory c:\, and its work.
Sorry fom my english.
Goodbye!
"You cannot install Visual Studio Tools for Apache Cordova CTP3.0 in Visual Studio 2013"
To resolve this issue, follow these steps to uninstall Multi-Device Hybrid Apps for Visual Studio CTP 2.0
Open a command prompt as an administrator.
Run the following command: "%ProgramData%\Package Cache{dea88246-f74a-4171-ad6c-d9c978bf2973}\vs2013mda_0.1.exe" /uninstall /passive /force /burn.ignoredependencies={53d408db-eb91-43fb-9d8f-167681c19763};vsupdate_KB2829760
Run vs2013mda_0.3.exe again for Visual Studio Tools for Apache Cordova CTP 3.0.
The above worked when installing update 4, please see: http://support.microsoft.com/kb/3014133
I solved this problem by another way.
I have tried to uninstall from command line, but no one of paths don't exists on my computer.
And I simply created another user with administrator permissions and installed new apache cordova tools from that user.
In my situation it correctly works running by new created user and old user.
Sorry for my horrible English.
I'm having trouble with launching aptana 3 after an update yesterday.
Running on windows 7 64bit.
I get this error trying to launch:
The aptana studio 3 executable launcher was unable to locate its companion shared library.
Did a re-install with the latest version from the Aptana website, I didn't try this primarily because I feared all my settings would be gone (like the update did). Nothing to fear, I just needed to re-link my workspace.
All my preferences where still there.
I have downloaded recently Aptana Studio 3, build: 3.0.6.201110251455 and I have the following Aptana Studio 3 bug which prevents me to work with PHP (a project based on Symfony2).
http://jira.appcelerator.org/browse/APSTUD-3617
Error while indexing module: ClassCastException: Variable cannot be cast to Identifier
Could you please let me know when Aptana Studio 3.0.7 will be released or how to get this bug fixed into Aptana Studio 3.0.6 ?
3.0.7 is tagged as Due: 02/Nov/11 in JIRA but I can't find where I can download it.
3.0.7 is feature complete, but due to scheduling issues, it will out next month. In the meantime, grab the beta from preview.appcelerator.com.