NuGet error during installing packages "Extensibility DTE object unavailable" - visual-studio-2012

I'm trying to install a package on the Visual Studio 2012 environment using NuGet. For at least two packages (EntityFramework and nLog) I'm getting following error:
Install failed. Rolling back...
Extensibility DTE object unavailable.
Visual Studio is running as an administrator. Operating system is Windows Server 2008 R2 Enterprise. I use NuGet 2.0.30625.9003.
Moreover when VS is starting it throws following exception:
Advises I have found on the Internet to run devenv /ResetSettings or devenv /ResetSkipPkgs and then devenv /Setup but none of this has solved the issue in my case. Is there any way to mend it without re installing VS?

Try updating NuGet to the latest version. The version you're running is pretty old. Even if it won't help, it's a good idea to update it.

Related

Trouble installing Visual C++ Redistributable 2008 in Windows 11 - Error 1935

So I recently installed MSI Afterburner on my Windows 11 Machine, but after installing it won't open up. The probable issue was that I didn't have Visual C++ 2008 Redistributable installed. I have all other versions from 2010-2022.
But while installing the 2008 and 2005 redistributables I end up getting a 1935 error and the installer just rolls back.
Error 1935 dialog box
I searched it up and tried everything like running an sfc scan, disabling and enabling the .NET frameworks. I also checked my Registry Editor and it was all correct.
I checked the event logs and found this :
Activation context generation failed for "D:\MSI Afterburner\MSIAfterburner.exe". Dependent Assembly Microsoft.VC90.MFC,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8" could not be found. Please use sxstrace.exe for detailed diagnosis.
Then I figured out maybe there was problem with the WinSXS folder's permissions.
Turns out only the TrustedInsaller had full access to the folder and the subfolders.
So, I also tried changing the WinSXS folder's permissions manually, but in vain.
How do I fix this error? How do I change the WinSXS folder's permissions successfully?
Or is there any other fix to get MSI Afterburner up and running? Please help.
This is rather peculiar. I know our systems can differ.
I have installed VS 2022 on a pristine Windows 11 system without MSI Afterburner.
Installed VS 2008 redistributable, no problem.
Again: pristine Windows with MSI Afterburner installed.
Installed VS 2008 redistributable, no errors.
Windows 11 Enterprise, Build 22000.co_release.210604-1628
Redistributable 9.0.21022.8 (2016)
MSI Afterburner 4.6.4 Beta, Riva Server 7.3.2 Beta.
After that installed redistributable 2005, no problem.
Did it happen while installing 2005 redistributable? Did you install any other software? It must be something specific to your system.

Tizen Studio 3.3: Device Manager and Emulator Manager fail to launch due to "The code execution cannot proceed because MSVCP120.dll was not found."

I have recently installed Tizen Studio 3.3 (web-ide_Tizen_Studio_3.3_windows-64.exe) and also install all necessary packages through Package Manager. After the process of installation had finished, I tried to launch Device Manager and Emulator Manager, but failed because of the system Error: "The code execution cannot proceed because MSVCP120.dll was not found. Reinstalling the program may fix this problem".
However, this file exists in the folder C:\Windows\system32 and all versions of Microsoft Visual C++ Redistributable Versions are installed.
Please, help me to overcome this issue. Thank you in advance.
Overall, I have found out how to deal with this problem.
First of all, I had to totally reinstall Microsoft Visual C++ 2013 Redistributable. Thanks 'magicandre1981' for this kind of hint. It helps me to get rid of this kind of error:
https://sun9-65.userapi.com/c854124/v854124694/1151cf/ZnvZokiCCoM.jpg
As for unsuccessful launching of Device Manager, where nothing happens after it has been clicked, I overcome this problem by changing the path from 'C:\Program Files\Java\openjdk-13_windows-x64_bin\jdk-13\bin' to 'C:\Program Files\Java\jdk1.8.0_221\bin' in Environment Variables.
You need to install Visual C++ Redistributable Packages for Visual Studio 2013 (x86)
https://www.microsoft.com/en-us/download/details.aspx?id=40784
Reinstall the vcredist_x86.exe even if you have 64-bit system. This solution also fix Tizen Studio 4.6 Device Manager.
The solution is to update Visual C++ Redistributable Packages for
Visual Studio. You can do it by the link
"microsoft.com/en-GB/download/details.aspx?id=40784". Recomendation:
install vcredist_x86.exe even if you have 64-bit system. This will fix
the problem.
Moreover, check if you have no spaces in folder name, where you are
installing SDK. The installation can be complited successfully, but
you will catch errors like "can't resolve path", because of spaces.
Thats confusing.
Reference: https://developer.tizen.org/forums/sdk-ide/missing-msvcr120.dll-v3.1-emulator
According to my experience, device manager and emulator manager was not working on open jdk11, 12, 13.
I have tried for several days and contacted with samsung developer support.
They asked me to install oracle jdk8, I did.
Now it is working well.
Hope it help to somebody who having such an issue.

Cannot create or compile win32 projects in Visual Studio 2015

I have Visual Studio 2010, 2012, 2013, 2015, and 2017 installed on my windows pc.
All version have the C++ components installed.
When I try to build a win32 project in vs2015, I get the error:
TRACKER : error TRK0005: Failed to locate: "CL.exe". The system cannot find the file specified.
And If I try to create a new win32 project via the new project wizard, I can select the Win32 project types, but when I click OK, the wizard just reopens, with no error message.
This only occurs with vs2015. I have tried repairing the installation, and re-installing 2015, but no luck. Anything else I can try?
Try changing this: Build/Configuration Manager/Plataform/New/X86
The basic gist of this, is that you have to install your vs versions in chronological order.
If you fail to do this, for example, installing vs2015 first, certain tools or run-times will not be installed later, as installers for c++ runtimes are version number sensitive.
I had to uninstall all versions, and all c++ run times, then start again to solve the issue.

MicrosoftVisual C++ 2015 Redistributable installation failed 0x80240017

When I try to install Microsoft Visual C++ 2015 Redistributable, I get this error
0x80240017, I need it to solve the api-ms-win-crt-runtime-l1-1-0.dll problem
I had the same problem recently, I needed to use XAMPP and when initializing the Apache module I received this error. I tried many things:
Install all windows updates.
Install Visual C ++ 2015 Redistributable that installs this DLL (I get this error 0x80240017 and could not install).
Install the KBKB2999226 and KB2919355 package that contains this DLL.
Clear TEMP folder and rename directories.
I could not by any means. What solved my problem was to install Visual Studio 2015 itself, I had to push the envelope, I had to push it, that solved my problem, and XAMPP becomes to run, unfortunately.

npm install bcrypt on Windows Server 2012

I'm getting this error when trying to install my node modules for my node server.
MSBUILD : error MSB3428: Could not load the Visual C++ component "VCBuild.exe".
To fix this, 1) install the .NET Framework 2.0 SDK,
2) install Microsoft Visual Studio 2005 or
3) add the location of the component to the system path if it is installed elsewhere.
[C:\inetpub\wwwroot\PearsonRealty- API\node_modules\bcrypt\build\binding.sln]
I've tried to install the .NET Framework 2.0 SDK, but it just exits out and never runs. I can't install Microsoft Visual Studio since I'm on an AWS EC2 instance and I wouldn't have enough space for it. Any help would be awesome, thanks.
You do need to install either VCExpress (preferrably at least 2015) or you can try the experimental VC Build Tools solution which is a smaller install than full-blown VCExpress. Otherwise, if you have one, you can try building on a local Windows machine first and then uploading the compiled addon directory to AWS.

Resources