Today I selected "Work Items" as I have a million times before but this time I was met with this error along the top of my "Team Explorer" tab:
"Page [some long GUID] not found."
This also happened for "Pending changes".
To fix the issue simply run the below command in an elevated command prompt as detailed here.
"C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\devenv.exe" /setup
My understanding is this command forces the recreation (what Microsoft refers to as "merging") of current VS settings into what is apparently a corrupt settings cache. On the surface, this is similar to deleting the directory path C:\Users\username\AppData\Local\Microsoft\VisualStudio\version and allowing visual studio to recreate it at launch. However, I prefer to not to delete this outright and instead rely on re-merge approach.
Recently I found this sometimes occurs when I launch several solutions at once (i.e. I have 1 or more Visual Studio instances loading a solution at the same time). I also have ReSharper, SQL Prompt, VSCommands and TFS Power Tools installed which I'm sure contribute to some degree.
UPDATE:
This fix should work for all versions of Visual Studio, however you will need to execute the command in the directory appropriate to your version. For example with Visual Studio 2015 the path would be:
"C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv.exe" /setup
Version mappings for Visual Studio (original version mapping answer here):
Visual Studio 2005 = 8
Visual Studio 2008 = 9.0
Visual Studio 2010 = 10.0
Visual Studio 2012 = 11.0
Visual Studio 2013 = 12.0
Visual Studio 2015 = 14.0
Visual Studio 2017 = Path has changed to: "C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE"
Deleting all files in ComponentModelCache folder worked for me
For Visual Studio 2013:
"C:\Users\username\AppData\Local\Microsoft\VisualStudio\12.0\ComponentModelCache"
For Visual Studio 2015:
"C:\Users\username\AppData\Local\Microsoft\VisualStudio\14.0\ComponentModelCache"
or
%userprofile%\AppData\Local\Microsoft\VisualStudio\14.0\ComponentModelCache
If you get this issue in VS2015 and running "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv" /setup doesn't fix you issue you can try the following:
Close all instances of VS
Delete all files in C:\Users\\AppData\Local\Microsoft\VisualStudio\14.0\ComponentModelCache
run "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv" /setup
This happend also with my installation of VS '13 when I installed VS '15.
Removing the files at
"C:\Users\username\AppData\Local\Microsoft\VisualStudio\12.0\ComponentModelCache"
did the job for me.
I encounter the same problem with you, and resolved by run the VS as administrator
Here are the steps I followed. Please make sure you follow them in correct sequence. These steps are for VS 2015. Use 12.0 (instead of 14.0) for VS 2013 and 10.0 for VS 2010
Close all instances of VS
Delete all files in C:\Users{UserName}\AppData\Local\Microsoft\VisualStudio\14.0\ComponentModelCache
Delete the folder C:\Users{UserName}\AppData\Roaming\Microsoft\VisualStudio\14.0
run "C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv" /setup in a command prompt as administrator
I've installed Visual Studio 2012 Release Preview, and it appears to be fine, but now when I try to use Visual Studio 2010 to compile C++ projects, I get the following error message:
LINK : fatal error LNK1123: failure during conversion to COFF: file invalid or corrupt
I'm not 100% sure of this, but it seems to be related to projects that have .rc (resource) files in them.
I've tried repairing Visual Studio 2010 from Add/Remove programs and rebooting, but this has no effect.
I also get the same error if I use Visual Studio 2012 RC to compile the C++ projects when set to use the Visual Studio 2010 toolset. Upgrading to the Visual Studio 2011 toolset fixes the problem (but of course I don't want to do this for production code).
Update: I've uninstalled Visual Studio 2012, rebooted, and the problem still persists! Help!
This MSDN thread explains how to fix it.
To summarize:
Either disable incremental linking, by going to
Project Properties
-> Configuration Properties
-> Linker (General)
-> Enable Incremental Linking -> "No (/INCREMENTAL:NO)"
or install VS2010 SP1.
Edits (#CraigRinger): Note that installing VS 2010 SP1 will remove the 64-bit compilers. You need to install the VS 2010 SP1 compiler pack to get them back.
This affects Microsoft Windows SDK 7.1 for Windows 7 and .NET 4.0 as well as Visual Studio 2010.
If disabling incremental linking doesn't work for you, and turning off "Embed Manifest" doesn't work either, then search your path for multiple versions of CVTRES.exe.
By debugging with the /VERBOSE linker option I found the linker was writing that error message when it tried to invoke cvtres and it failed.
It turned out that I had two versions of this utility in my path. One at C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\BIN\cvtres.exe and one at C:\Windows\Microsoft.NET\Framework\v4.0.30319\cvtres.exe. After VS2012 install, the VS2010 version of cvtres.exe will no longer work. If that's the first one in your path, and the linker decides it needs to convert a .res file to COFF object format, the link will fail with LNK1123.
(Really annoying that the error message has nothing to do with the actual problem, but that's not unusual for a Microsoft product.)
Just delete/rename the older version of the utility, or re-arrange your PATH variable, so that the version that works comes first.
Be aware that for x64 tooling builds you may also have to check C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\amd64 where there is another cvtres.exe.
Check the version of cvtrs.exe:
dir "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\cvtres.exe"
Wrong version:
date: 03/18/2010
time: 01:16 PM
size: 31,048 bytes
name: cvtres.exe
Correct version:
date: 02/21/2011
time: 06:03 PM
size: 31,056 bytes
name: cvtres.exe
If you have wrong version you should copy the correct version from:
C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\bin\cvtres.exe
and replace the one here:
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\cvtres.exe
i.e.
copy "C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\bin\cvtres.exe" "C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\cvtres.exe"
According to this thread in MSDN forums: VS2012 RC installation breaks VS2010 C++ projects, simply, take cvtres.exe from VS2010 SP1
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\cvtres.exe
or from VS2012
C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\bin\cvtres.exe
and copy it over the cvtres.exe in VS2010 RTM installation (the one without SP1)
C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\cvtres.exe
This way, you will effectively use the corrected version of cvtres.exe which is 11.0.51106.1.
Repeat the same steps for 64-bit version of the tool in C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\amd64\cvtres.exe.
This solution is an alternative to installation of SP1 for VS2010 - in some cases you simply can't install SP1 (i.e. if you need to support pre-SP1 builds).
If you have installed Visual Studio 2012 RC, then it installed .NET 4.5 RC.
Uninstall .NET 4.5 RC, and install the version you need (4.0 for VS 2010). This should clear up any problems you are having.
This solved the same problem. There is no need to uninstall Visual Studio.
It's because of .NET Framework 4.5 is replacing .NET Framework 4.0.
I uninstalled Visual Studio 2010 several times with no luck. When I removed .NET Framework 4.5 and reinstalled Visual Studio 2010 it went fine.
See Uninstall Visual Studio 11 completely to do a fresh install.
For me, setting 'Generate Manifest' to 'No' fixed it. (Also fixed with /INCREMENTAL:NO)
If you're using x64, here's a resource will help:
This happens because Microsoft .NET 4.5 is incompatible with Visual C++ 10. The workaround is to ensure that you run the .NET version of cvtres.exe rather than the Visual C++ version. I did this by renaming the Visual C++ versions of those files and copying the .NET versions in their place.
1. C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\cvtres.exe
2. C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin\amd64\cvtres.exe
1. C:\windows\Microsoft.NET\Framework\v4.0.30319\cvtres.exe
2. C:\windows\Microsoft.NET\Framework64\v4.0.30319\cvtres.exe
I solved this problem eventually by doing a full uninstall of VS2012 RC, followed by a full uninstall of VS2010, then a reinstall from scratch of VS2010.
It took forever, but I'm now able to compile C++ projects in VS2010 again.
The issue was magically resolved for me by removing .NET 4.5, and replacing it with .NET 4.0. I then had to repair Visual Studio 2010 - it being corrupted along the way somehow.
I had previously installed, and then un-installed, Visual Studio 2012 - which may be related to the issue.
I have not installed Visual Studio 2012, but I still got this error in Visual Studio 2010. I got this resolved after installing Visual Studio 2010 SP1.
I had the same problem with Microsoft Visual Studio 2010 Ultimate and it was solved by the method described in this youtube video
The video suggests to rename the file cvtres.exe in C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin (in my Win7X64 matchine) to cvtres-old.exe
It didn't work for me after Enable Incremental Linking -> "No (/INCREMENTAL:NO)", but it works for me after I deleted the rc file.
+1 to user Short for an answer that worked for me!
I tried to do some debugging of this with msbuild /v:diag, and I'm seeing that MSBuild is trying to embed a manifest in the executable, with <somename>.dll.embed.manifest.res on the linker command line, where that is a resource file built from <somename>.dll.embed.manifest. But the manifest file is an empty Unicode text file. (That is, a two-byte file with the Unicode 0xFEFF prefix)
So the root problem seems to have something to do with that manifest file not being generated, or it being used when <somename>.dll.intermediate.manifest should have been used.
An alternate solution seems to be to turn off the "Embed Manifest" option under Properties, Manifest Tool, Input and Output.
To summarize:
Step1
Project Properties
-> Configuration Properties
-> Linker (General)
-> Enable Incremental Linking -> "No (/INCREMENTAL:NO)"
if step1 not work, do Step2
Project Properties
-> Configuration Properties
-> Manifest Tool (Input and Output)
-> Enable Incremental Linking -> "No"
if step2 not work, do Step3
Copy file one of:
C:\Program Files (x86)\Microsoft Visual Studio
11.0\VC\bin\cvtres.exe
C:\Program Files (x86)\Microsoft Visual Studio
12.0\VC\bin\cvtres.exe
C:\Program Files (x86)\Microsoft Visual Studio
13.0\VC\bin\cvtres.exe
Then, replace to C:\Program Files (x86)\Microsoft Visual Studio
10.0\VC\bin\cvtres.exe
With me, do 3 step it work
As of January 2014, for some reasons I got installed .NET Framework 4.5.1, I don't know if due to a third party software installation or to an automatic update.
On January 29th, I got installed one component and I started receiving the
LINK : fatal error LNK1123: failure during conversion to COFF: file invalid or corrupt
message. At that time, I solved by avoiding the incremental link.
On Jan. 31st, I got installed another component of .NET Framework 4.5.1 and the incremental link trick did not work anymore. I then installed the Visual Studio 2010 SP1, but afterwards the problem became:
Error 6 error LNK1104: cannot open file 'msvcrtd.lib'.
I think the SP1 messed up my Visual Studio 2010 installation.
So I uninstalled .NET Framework 4.5.1, installed .NET Framework 4.0 and uninstalled and then reinstalled Visual Studio 2010. That worked for me.
Even inspite of installing Service pack you are getting the error then try removing/renaming the cvtres.exe in the C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\bin folder. This has worked for me.
I set Enable Incremental Linking to "No (/INCREMENTAL:NO)" and it doesn't work for me.
Next I've changed:
Project Properties
-> Configuration Properties
-> General
-> Platform Toolset -> "Visual Studio 2012 (v110)"
and it works for me :)
Reinstalling CMake worked for me. The new copy of CMake figured out that it should use Visual Studio 11 instead of 10.
I was using the Windows SDK for core Win32 programming and had .NET 4.5 installed for "unknown" reasons. I have uninstalled that and installed 4.0 like previous answers and yeah, it worked for me too.
Just am flabbergasted that I had to use the useless .NET framework for building Win32 apps using the SDK.
I solved this by doing the following:
In a command prompt, type msconfig and press enter.
Click services tab.
Look for "Application Experience" and put tick mark (that is, select this to enable).
Click OK. And restart if necessary.
Thus the problem will go forever. Do build randomly and debug your C++ projects without any disturbance.
For those of you looking for a solution for this problem with the OpenGL SuperBible 6th source code samples, the solution is building in Release instead of Debug. All projects have disabled the incremental linking option in the Release version.
My problem was that I've had two paths on my PC that contained the same libraries. Both paths were added to the Additional Library Directories in Configuration Properties -> Linker -> General. Removing one of the paths solved the problem.
I had the same problem after updating of .NET:
I uninstalled the .NET framework first,
downloaded visual studio from visualstudio.com and selected "repair".
NET framework were installed automatically with visual studio -> and now it works fine!
I tried a few times and finally solved the problem by uninstalling several times the VS2010. I think I hadn't uninstalled all the files and that's why it didn't work for the first time.
In the installation of VS2012, it is said that if you have VS2010 SP1 you can't work on the same project in both programs. It is recommended to have only one program.
Thanks!
I just installed VS11 professional version on windows 8 consumer preview OS.
I tried to create a win32 console app, wizard fails with following error:
Microsoft Visual Studio
'C:\Program Files\Microsoft Visual Studio 11.0\VC\VCWizards\default.vcxproj' cannot be opened because its project type (.vcxproj) is not supported by this version of the application.
To open it, please use a version that supports this type of project.
OK
Not sure what i'm missing. Anyone here can help me?
Here's what fixed it for me, check your User environment variables for VCHOME, VCINSTALLDIR and vsinstalldir.
Change
X:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\
to
X:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\
Or
X:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\
depending VS 2012 or 2013.
Couldn't find the answer. Re-installation of VS11 fixed the issue.
Run VS2011 first and than drag and drop project file in it. That helped me.
For those who come to this thread with the same problem but for VS2015: installing Visual Studio 2015 Update 1 fixed the problem for me.
I've installed ReSharper 5 on two installations of Visual Studio 2010 Professional. In both cases, ReSharper claims it has installed successfully - but Visual Studio doesn't recognize the extension. It doesn't show up in the Extensions Manager, doesn't appear in Help - About - Installed products, and can't be found anywhere else in the environment.
I've tried install / uninstall of both Visual Studio and ReSharper, computer restarts, etc. Both machines have Visual Studio 2008 and ReSharper 5 works fine in these IDEs, and both machines are running Windows 7.
I've found other people online with this issue, but no solutions. Anyone know how to fix this?
Check that ReSharper is enabled in Tools->Options->ReSharper. Suspend and unsuspend it, in case that helps (I've heard that work before). Note that ReSharper will notice if more than one computer on a given network is running the same license, and disable all but one of the instances that are running. Check that hasn't happened to you.
Run devenv /resetskippkgs, solved my issues in Visual Studio 2008
I've fixed the problem by just copying the JetBrains folder from other version of Visual Studio:
This is visual studio 2010 folder for extensions:
c:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\
This is visual studio 2012 folder for extensions:
c:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\Extensions\
I just copied from 2012 folder the 'JetBrains' and pasted to the 2010 extensions folder.
I can't publish in 2008, I was previously using 2005 and it published just fine.
Error 2 An error occurred while signing: SignTool.exe not found.
I know there are tons of hits for a search on signtool.exe on google. The ones I've found involve copying the file to X,Y,Z locations and ensuring signtool matches up with your VS command prompt path.
When I run my start-> program files -> visual studio 2008 -> Visual Studio Tools -> Visual Studio Command prompt. and type signtool.exe it finds the file just fine.
I have Visual Studio 2005 professional edition, Visual studio 2008 profession edition,
Visual studio 2005 SDK February 2007, just installed Visial Studio 2008 SDK1.1 to see if that would fix it, no luck.
I have copied signtool.exe to lots of places that were suggested on the google searches, it is now located at all of the following:
C:\Program Files\Visual Studio 2005 SDK\2007.02
C:\Program Files\Microsoft Visual Studio 9.0\Common7\Tools
C:\Program Files\Microsoft Visual Studio 9.0\VB\Bin
C:\WINNT\Microsoft.NET\Framework\v3.5
C:\Program Files\Microsoft SDKs\Windows\v6.0A\Bin
C:\Program Files\Microsoft Visual Studio 8\Common7\Tools\Bin
C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bin
C:\Program Files\Microsoft Visual Studio 9.0\SDK\v3.5\Bin
C:\Program Files\Microsoft Visual Studio 9.0\VB\Bin\1033
C:\Program Files\Visual Studio 2005 SDK\2007.02\VisualStudioIntegration\Tools\Bin
I'm on windows XP
2009-06-12 update
I can only publish if I copy signtool.exe to the project folder I'm publishing now.
Replace signtool with "$(FrameworkSDKDir)bin\signtool" with the quotes and see if it works. It tried this now on Visual Studio 2008 Express Edition.
N.B: I have been using same command on VS 2005 for signing the binaries.
This may help some one else....
I got round this problem by going to the signing tab and unchecking the Sign The ClickOnce Manifests option and now it works...
I guess that doesn't FIX the problem..but it gets around it allowing you to publish your application with out the Signtool.exe File.
This may help some one else.... I got round this problem by going to the signing tab and unchecking the Sign The ClickOnce Manifests option and now it works...
that one doesn't worke for me, because every time I uncheck the signing (and save the config) Visual Studio checks it back on.