Visual Studio 2017 issue during extension installation - visual-studio

i try to install new extension on visual studio 2017 community
when i go to Menu Tool>>Extensions and Updates..
i got error "Retrieving the COM class factory for component with CLSID {xxx} failed due to the following error: 8007007e The specified module could not be found. (Exception from HRESULT: 0x8007007E)"
I used ProcessMonitor To find missing DLL, I found that "C:\ProgramData\Microsoft\VisualStudio\Setup\x86\Microsoft.Vi‌​sualStudio.Setup.Con‌​figuration.Native.dl‌​l"
Result:PATH NOT FOUND
How to resolve this issue ?
Notes:this occur when uninstall VS 2017 RC and Install VS 2017.

According to this thread, you should first execute "InstallCleanup.exe -full" command, and then run the Visual Studio Installer to repair your VS installation.

Related

VisualStudio crash on startup - Error:"streamjsonrps.remoteinvocationException: could not load file or Assembly System.Linq"

I'm getting error message when start Visual Studio 2017 Community version.
At crash with below error message:
Could not start visual studio due to an error.StreamJsonRpc.RemotelnvocationException
Could not load file or assembly System.Linq, Version=4.O,O.O,
Culture= neutral, PublicKeyToken= bO3f5f7f1 1 d5Oa3a or one
of its dependencies. The module was expected to contain an
assembly manifest.
I re-install visual studio, but still getting same error message.
Any help will be appreciate.
I had a similar issue workaround. try this command in the in run window "devenv /ResetSettings"
Please follow the following
1- Stope any antivirus
2- Open Developer Command Prompt for VS 2017
2- run "devenv /nosplash"
I hope this can fix the issue

Package management initialization failed. When launching Visual Studio 2017 (15.7.2)

After installing VS2017 Community ver. 15.7.2 on Win 7 64-bit, following error was found when launching VS2017 with or without admin privilage:
Package management initialization failed.
You can get more information by examining the file:
C:\Users\NAME\Appdata\Roaming\Microsoft\VisualStudio\15.0_5024a39e\ActivityLog.xml
These are the errors found in ActivityLog.xml file:
Infos: Could not find ConfigurationChanged timestamp.
Error: merging configuration file C:\Users\\AppData\Local\Microsoft\VisualStudio\15.0_5024a39e\devenv.exe.config
Error: merging configuration file
C:\Users\NAME\AppData\Local\Temp\dev6FC4.tmp
Error: merging configuration file
C:\Users\NAME\AppData\Local\Temp\dev6FC5.tmp
Error: merging configuration file
C:\Users\NAME\AppData\Local\Temp\dev6FC6.tmp
Error: Configuration file merge failed.
Error: Failure calling FinishInitialize.
Tried to install VS2017 Enterprise as well as the VS2017 Community 15.6.7 and got the same errors.
There is a similar problem answered here but it doesn't work for me.
Any input is appreciated
I had the same problem, i solve that doing this
Uninstall Visual Studio 2017 and other Visual Studios
Delete C:\ProgramData\Microsoft\VisualStudio
Uninstall any Visual C++
Look for any Visual Studio Key on the Regedit and delete
Delete C:\Users\UserName\Documents\Visual Studio 2017 (Backup your projects)
Delete C:\Users\UserName\AppData\Local\Microsoft\Visual Studio\15.##
Update your Windows and restart your pc
Install Visual Studio 2017 again
Try to open, and one error apears
Copy the devenv.exe.config file locate in the root of the IdE to
C:\Users\UserName\AppData\Local\Microsoft\Visual Studio\15.##
Try to open again
Try to open in safe mode
Try devenv.exe /resetSettings
Try to repair Visual Studio Again
For me works :) !

Not able to uninstall VS 2013 professional with update 3

