I'm trying to update Visual Studio 2017 RC from 15.0.25909.2 to 15.0.25914.0 and when I hit Update button it throws following error
Path to vsix file 'update' is invalid or you don't have required access permissions. Please check the path is valid and you have required access permissions.
Usage: VSIXInstaller.exe [/quiet] ...
...
I ran it as Administrator unfortunately same issue occurs.
Recorded Screen-cast is here
Thanks to #panagiotis-kanavos I did be able to solve the issue. For those who may hit the same wall, here is the steps I followed.
You need to locate Visual Studio Installer which is not in Start Menu!. You may find it at C:\Program Files (x86)\Microsoft Visual Studio\Installer\vs_installer.exe
Once you run it, click on Update button.
It will probably give you errors like this
[232c:0020][2016-12-09T09:31:36] VSIX installer does not exist at 'C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\VSIXInstaller.exe'.
[232c:0020][2016-12-09T09:31:36] Package '...' failed to uninstall. Return code: 2
Check the path and make sure VSIXInstaller.exe is there
Once again, click on Update button.
this time, it will throw a different error and if you open the log file that upgrade process provides, it should have full command details which is/are failing
🚨 WARNING 🚨 following code was in "my" log file and I placed it here "only for demonstration purpose", do not use it directly, check your log file to get correct failing errors
"C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\VSIXInstaller.exe" /q /s /admin /appidinstallpath:"C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\devenv.exe" /logFile:"C:\Users\ciler\AppData\Local\Temp\dd_setup_20161209094800_001_GitHub.VisualStudio.log" /skuName:Enterprise /skuVersion:15.0.25928.0 /appidname:displayName /uninstall:c3d3dc68-c977-411f-b3e8-03b0dccf7dfc
Run that command in your Command Prompt and make sure you change the /logfile: filename in order to eliminate overwriting the existing one.
Related
After re-installing Visual Studio Community edition I've been getting this error.
I get the error right after the splashscreen shows
Could not load file or assembly 'Microsoft.ServiceHub.Client'
Please open File Explorer and search this file name to verify this file is existing on your computer or not.
Meanwhile, you can have a try with the following to troubleshoot this issue:
Clear all folders and files under the folder: %LocalAppData%\Microsoft\VisualStudio\15.0_xxx\ and restart the VS 2017 to check it again.
Open cmd and navigate to the VS 2017 installation folder like C:\Program Files(x86)\Microsoft Visual Studio\2017\xxx\Common7\IDE and run the command: devenv /safemode to run it as safe mode, then check if the installed extensions caused this issue.
Re-run the VS 2017 installer as administrator and choose Repair to repair it
I have installed VS 2010 Ultimate on Windows 7 Enterprise. It is not working. So I uninstalled that and re-install VS 2010 Professional.
But I am getting an error whenever I open Visual Studio 2010.
Error:
The 'Visual Studio Tools for Applications v3.0 Shell Integration Package' package did not load correctly.
The Problem may have been caused by a configuration change or by the installation of another extension. You can get more information by running the application together with the log parameter on the command line, and then examining the file
'C:\users\Name\AppData\Roaming\Microsoft\VisualStudio\10.0\ActivityLog.xml'.
How to fix this issue? Please help me.
I ran Procmon from Sysinternals on devenv.exe with a filter set to capture file system events only, and only not equal 'success' results.
This brought up some results pointing at a directory where devenv.exe attempted to load Microsoft.VisualStudio.Tools.Applications.Package.dll from. None of those directories contained that file.
Searched for that file and found it under C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\PrivateAssemblies\Microsoft.VisualStudio.Tools.Applications.Package.dll That location was not among the directories captured by Procmon.
Copied the file to the first location indicated by the error captured by Procmon and voila, problem solved.
I followed this link to the letter for creating a new project template in Visual Studio for MVC3. Unfortunately, while the template shows up in the Dialog, when I click on it to create a new project, I get the "Exception from HRESULT: 0x80070002". I have no idea how to fix this.
One person in the thread mentioned that the /installvstemplates command has to be run as an Administrator. I've done that. Still doesn't work. This exception is beyond useless.
From a user who contacted Microsoft Support for the same issue (file not found on template) If not on 64-bit machine remove (x86) from folder names. Backup the entire ProjectTemplates folder before you start.
Open C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\VWDExpress\ProjectTemplates\CSharp\Web\1033 and copy any of the folders that have 'MVC' in the name from the second folder to the first (move the 3.1's to where the 3.0's were).
Once you've done that go up a few levels to the ProjectTemplates folder and do the same for the other code bases.
Open Visual Studio Developer Command Prompt as an administrator and run: devenv /setup
This should set up your ProjectTemplatesCache folder correctly and fix the problem.
I am trying to use this tutorial from MS to verify I can build a .cpp file from the command line on my system. I seem to be having problems with my VS Command Prompt. It cannot find cl.exe or the needed include files. I added C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin and C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE to my path so it would find cl.exe. Now my error is:
test.cpp(1) : fatal error C1034: iostream: no include path set
Isn't the whole point of the VS Command Prompt to setup all these environment vars for me? Why isn't it setting it up properly?
I'm not sure exactly what your problem is but you might want to do the following to help determine the actual cause.
You may have noticed that the VS command prompt shortcut is a bat file. The first line is
#echo off
Change it to
REM #echo off
Run it again and see if you get any errors. If you don't it may be in one of the processor specific batch files to know which one that is look for the call to other batch like this.
C:\Program Files\Microsoft Visual Studio 10.0\VC>call "C:\Program Files\Microsof
t Visual Studio 10.0\VC\bin\vcvars32.bat"
Setting environment for using Microsoft Visual Studio 2010 x86 tools.
Again REM out the #echo off in the batch and then run it again and see what errors you get.
Update from comment
The error ERROR: Cannot determine the location of the VS Common Tools folder
means your missing the Environment Variable %VS100COMNTOOLS% which is usually set to
"c:\Program Files\Microsoft Visual Studio 10.0\Common7\Tools\"
You can simply add it back using system properties -> Advanced -> New (under system variables)
See this superuser question for more on environment variables
I just figured it out. Thanks to Conrad Frix for the debugging tip.
It is surely due to some lovely security policy I have here on my workstation. Running the shortcut as administrator works. My account is a local admin account, but the admins do all kinds of weird stuff to our machines here...sigh. So, much of our development has to happen by "elevating".
Note, I was able to change the shortcut to run as under administrative privileges by selecting Properties->Advanced->Run as administrator.
I'm using EditBin to increase the stack size of an application I'm writing. I have this in the post-build event command line for Visual Studio:
"C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\editbin.exe" /STACK:268435456 "$(TargetPath)"
When I build my project, I get this error:
Error 470 The command ""C:\Program
Files (x86)\Microsoft Visual Studio
10.0\VC\bin\editbin.exe" /STACK:268435456 "[Target Executable]"" exited
with code -1073741515.
I have both of the following in my PATH environment variable:
C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin
The command also works when I run it manually with cmd.exe. Does anyone know what the problem is here?
I had the same issue, how I resolved it:
Ran msbuild.exe <my.sln> /t:<mytargetproject> from a VS2010 command prompt, where <my.sln> is your solution name and <mytargetproject> is the project you are trying to build. For e.g. msbuild.exe helloworld.sln /t:mainproj.
When you do this or at least when I ran this, a dialog box popped up and said "foo.dll" cannot be found, I added the path of that dll to my "PATH" environment variable and the problem was solved! See ChrisF's comment to the question, as it says, the error is that some dll/component is missing.
From the dll name it complained about, I believe this is not contained to VS2010 libs/dlls, for me it was a third-party dll (which I am using and supposed to be available during the build) it was complaining about.
The best solution is to run the vcvarsall.bat located in the root of the visual studio install folder(C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC). That sets up the search folders for all MSVC compiler related tools.
I got this to work for now by copying mspdb100.dll into the same directory as editbin.exe, but this is not an optimal solution because every developer on my team will need to do the same thing.