CreateInstance failed - VisualStudio 2015
See original GitHub issueToday BuildVision simply didn’t load when I started Visual Studio 2015. It has been installed 1 or 2 months ago, no other update or extension was installed on Visual Studio. An error message was displayed suggesting to look at Visual Studio ActivityLog.xml file. There I found following entries:
<entry>
<record>582</record>
<time>2017/08/11 13:15:48.148</time>
<type>Information</type>
<source>VisualStudio</source>
<description>Begin package load [BuildVisionPackage]</description>
<guid>{837C3C3B-8382-4839-9C9A-807B758A929F}</guid>
</entry>
<entry>
<record>583</record>
<time>2017/08/11 13:15:48.163</time>
<type>Error</type>
<source>VisualStudio</source>
<description>CreateInstance failed for package [BuildVisionPackage]Source: 'mscorlib' Description: Could not load file or assembly 'Microsoft.VisualStudio.Shell.15.0, Version=15.0.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.Shell.15.0, Version=15.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.VisualStudio.Shell.15.0, Version=15.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
 at System.Reflection.RuntimeAssembly.GetType(RuntimeAssembly assembly, String name, Boolean throwOnError, Boolean ignoreCase, ObjectHandleOnStack type)
 at System.Reflection.RuntimeAssembly.GetType(String name, Boolean throwOnError, Boolean ignoreCase)
 at System.Activator.CreateInstanceFromInternal(String assemblyFile, String typeName, Boolean ignoreCase, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, Evidence securityInfo)
 at System.AppDomain.CreateInstanceFrom(String assemblyFile, String typeName)

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>{837C3C3B-8382-4839-9C9A-807B758A929F}</guid>
<hr>80004005 - E_FAIL</hr>
<errorinfo></errorinfo>
</entry>
I tried to restart Visual Studio, restart PC, uninstall BuildVision and install again, all in vain. Could it be that Visual Studio has automatically updated to v2.0 that has just been released and it is broken?
Issue Analytics
- State:
- Created 6 years ago
- Comments:16 (9 by maintainers)
Top Results From Across the Web
Visual Studio 2017 fails to launch. CreateInstance failed for ...
Visual Studio 2017 fails to launch. CreateInstance failed for package [Threaded Wait Dialog Package]Closed - Fixed2 3.
Read more >COMException CreateInstance failed on publish
When running the web api in visual studio (2015) on my local machine, everything works perfectly. When running the published web api on...
Read more >Reason of issue - Microsoft Q&A
CreateInstance (RuntimeType type, Boolean publicOnly, ... takes to get the error, type of project, version of visual studio, environment etc.
Read more >Visual Studio 2019 crashes on startup - Microsoft Q&A
In the log file, I found some errors like: CreateInstance failed for package Async Query Service Package; CreateInstance failed for package Task ...
Read more >Question - Error detecting Visual Studio installations
I'm using Visual Studio 16.6. Thanks for any help. Error... ... Activator:CreateInstance(Type) Unity.CodeEditor.CodeEditor:get_Current()
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ok. Under invastigation. Will provide an Update asap!
Thanks for the quick fix. You don’t realize how valuable BuildVision is until you don’t have it