We Keep Coding

Where is "ildasm" in Visual Studio 2019?

I used to be able to run ildasm in the Developer Command Prompt for Visual Studio 2017. With Visual Studio 2019, ildasm is no longer available:
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community>ildasm
'ildasm' is not recognized as an internal or external command,
operable program or batch file.
Was it replaced with something else or is my VS 2019 installation incomplete?

ildasm.exe is installed with the Windows SDK tools, located in C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.6.1 Tools\ildasm.exe or somewhere similar depending on the version.
You can install the SDK from this website or by selecting it in the optional components during the installation of VS2019.

Try to use it directly from Developer Command Prompt 2019/2017

I have installed VS 2017. But the installer can't find it, which results in that I can't update and uninstall them

This is my Visual Studio UI and installer:
Then, I try to open the installer from Visual Studio. But it shows an error message:
I think that there is no specific path of the vs in its config files. However, I failed to find it. Please share your advice and a solution for this. Thanks.

Let's try this way
- Open CMD with admin privilage and go to this path
cd /d c:\program files (x86)\microsoft visual studio\installer
Depend on which version of visual studio you have installed (Enterprise, Community or Professional) type :
for Enterprise
vs_installershell.exe repair --installPath="C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise"
for Community
vs_installershell.exe repair --installPath="C:\Program Files (x86)\Microsoft Visual Studio\2017\Community"
for Professional
vs_installershell.exe repair --installPath="C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional"
here is the source it has worked for some users
https://developercommunity.visualstudio.com/content/problem/313423/missing-option-value-installpath.html

Project could not be opened because the Visual C# 2015 compiler could not be created. Please re-install Visual Studio

I have a Windows 10 PC on which I have installed VS 2012, VS 2015, and VS 2017.
The solution was created for 2015 platform toolset. When I open the solution in VS 2017, and try to build it, it works fine.
If I open it in VS 2015, and build it, that also works.
But when I try to build it using:
"C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv.exe" [link to .sln file] /Build "Release|Win32" /Out "build.log"
I get the error message:
Project 'URCSLogger' could not be opened because the Visual C# 2015 compiler could not be created. Please re-install Visual Studio.
I tried everything in this fix but nothing worked. Any tips?

Have you tried MsBuild.exe [Path to your solution(*.sln)] /t:Build /p:Configuration=Release;Platform=x86 ?
See MSDN documentation here: https://msdn.microsoft.com/en-us/library/ms164311.aspx
Please ensure you have Release | x86 configuration settings in your solution. See How do I specify the platform for MSBuild?
Hope this helps.

VS2017 command line build (missing "%VS150COMNTOOLS%VSVars32.bat")

I have installed VS2017 and call
call "%VS120COMNTOOLS%VSVars32.bat"
from the command line but all I get is
'"%VS150COMNTOOLS%VSVars32.bat"' is not recognized as an internal or external command, operable program or batch file.
If I run "set" from the command line I can see VS120COMNTOOLS (for VS2013) & VS140COMNTOOLS (for VS2015) but there is no VS150COMNTOOLS. How can I build from the command line?

I submitted this as a tech support issue to Microsoft who accepted it as a bug in the install ("there is no VSVars32.bat in the C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\Tools directory.").
However, there is a work-around:
From MS:
At least, since there is a VsDevCmd.bat, there is a Visual Studio 2017 Developer Command Prompt, which also sets, modifies environment variables (Framework40Verion, FrameworkDir, FrameworkDIR64, FrameworkVersion, FrameworkVersion64, INCLUDE, IPCPATH, PATH, VCINSTALLDIR, VCToolsInstallDir, ...)
C:\Program Files (x86)\Microsoft Visual Studio\2017\EDITION\Common7\Tools\VsDevCmd.bat
Run C:\Program Files (x86)\Microsoft Visual Studio\2017\EDITION\Common7\Tools\VsDevCmd.bat where EDITION is the type of VS2017 install, i.e. C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\Tools\VsDevCmd.bat for the Enterprise install. This sets up the needed environment variables and batch builds will work.
Hope this helps anyone struggling with the same issue.

