bbalaji
Occasional Observer

CDCPackage did not load correctly

We are using VisualStudio - 2015 and installed Crownpeak extension. it was working fine till Yesterday.

Today we are started getting  the below error , Now we cannot able to access the Crownpeak Visual Studio Extension

CrownPeak Error.jpg

 

inside the activityLog.xml 

captures the below logs 

CreateInstance failed for package [CDCPackage]Source: 'mscorlib' Description: Could not load file or assembly 'Microsoft.VisualStudio.Shell.Framework, 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.Framework, 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.Framework, 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].


 

 

0 Kudos
2 Replies
bbalaji
Occasional Observer

the above error is appearing only in VS 2015, in VS 2017 its working fine.
0 Kudos

Hi -

This is the currently supported version of Visual Studio, so I recommend contacting product support to help troubleshoot and resolve this.

You should send a ticket through the Case Portal.

If you don't currently have access to the portal, you can request it with this form.

Best,

Denise

0 Kudos