After I installed an extension to Visual Studio 2017 Enterprise, VS crashes on startup. In previous versions there was a /safemode switch. I tried it but it seems to be no longer supported. What can I do to suppress loading of extensions in Visual Studio when it crashes (cannot disable extensions via extension manager).
Thanks
There is still a /SafeMode switch. If this does not help you need to do a repair on visual studio 2017
https://learn.microsoft.com/en-us/visualstudio/ide/reference/safemode-devenv-exe
Related
I have Visual Studio 2019 16.8.2 and I have installed the Office Development tools from Visual Studio Installer. I then created an Excel Web Add-In project and when I try to run the project, I get this error:
In the output window, there isn't much useful info:
Excel is of course installed, I have the following version:
Could there be some form of Compatibility issue? or maybe something in the Visual Studio Version?
I tried to check online but couldn't find anything related to this.
The problem is that you should not Visual Studio as administrator. When running as Admin it results in the error. Running as not admin works correctly.
I tried to open a .Net Core solution which was working fine in 2015. Recently they added some .Net Core projects to the solution and asked us to upgrade to Visual Studio 2017 to be able to run them. We installed Visual Studio 2017 and tried to open the solution, but I am not able to build it. I get the following errors when I right-click and try to select "Manage Nuget packages".
I tried to open the PackageManager console from Tools: even this is not working
I also performed the "repair Visual Studio" process too.
Finally i resolved it by deleting my nuget.config both at project level and also in %appdata%/roaming/nuget .I think the issue is because of broken config file due to change from visual 2015 to visual studio 2017 .Not sure about the exact issue though
I'm migrating a C++/CLI project from VS2008 to VS2017 but I always get an error when "reloading" the project to convert.
The project don't load and I don't see any clear error message about the reason.
You should check that the correct components of Visual Studio 2017 are installed.
May be it's not installed by default in your case. It happened to me when I installed Visual Studio 2017 using this chocolatey package
You can solve this issue with the steps in this question: Visual Studio 2017 Professional C++/CLI Missing
We have a build definition in TFS 2015 that have worked fine with Visual Studio 2015 projects and solutions. We have now decided to upgrade to Visual Studio 2017 and thus we would like to target Visual Studio 2017 in the Visual Studio build task. We have installed Visual Studio 2017 on the build agent. Unfortunately the only options available int the Visual Studio build task are 2012, 2013, 2015 and Latest. We have tried latest but it does not find Visual Studio 2017 on the build agent. It won't work with the msbuild task either.
I have a similiar issue and resolved by installing VS2017 in my build agent server and configuring MSBuild to point to my MSBuild 15.0 folder:
Add MSBuild to your build steps
On the Advanced options, expand and fill the 'Path to MSBuild' like the image below:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin
VS2017 RTM is released recently while TFS2015 was released before. That's why there is no VS2017 option in VS Build Task in TFS2015 Server. If you upgrade your server to the latest TFS2017, you would see "Visual Studio "15" (preview)" option listed in VS Build Task which is the version for VS2017 preview. And in the feature, the option will be updated to VS2017 which is the same as VSTS.
we are facing a similar issue and it is not possible for us to update ourselves as it is maintained on a company level where we cannot take that much influence.
However our team wanted to switch to VS2017 and make use of the C# 7 features. That's why we tried it as well with replacing the build steps from Visual Studio Build to MSBuild. Sadly this did not work as expected (we got some errors during the build).
As our main objective is to use the C# 7 features we looked for a way how to still achieve that at the time with Visual Studio 2015 remaining on the Build Server. We ended up using the nuget package Microsoft.Net.Compilers that, when used in a project, will use that compiler instead of the installed one.
More on this can be found in this Thread.
It seems the updates to the build tools are installed via the command line of the VS2017 installer.
See the docs for details.
Just adding another thing: if you're using custom build template make sure to edit it and modify the ToolPath attribute value to:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin
Visual Studio 2012 Premium crashes when I use the Solution Configuration Manager (or drop down on tool bar) to switch from Debug solution config to Release. As soon as I make the selection to the Release config, I get a dialog with a progress bar stating it is looking for a solution to the problem and after a few seconds that dialog closes VS closes and another dialog opens that states it is restarting Visual Studio. I get this same behavior if I try to create a new configuration from within the Solution Configuration Manager; i.e., as soon as I save the new config VS crashes. During the crash I'm not given the option in the dialogs to get detailed info for the crash.
This did not happen with the same code in VS2010 and Win7.
My work-around is to modify the Debug config to be what I need for Release, and then put it back to what I need for Debug.
VS 2012 was installed on a clean (not an update) install of Windows 8. I've installed all the latest updates for both Win8 and VS. Here is the Visual Studio boiler-plate info:
Microsoft Visual Studio Premium 2012
Version 11.0.50727.1 RTMREL
Microsoft .NET Framework
Version 4.5.50709
Installed Version: Premium
LightSwitch for Visual Studio 2012, Team Explorer for Visual Studio 2012, Visual Basic 2012, Visual C# 2012, Visual C++ 2012, Visual F# 2012, Visual Studio 2012 Code Analysis Spell Checker, NuGet Package Manager 2.0.30717.9005, PreEmptive Analytics Visualizer 1.0, SQL Server Data Tools 11.1.20627.00, Web Developer Tools 1.0.30710.0