VS2017 has reworked its directory structure and filenames. The file is no longer titled "VsVars32.bat", you should look for the file 'vcvars.bat', which can be located in ..\Program Files (x86)\Microsoft Visual Studio\2017\EDITION\Common7\Tools\vsdevcmd\ext\vcvars.bat (using Adam's syntax, replace EDITION with the version of Visual Studio you use).
For simplicity, you can use %VSAPPIDDIR% in your call to point to the IDE folder where devenv.exe is located, and go back one folder to define your path to the batch file. For example:
call "%VSAPPIDDIR%..\Tools\vsdevcmd\ext\vcvars.bat"

If its any help to anyone...
If you modify your Visual Studio 2017 installation to install the component:
"VC++ 2015.3 v140 toolset for Desktop (x86,x64)"
then the 'VSVars32.bat' file which is missing, will be installed (as its a component of VC++ 2015, but not VC++ 2017).

How can I fix the Microsoft Visual Studio error: "package did not load correctly"?

I installed Visual Studio 2012 and DevExpress 13.1. As Visual Studio started, it generated an error shown by this attached image,
The 'Microsoft.VisualStudio.Editor.Implementation.EditorPackage' 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 examining the file 'C:\Users\must\AppData\Roaming\Microsoft\VisualStudio\11.0\ActivityLog.xml'.
Continue to show this error message?
This error also appears in Visual Studio 2017.

I started to see this on a fresh Windows and Visual Studio 2013 Ultimate with Update 2 installation (although others have also reported it on Updates 3 and 4, as well as the Professional version).
To resolve the problem, close all Visual Studio instances, then delete all files in the following folder:
Visual Studio 2013
%localappdata%\Microsoft\VisualStudio\12.0\ComponentModelCache
It worked fine for me. Thanks to this article.
Visual Studio 2015
%localappdata%\Microsoft\VisualStudio\14.0\ComponentModelCache
Visual Studio 2017
%localappdata%\Microsoft\VisualStudio\15.0_xxxx\ComponentModelCache
Visual Studio 2019
%localappdata%\Microsoft\VisualStudio\16_xxxx\ComponentModelCache
Visual Studio 2022
%localappdata%\Microsoft\VisualStudio\17_xxxx\ComponentModelCache

I encountered this problem in Visual Studio 2017 (15.7.4). After trying various solutions, eventually this worked for me: close all Visual Studio instances, and run this from the command line (possibly with administrator rights):
devenv.exe /clearcache
devenv /updateconfiguration

Close Visual Studio.
Backup and delete the following path:
C:\Users\{your_username}\AppData\Roaming\Microsoft\VisualStudio\11.0
Restart Visual Studio as Admin. Otherwise, the Roaming folder can't be repaired by Visual Studio.

Try devenv /setup on the Visual Studio Command Prompt with administrative rights.
I had the same problem with Visual Studio 2013 Ultimate. I tried the solution by Reza posted here, but it didn't work.
Eventually I couldn't close Visual Studio. It was showing a similar dialog when I tried to close, and it wasn't closing. I tried this: Error message "No exports were found that match the constraint contract name". Neither.
I noticed a message in the Team Explorer window saying "Page 'somenumber' cannot be found". I tried that way, and I found this answer: Page '312e8a59-2712-48a1-863e-0ef4e67961fc' not found using Visual Studio 2012. So I run devenv /setup on the Visual Studio Command Prompt with administrative rights.
It did the job, and everything is fine now.

Solution for Visual Studio 2017:
Step 1: open Visual Studio cmd in administrator mode (see start menu item: Developer Command Prompt for VS 2017 - Be sure to use: Run as administrator)
Step 2: change directory to the folder where Visual Studio 2017 is installed, for example:
cd C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise
(You can copy/paste this command to your cmd prompt. For Visual Studio Professional, the folder will be called "Professional" instead of "Enterprise", etc.)
Step 3: copy/paste the below command
gacutil -if Common7\IDE\PublicAssemblies\Microsoft.VisualStudio.Shell.Interop.8.0.dll
Hit Enter...
It will resolve the issue...
Otherwise, you can also add the following to the GAC as above:
Microsoft.VisualStudio.Shell.Interop.9.0.dll
Microsoft.VisualStudio.Shell.Interop.10.0.dll
Microsoft.VisualStudio.Shell.Interop.11.0.dll

I had a similar problem, and I went to Control Panel → Programs and repaired the Visual Studio installation. It worked for me.

I had the same problem. Try to remember the latest extension that you installed. I delete the latest extension from extensions and updates and restart Visual Studio. and the problem is solved. For me, the extension name is Productivity Power Tools

I had a similar issue (Tizen Project type package did not load correctly) with Visual Studio 2017.
After trying all the answers above, and spending a few hours searching for a solution for the errors inside ActivityLog.XML, nothing worked for me.
Eventually, the solution was a Visual Studio Repair.
I assume that the repair process overrides some configurations that caused the problem.
Repair Visual Studio 2017
Repair Visual Studio 2019

I also experienced this issue after installing Telerik Reporting. I was not able to launch any solution in Visual Studio 2013, nor could I close Visual Studio 2013.
After uninstalling the reporting package and deleting Local / Roaming AppData for Visual Studio 2012, the problem was fixed.

In my case the error message is "The 'IntelliCodeCppPackage' package did not load correctly" (Visual Studio 2019):
I solved this is issue with these steps;
Disable the Visual Studio IntelliCode extension
Restart Visual Studio
Enable that extension again

I tried everything except the repair. I even did an update. This is what fixed it for me:
Open "Developer Command Prompt for VS 2017" as Admin
CD into (your path may vary) CD C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\PublicAssemblies
Run command gacutil -i Microsoft.VisualStudio.Shell.Interop.11.0.dll
Restart Visual Studio

Based on this Connect feedback I fixed it by closing all opened documents and restarting Visual Studio. I use Visual Studio 2015.

You need to find file devenv.exe.config in C:\Users\{user_name}\AppData\Local\Microsoft\VisualStudio\14.0\ and update it. (Or C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\, depending on the location of your devenv.exe file.)
For this particular case, you should find rows that setup redirects for System.Collections.Immutable and change newVersion from 1.1.36.0 to 1.1.37.0.
The original article is How to restore Visual Studio 2015 after the Update 1 (dependency dance).

I had this problem, and projects were not loading correctly or stating that they needed migration. The ActivityLog.xml showed an error with a particular extension. I uninstalled the extension and restarted Visual Studio. That resolved the issue.

I also experienced the same error, "NPM package not installed correctly",
while creating a Node.js project in Visual Studio 2015.
I resolved my issue by performing two steps:
Delete all files present in this location:
C:\Users\<Your User Name>\AppData\Local\Microsoft\VisualStudio\14.0\ComponentModelCache
Restart Visual Studio.
Open Visual Studio and go to menu Tools → NuGet Package Manager → Package Manager Settings →
On the left side: You will see a drop down list: select Node.js, Tools → Npm → ClearCache → *OK
Then again try to create the project. It resolved my issue.

I had the pleasure of experiencing this random problem in Visual Studio 2017 Enterprise.
I tried every solution here, and it didn't work, including the Visual Studio repair (which takes a while). Several hours in, I thought maybe I should actually check the ActivityLog.xml file.
I uninstalled the offending extension from the 'Developer Command Prompt for VS2017' as an administrator since Visual Studio just freezed after open and nothing could be clicked.
Steps to uninstall - courtesy of jessehouwing.net
Find the vsix file you used to install the extension.
Open it in your favorite archiver (mine is 7-Zip).
Grab the extension's Id from the Identity node from the extension.vsixmanifest.
Run (in my case) vsixinstaller /u:Microsoft.VisualStudio.LiveShare to remove the extension.

Find the ComponentModelCache folder
Delete Microsoft.VisualStudio.Default.cache
Restart Visual Studio
Enjoy using Visual Studio.

I had a similar problem.
After checking ActivityLog.xml and it said that it could not create an instance for the Extension/package name from a specific folder. I traced that path and I didn't find that folder it is looking for.
So I installed the extension again, I looked for the dll, and copied the containing folder contents to the folder Visual Studio is looking for.
So to recap:
Check if the folder in the error exists
If not, create a new folder with the same name
Look for the dll in the error in the Visual Studio folder, if not found, install the extension again
If the error resists, search inside the Visual Studio folder in Program Files (x86) for the dll and open the containing folder
Copy all the contents
Paste inside the new folder you have created with the name mentioned inside the ActivityLog.xml

Firstable, you need to be sure have the last Microsoft .NET Framework version, in my case, I had the 4.6 version and I have downloaded and updated the .NET Framework 4.8.03761 Developer Pack, from the official site:
https://dotnet.microsoft.com/download/dotnet-framework/net48
Once I restarted my PC, to continue fixing that, I solved this problem by clearing Visual Studio Component Model Cache.
Just delete or rename this folder:
%LocalAppData%\Microsoft\VisualStudio\11.0\ComponentModelCache
or
%LocalAppData%\Microsoft\VPDExpress\11.0\ComponentModelCache
and restart Visual Studio.

Since this is the top SO result in google for this issue, I'm going to leave my fix here for VS 2022 when experiencing this issue. I found it is commonly caused by an extension issue. In my particular case TypeScript Definition Generator was causing the issue and removing the extension solved it. To find which extension could be causing the issue, run VS with the /Log command line switch.
i.e.: "C:\Program Files\Microsoft Visual Studio\2022\Community\Common7\IDE\devenv.exe" /Log
After the error occurs, close VS and locate ActivityLog.xml found at %AppData%\Microsoft\VisualStudio\<version>\ActivityLog.xml. Search the log for any extensions reporting an error and uninstall it.

I just wanted to mention that I got a similar error in SQL Server Management Studio 2016, where I basically ignored it. Later, I launched Visual Studio (2015), and this error occurred there as well.
I searched and found the answer here recommending that files be deleted from the
%localappdata%\Microsoft\VisualStudio\14.0\ComponentModelCache
folder. However, in my case, this folder was empty.
Since I remembered that I saw the error in Management Studio first, I checked, and there was a similar folder at
%localappdata%\Microsoft\SQL Server Management Studio\13.0\ComponentModelCache
This folder was not empty. I closed both Visual Studio and Management Studio, and deleted the files from this folder.
Afterwards, both Management Studio and Visual Studio launched without error.

I had this problem after installing Crystal Reports for Visual Studio. I solved it by closing all Visual Studio instances and reinstalling Crystal Reports.

I solved it:
Go to install
Modify
Go to "Installation location" tab
Check "keep download cache after the installation"
Modify

My issue was Mysql connector net 6.4.4, Nuget, xamarin, VSPackage, EditorPackage and etc.. package did not load correctly.
My solution is below for vs2015
Open AppData location // all the configurations are updating on it.
Backup and Remove the folder in which configuration error is thrown in the visual studio.
forex. If you have Nuget package did not load correctly error - Remove Nuget folder in Local and Roaming directories.
And also clear the data on AppData/Microsoft/visual Studio/14.0 for vs2015
that's it and it worked for me!...

For Visual Studio 2019: I have done the following things to solve the problem
Backup the following Folder. After Taking backup and Delete This Folder C:\Users\munirul2537\AppData\Roaming\Microsoft\VisualStudio\16.0_add0ca51
Go to the installation panel of visual studio and do the following things
1.Go to install
2.Modify
3.Go to "Installation location" tab
4. Check "keep download cache after the installation"
5. Modify

For Visual Studio 2017, 2019. I got this error and able to fix it just by enable the Live Share extension from extensions.
see the VS community page for detail.

For others that have a similar problem but with live share.
In the visual studio installer there was a warning that live share was not installed correctly and a modification was pending, that would download live share again.
After completion of the modification the error was resolved.

I had the same problem for Visual Studio 2019 v16.8.6. It was fixed after repair Visual Studio from Visual Studio Installer.

After trying lots of options this worked for me (VS 2019):
Launch Developer Command Prompt for VS 2019 (Run as Administrator)
cd "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\PublicAssemblies" Replace Community with your specific distribution.
Execute the next line: gacutil -i Microsoft.VisualStudio.Shell.Interop.11.0.dll

One more solution that worked for my colleague after trying all the others that did not work (for Visual Studio 2022).
Try this:
Close all instances of Visual Studio
Go to: C:\Program Files (x86)\Microsoft SDKs\Windows
You should see a number of vX.0-like directories (e.g. v10.0A for Visual Studio 2022 Enterprise). Back-up and remove all those directories except the one matching your Visual Studio (in my case I'd remove everything except v10.0A).
Start Visual Studio. The "package did not load correctly" warning will be gone.
Rationale:
If you had older versions of Visual Studio installed previously, they will come with their own NETFX Tools which might not uninstall correctly together with those older instances of Visual Studio. The new Visual Studio will for some reason pick the old Tools and fail using them. Removing the redundant directories fixes it.