I've Visual Studio 2017 community edition. I have a C# project created using Visual Studio 2015. When I try to open the project in VS 2017 I get an error message prompt:
--------------------- Microsoft Visual Studio
Project 'dataStructureInCSharp' could not be opened because the Visual C# 2017 compiler could not be created.
Please re-install Visual Studio.
--------------------------- OK
I'm trying to obtain help if anyone else has faced similar issue. I feel going the uninstall and then reinstall route is very costly for me and would try that option last if I've got no other resort.
What I've done so far :
Tried starting visual studio with administrative privileges
But problem remained same.
I tried creating a new console project solution from scratch but in that case I get very same error and an additional error error also shown below:
System Environment: Windows 7 Ultimate Service Pack 1
You can try to close all VS 2017 instances and delete the folder %localappdata%\Microsoft\VisualStudio\15.0_xxxx\ComponentModelCache, then open VS to create a new Console project.
Or
please re-run the VS 2017 installer as administrator, click the icon beside ‘Launch’ button and choose ‘Repair’ to repair as shown below:
Just to brief the history of my problem, I had first installed Visual Studio(VS) 2017 community when it was in RC stage. This was first time when I saw the workload based UI of visual studio installation. Initially I simply chose .Net desktop development workload to get started as I was interested in creating only console applications to get my hands dirty.
Initially it was all working well. One fine day I added all other workloads I was interested in namely Universal Windows Platform Development, Azure Development, ASP.NET and web development,Node.js development, and Mobile development with .Net. I'm not sure if there any of the specific workloads to be blamed for the issue I've posted.
Just to avoid the case if RC and RTM release builds might not have messed up my entire environment, I simply uninstalled the entire stuff, rebooted my machine and installed it again from scratch from latest RTM release for Visual Studio Community.
I would strongly recommend that you first try possible solutions suggested by #Sara-MSFT before doing clean reinstall just in case if it works. It can save you couple of hours required in whole reinstallation process if it works.
I have created a new C# project using a Word 2013 and 2016 VSTO Add-in template in Visual Studio 2015. I have not done any changes to the auto-generated project code in order to see how it will be built on my TFS 2015 Build Server. The build produced the following error:
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\OfficeTools\Microsoft.VisualStudio.Tools.Office.targets (315, 0)
The "SetOffice2007AddInRegistration" task failed unexpectedly.
System.Runtime.InteropServices.COMException (0x800703F0): An attempt was made to reference a token that does not exist. (Exception from HRESULT: 0x800703F0)
at Microsoft.VisualStudio.Tools.Office.Runtime.Interop.VSTOEENativeMethods.GetVSTOEEHandle()
at Microsoft.VisualStudio.Tools.Office.Runtime.Interop.VSTOEENativeMethods.GetSolutionMetadata(String solutionInfoString)
at Microsoft.VisualStudio.Tools.Applications.OfficeSolutionMetadata..ctor(String manifestLocation)
at Microsoft.VisualStudio.Tools.Office.Runtime.AddInRegistryKeyManager.RegisterAddIn(Uri manifestUri, String addInName, String officeApplication, String friendlyName, String description, Int32 loadBehavior, String compatibleFrameworkXML, Boolean runLocal)
at Microsoft.VisualStudio.Tools.Office.BuildTasks.SetOffice2007AddInRegistration.Execute()
at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
at Microsoft.Build.BackEnd.TaskBuilder.d__26.MoveNext()
The Build Service is run as a domain account which is an administrator of the Windows Server 2012 where the Build Service is installed. The Visual Studio 2015 and Office 2016 are installed on this Windows Server.
When I build the project in Visual Studio 2015 on my local pc I have no errors at all.
Please, help if you experienced the same problem in your work. Thank you.
This issue is not TFS related.
But I found a solution from Jens at this website, which should help you:
"
According to the MSDN Library SetOffice2007AddInRegistration "Defines an MSBuild task that creates or removes registry keys that are needed to run or uninstall an add-in for the 2007 Microsoft Office system." So I checked the registry and figured out that the only entries that were still present were the ones under HKEY_CURRENT_USER\Software\Microsoft\VSTO\SolutionMetadata where VSTO caches metadata for solutions. I deleted all keys and subkeys (your existing solutions will still work, it's just cached metadata) and my solution compiled successfully.
"
As I have spent significant chunk of my time trying to resolve this error and getting to nowhere, I would like to share my experience with other people. I have a suspicion that MSBuild has a bug when it is run for XAML build definitions of Office Addin projects.
I created a brand new Word 2016 Addin project in Visual Studio 2015. No custom code. The project had only auto generated code. The Visual Studio built the project with no errors. I run the build with the MSBuild Diagnostic output Verbosity option selected.
After that, I run the MSBuild program from the command line with the same parameters that TFS Build Server run the build. The only difference was the the Diagnostic verbosity log option to create a detailed log. I compared two logs produced by Visual Studio and MSBuild. The MSBuild log indicated that workflow never got to the step of unregistering the Addin. Actually, it tried to register the Addin without unregistering. The Visual Studio log showed that the Visual Studio build unregistered the Addin and registered it after that successfully.
Learning the TFS 2015 features, I found out about Agent Pool and Build Agents. I realized that instead of running MSBuild for XAML defined builds, the TFS 2015 Build Agents use Visual Studio to build the application. So, I set up the Agent Pool and Build agent on my build server and, voila, the Addin was built successfully!
The conclusion is if you have XAML defined build for your Addin project, do not use it in TFS 2015. Create a new TFS build definition using Agent Pool features provided in TFS 2015. This will guarantee that your build will be done on TFS build server exactly like on your PC in Visual Studio environment.
I have a problem that when I try to open to create a new C# project in either VS 2013 or 2015, I get an error saying that the program has stopped working then it restarts. I tried disabling .Net Framework 3.5, but it didn't help, also I tried repairing it through the control panel, but it didn't help either. What shall I do?
Uninstall and do a fresh reinstall? – Jacobr365
I DID uninstall Visual Studio 2013 before installing 2015.
Clearing the component cache fixes some issues with Visual Studio: Delete C:\Users[User]\AppData\Local\Microsoft\VisualStudio[Version]\ComponentModelCache or try starting in Safe Mode first: C:\Program Files (x86)\Microsoft Visual Studio [Version]\Common7\IDE\devenv.exe /safemode – Mark
I tried both, but it didn't help.
Thanks
You should uninstall both 2013/2015
With related packages (.net, sql...)
Then reinstall it
Warning: do this only if anything else doesn't worked
I have had this issue before, Use iobit uninstaller or as mention above Ccleaner to fully remove all secondary packages, If you use iobit then when you uninstall it will give you the option to completely clean it from the registry. Restart machine and install again, try install from the web installer. If problem persists then you will most likely have to reinstall your windows OS.
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.