I guess, this happened after recent update to Visual Studio 15.8.0 yesterday. Although I'm not 100% sure that this update caused it. When I try to load resource or open already created .rc file this happens:
Error message
ActivityLog.xml says this:
<entry>
<record>533</record>
<time>2018/08/15 18:01:53.704</time>
<type>Error</type>
<source>VisualStudio</source>
<description>No InprocServer32 registered for package [Visual C++ Resource Editor Package]</description>
<guid>{74AAD8B2-3294-49CB-BB5D-E9BAB132BFD5}</guid>
<hr>8007007f</hr>
<errorinfo></errorinfo>
<path>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\vcpackages\resedit.dll</path>
</entry>
What I tried to do to fix this:
All fixes from this question
Repairing Visual Studio from VS Installer
Removing and reinstalling VS from scratch
Nothing works. What could it be and how to fix this? It's not critical, because I still can open resource.rc, resource.h and manually add resources - it compiles fine. But still rather inconvenient.
This issue with resedit.dll is fixed in MSVS2017 15.8.2.
Release notes: https://learn.microsoft.com/en-us/visualstudio/releasenotes/vs2017-relnotes#15.8.2
Bug report: https://developercommunity.visualstudio.com/content/problem/311385/visual-c-resource-editor-package-load-failed.html).
We had the same Problem in our Company. The update works on Windows10 but Windows 7 Systems aren't able to open the resource editor.
Our "dirty" solution was to copy the resedit.dll from an older Visual Studio Version onto the new one.
Hopfully Microsoft brings a bugfixed version soon
Related
I have installed 'qt-vsaddin-msvc2017-2.3.0' for using QT in Visual Studio 2017, but there are some issues after installation. First thing is that I can not modify QT project Settings in Qt VS Tools since it is grey. After I restart VS, it keeps showing that 'Qt Visual Studio Tools Version 2.3.2: initializing...' and doesn't go on. Is there something I miss when I install qt-vsaddin?
Answering this question a bit late because I ran into this problem myself today. The problem is your VS2017 is not up to date -- You need at least version 15.8; currently 15.9 is released. Odds are your ActivityLog.xml looks similar to Pavel Celba's answer here in which it's having trouble loading a specific version of the Microsoft.VisualStudio.Threading assembly. In order to fix the issue, you're going to have to do one of two things:
Update your Visual Studio Community/Professional/Enterprise to the latest version.
Downgrade your version of the Qt vsaddin to 2.2.2. You can obtain the 2.2.2 release, here. If you need a previous version because your version is even earlier, go to the parent directory of that link.
Once you've installed 2.2.2 or have obtained the Visual Studio 15.9 update, it should be working correctly.
I also had this issue because my VS version is 15.4 but I can't connect to the internet on that computer.
Try installing qt-vsaddin-msvc2017-2.3.2.vsix . If it fails you will probably need to reinstall VS 2017.
We have same problem here - the error shown is:
<entry>
<record>334</record>
<time>2019/02/25 12:48:44.893</time>
<type>Error</type>
<source>VisualStudio</source>
<description>SetSite failed for package [Vsix]Source: 'QtVsTools' Description: Could not load file or assembly 'Microsoft.VisualStudio.Threading, Version=15.8.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.VisualStudio.Threading, Version=15.8.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.VisualStudio.Threading, Version=15.8.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
at QtVsTools.Vsix.InitializeAsync(CancellationToken cancellationToken, IProgress`1 progress)
at Microsoft.VisualStudio.Shell.AsyncPackage.<>c__DisplayClass16_0.<<Microsoft-VisualStudio-Shell-Interop-IAsyncLoadablePackageInitialize-Initialize>b__1>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at Microsoft.VisualStudio.Services.VsTask.RethrowException(AggregateException e)
at Microsoft.VisualStudio.Services.VsTask.InternalGetResult(Boolean ignoreUIThreadCheck)
at Microsoft.VisualStudio.Services.VsTask.GetResult()
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
</description>
<guid>{15021976-647E-4876-9040-2507AFDE45D2}</guid>
<hr>80070002</hr>
<errorinfo></errorinfo>
</entry>
Our Visual Studio version is:
Microsoft Visual Studio Enterprise 2017
Version 15.5.1
We cannot update to newest update due to company policies.
Disconnect form internet and install Qt vsaddin 2.2.2 then run VS2017 go to Tools>Extensions and Updates> select "Qt Visual Studio Tools" > and then uncheck "Automatically update this extension".
I am working on some very old software that uses Visual Studio 6, Visual Studio .net and Visual Studio 2010. So I ended up having to install various versions of studio from 6 all the way to 2017. At some point something got messed up and I ended up uninstalling and reinstalling a whole bunch of things. Everything else works now, but Visual Studio 2015 is toast. I uninstalled anything related to 2015, then reinstalled it. Same problem. Uninstalled it again, hoping the uninstaller would correctly remove stuff, reinstall, again no go.
So, when I open VS, the log in button on the top right does nothing. If I try to create a test C++ project, it just closes the screen where you enter the project details and then reopens it, no joy there. If I open a solution with C++ projects in it is says it does not know how to load the project file of that type.
If I build the project in VS 2017 and leave the projects as VS 2015, I get a linker error "LINK : fatal error LNK1104: cannot open file 'mfc140d.lib'", so something mostly likely did not install properly.
After clicking on the log in button, the other menu's will highlight when you click on then, but no menu's.
The ActivityLog.xml contains stuff like this:
<entry>
<record>366</record>
<time>2017/08/08 14:18:48.820</time>
<type>Error</type>
<source>Extension Manager</source>
<description>Error loading extension: This VSIX does not apply to any product installed on this machine. The problem could be that the VSIX manifest's format is not recognized, or that the manifest has been corrupted. Data at the root level is invalid. Line 1, position 1. </description>
<path>C:\PROGRAM FILES (X86)\MICROSOFT VISUAL STUDIO 14.0\COMMON7\IDE\EXTENSIONS\MICROSOFT\VSGRAPHICS\</path>
</entry>
<entry>
<record>367</record>
<time>2017/08/08 14:18:49.123</time>
<type>Error</type>
<source>Extension Manager</source>
<description>Extension will not be loaded because an extension with the same ID 'Microsoft.Windows.DevelopmentKit.Desktop' is already loaded at C:\PROGRAM FILES (X86)\COMMON FILES\MICROSOFT\EXTENSIONMANAGER\EXTENSIONS\MICROSOFT\WINDOWS KITS\10\DESKTOP SDK\...</description>
<path>C:\PROGRAM FILES (X86)\COMMON FILES\MICROSOFT\EXTENSIONMANAGER\EXTENSIONS\MICROSOFT\WINDOWS KITS\8.1\DESKTOP SDK\</path>
</entry>
<entry>
<record>368</record>
<time>2017/08/08 14:18:49.123</time>
<type>Error</type>
<source>Extension Manager</source>
<description>Extension will not be loaded because an extension with the same ID 'Microsoft.Windows.DevelopmentKit.WindowsStore' is already loaded at C:\PROGRAM FILES (X86)\COMMON FILES\MICROSOFT\EXTENSIONMANAGER\EXTENSIONS\MICROSOFT\WINDOWS KITS\10\WINDOWS STORE SDK\...</description>
<path>C:\PROGRAM FILES (X86)\COMMON FILES\MICROSOFT\EXTENSIONMANAGER\EXTENSIONS\MICROSOFT\WINDOWS KITS\8.1\WINDOWS STORE SDK\</path>
</entry>
I am guessing I might have to uninstall VS 2015 and then manually clean up any remnants? Any suggestions? I really don't want to rebuild this machine.
Thanks.
I know it isn't a helpful answer, but the error messages suggest your registry etc. is beyond repair. The fastest and safest way to clean up is formatting the disks and reinstalling Windows from scratch.
For your next attempt to use Visual Studio I strongly recommend virtual machines, one for each VS version.
Before installation of RTM version of VS2015 Community Edition I had uninstalled VS2015 Enterprise CTP6 (including applications from "second installer"). There wasn't any problem during installation, but now I'm unable to create/open any C++ project. I receive following error message:
C:\Users\Piotrek\Documents\Visual Studio 14\Projects\Tests\Tests\Tests.vcxproj : error : Method not found: 'System.Threading.Tasks.Task Microsoft.VisualStudio.Project.IVsUnconfiguredProjectTypeGuidSetter.SetActiveProjectConfigurationAsync(Microsoft.VisualStudio.ProjectSystem.ProjectConfiguration, Microsoft.VisualStudio.ProjectSystem.ProjectConfiguration)'.
I tried to reinstall all related to any VS version stuff, but the problem remains.
Unfortunately, Google knows nothing about SetActiveProjectConfigurationAsync and now I'm stuck. Any suggestions?
Check if the Microsoft.VisualStudio.ProjectSystem.v14only.dll assembly is in your GAC (you'll see a similarly-named folder under C:\Windows\Microsoft.NET\assembly\GAC_MSIL if it is). It shouldn't be there. But perhaps you have an old version of that assembly in your GAC. If you see any folders in your GAC starting with Microsoft.VisualStudio.ProjectSystem.*, move them to a temporary folder and see if it fixes your problem. If it does, delete your temporary folder.
I'm trying to start a performance profiling session in Visual Studio 2012 RTM on Windows 8 PRO 64-bit for a console program (ANALYZE / Start Performance Analysis).
I get a popup message informing me
Could not load file or assembly 'Microsoft.VisualStudio.PerformanceTools.CounterInfo.dll' or one of its dependencies. The Specified module could not be found.
Apparently this can happen under VS2010 after KB2645410 is installed. I carefully followed the procedure given for this issue with the same error message:
Visual Studio 2010 SP1, KB2645410 and Add-Ins
However, that does not resolve the issue.
I have tried running VS2012 as Administrator as well.
How can I get the profiler working?
UPDATE
I can actually attach to a running instance of the project from the command line using the steps here:
Walkthrough: Command-Line Profiling Using Sampling
However, Visual Studio does not open the resulting .vspx file (it just does nothing after I open it with File / Open File).
UPDATE 2
Fuslogvw reports two binding errors when I attempt to start the profiler:
VS 2012 Profiler Binding Errors - Pastebin
Adding the following to the system path resolved the issue for me permanently.
C:\Program Files (x86)\Microsoft Visual Studio 11.0\Team Tools\Performance Tools
Some other answers may be appropriate to other situations.
Note that you probably will need to run Visual Studio as Administrator for profiling to work correctly.
I also struggled with that issue.
I found a working solution for me:
I opende the XXX.sln file using notepad.
There i found several parts in the Project and Global Section looking something like this:
ProjectSection(SolutionItems) = preProject
Performance1.psess = Performance1.psess
EndProjectSection
I removed all of them and that made my Analyzer work again.
I delete the .suo file and everythings works correctly now.
The same question exists here:
http://social.msdn.microsoft.com/Forums/en-US/a6487155-980c-4bc8-82de-2fe588fdf37f/windows-update-kb2645410-and-performance-tools-error
The following are suggested workarounds:
Remove windows update KB2645410
Only run one instance of Visual Studio
If you are the administrator on your development PC you can add the permission to Everyone to read and execute all the content in the folder "C:\Program Files (x86)\Microsoft Visual Studio 10.0\Team Tools\Performance Tools" and subfolders/files.
"I backed everything up and did a complete repair of Visual Studio using the original disk from Microsoft. That allowed the computer to shut down normally. Then I tried the patch again. It hung again, but after a few reboots we got a message about deleting corrupt files and finally everything seems OK."
My issue was resolved when I realized that my user access control was set too high. Once that was turned off, I rebooted and it all worked great.
Once I uninstalled re-sharper my issue was resolved.
UPDATE1: I have reinstalled Visual Studio and I am still having this problem. My guess is there is a problem with my environment.
Update2: Diving in.
I attached windbg to devenv and set a breakpoint in windbg for msenv!_tailMerge_WINMM_dll and traced through.
This is trying to load winmm.dll using the LoadLibrary API. I can see that LoadLibrary is failing and GetLastError is returning 5 which is "access denied".
now, why would vs be denied access to winmm.dll?
---Begin Original---
I am currently having a serious issue with Visual Studio 2005 SP1 Intellisense in C++. I have an all native solution with on project. Whenever I, or the editor, attempt to invoke intellisense auto-complete pow, Visual Studio crashes. I even tried this with a brand new console app. Ctrl + Space in the empty main and Visual Studio crashes.
I googled for help on this but to no avail. I have tried deleting the ncb file but no luck on that front either.
I am currently working with Intellisense turned off as shown in this article:
Visual Studio 2005 - 'Updating IntelliSense' hang-up
And I have no crashes, but it sure would be nice to have intellisense back
Call stack from a crash dump.
7c812a6b kernel32!RaiseException+0x53
502717a6 msenv!__delayLoadHelper2+0x139
50675186 msenv!_tailMerge_WINMM_dll+0xd
505ac3c3 msenv!CTextViewIntellisenseHost::UpdateCompletionStatus+0x1a7
505acb50 msenv!CEditView::UpdateCompletionStatus+0x30
505dcfad msenv!CEditView::CViewInterfaceWrapper::UpdateCompletionStatus+0x2a
02ae47fc vcpkg!CCompletionList::DoCompletion+0x444
02ade2ce vcpkg!CAutoComplete::PostProcess+0x240
02ade07f vcpkg!CAutoComplete::OnACParseDone+0x3e
02adac2d vcpkg!CMemberListWorkItem::OnCompleted+0x9d
029eb4e3 vcpkg!CWorkItem::ProcessPendingWorkItemCompletedCalls+0x117
029f8b4f vcpkg!CParserManager::OnIdle+0x183
0299961a vcpkg!CVCPackage::OnIdle+0x48
5014b288 msenv!ATL::CComAggObject<CTextBuffer>::QueryInterface+0x43
5a9d2394 VCProject!ATL::CComPtr<IOleInPlaceFrame>::~CComPtr<IOleInPlaceFrame>+0x24
5a9d2880 VCProject!ATL::CComObject<CVCArchy>::Release+0x10
774fd420 ole32!CRetailMalloc_GetSize+0x21
5009422b msenv!CMsoCMHandler::FContinueIdle+0x23
5009422b msenv!CMsoCMHandler::FContinueIdle+0x23
I would try the following set of steps to try and fix the problem
Reset All Settings: Tools -> Import / Export Settings -> Reset All Settings
Delete HKCU:\Software\Micosoft\VisualStudio\9.0 and then restart VS
Repair the VS installation through Add Remove Programs
Disable all 3rd party plugins
Did you try repairing the Visual C++ installation?
Do you have any plugins installed? Try disabling them.
It might be worth it to delete the .ncb file in the project directory, in case it was corrupted (.ncb is the intellisense database file).
If you're doing C++ development for a living (or at least doing serious development), there's no reason not to use Visual Assist.
What a bizarre problem.
I finally figured it out using procmon from sysinternals:
http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx
My sounds were somehow changed to windows default sounds after a recent trip to IT. This caused visual studio to play a clicking sound when intellisense happens. In order to play this sound winmm.dll must be loaded up, which is located c:\windows\system32\winmm.dll.
I suppose through debugging foray winmm.dll symbols were downloaded to a FOLDER called C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\winmm.dll. Of course this folder looked mighty tasty to Visual Studio, so when it tried to load the winmm.dll folder as a dll file POW!!!
I deleted the folder, and some other .dll folders :) and all is well.
Thanks for your help.
Make sure you are up on your service packs, I think VS 2005 is at SP1.
Try "cleaning" the solution, i.e. delete (rename) all temporary files like *.ncb, *.suo etc that have been created by Visual Studio. One of these files might have got corrupted (Your problem sounds like the IntelliSense database is broken).