I am trying to UNINSTALL VS - 2013 professional but I am not able to do so. Error I am getting is "Visual Studio Core features fatal error during installation"
When I check log file I get this message inside. after long list of text I find this somewhere in the log file
[11DC:14D4][2017-03-28T11:44:48]i000: MUX: ExecuteError: Package (vs_professionalcore) failed: Error Message Id: 1305 ErrorMessage: Error 1305.Error reading from file C:\Windows\Microsoft.Net\assembly\GAC_MSIL\Microsoft.VisualStudio.QualityTools.CommandLine\v4.0_12.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.QualityTools.CommandLine.dll. Verify that the file exists and that you can access it.
[13DC:1608][2017-03-28T11:46:08]e000: Error 0x80070643: Failed to uninstall MSI package.
[13DC:1608][2017-03-28T11:46:08]e000: Error 0x80070643: Failed to execute MSI package.
Kindly tell me how to fix it. I want to uninstall VS. Please help.
To clean up and delete Preview, RC and final releases of Visual Studio 2013 and Visual Studio 2015, as well as early previews of Visual Studio 2017, you can have a try with the VisualStudioUninstall tool: https://github.com/Microsoft/VisualStudioUninstaller

visual studio cannot open new project

Whenever I try to create a new project in VS 2010 I get the error:
New project/item dialog could not be initialized due to error:
Exception of type 'Microsoft.VisualStudio.Dialogs.DialogInitializationException' was thrown.
And when try to open existing project visual studio 2010 restarts.
I had the same problem on my computer. After a long time searching I solved it by the following steps:
Close all instances of Visual Studio
Go to "C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE" (or whatever is your VS installation directory)
Run command devenv.exe /resetuserdata and wait until finished
Run Visual Studio
I can't find the former case. As you met an exception
Microsoft.VisualStudio.Dialogs.DialogInitializationException
I am suggesting you try the way below:
Run devenv /resetuserdata.
Delete the file:
%LOCALAPPDATA%\Microsoft\VisualStudio\11.0\ComponentModelCache
and restart Visual Studio.
Close all VS instances and try the solution mentioned here:
Launch Developer Command Prompt for VS 2017 as Administrator
Go to VS 2017 installation folder, for example: pushd C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise
gacutil -if Common7\IDE\PublicAssemblies\Microsoft.VisualStudio.Shell.Interop.8.0.dll
Open your control panel
Change
Regional -> Formats tab -> Format: English(United States)
https://connect.microsoft.com/VisualStudio/feedback/details/727578/vs-do-not-work-with-finnish-number-format-on-w8-64-bit
It works for me :)
This problem can cause when you install an older version of Visual Studio nearby the current version. For example VS 2017 is installed on your system and you do force install of VS 2008.
I faced this problem many years ago by installing VS 2008 after VS 2010;
and today again I had this problem. Because I installed SolidWorks 2015 after VS 2017. SolidWorks had a Visual Studio 2008 inside its package that interferes my installation.
Just uninstalled VS 2008 and I'm done.
I found this to still be an issue in Visual Studio Community 2017, Microsoft released a work around that fixed my problem:
The work-around for this issue would be:
-Launch “Developer Command Prompt for VS 2017” as Administrator
-Go to VS 2017 installation folder, for example: pushd C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise
-gacutil -if Common7\IDE\PublicAssemblies\Microsoft.VisualStudio.Shell.Interop.8.0.dll

InstallShield and VS2010

I installed InstallShield 2012 Premier and try to create Basic MSI project in VS2010 (Premium). But I cannot create project since I get the error:
The 'InstallShield 2012 Package' 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 running the application together with the /log parameter >on the command line, and then examining the file 'C:\Users\Administrator\AppData\Roaming\Microsoft
\VisualStudio\10.0\ActivityLog.xml'.
If I follow the instruction in ActivityLog.xml I see the next error:
LoadLibrary failed for package [InstallShield 2012 Package]
C:\Program Files (x86)\InstallShield\2012\System\IsDevPkg.dll
I've tried devenv.exe /resetskippkgs and reinstallation of Visual Studio and InstallShield, but it was not helpful.
Perhaps I don't have some pererequisites installed?
Thanks,
Elena
Update: installation InstallShield 2012 Spring solved the problem. It seems like in newer version IS this bag has been fixed.

Resources