DJowe78
commented
1 year ago That changes in my Pull Request was not sufficient. I hope the info below is useful even if I have never played around with extensions for Visual Studio.
I managed to get it installed by changing the InstallationTarget and Prerequisite in the following files. But I got missing reference error in VS afterwards when opening the options for Visual chatGPT Studio.
extension.vsixmanifest manifest.json catalog.json
Changes in those files: InstallationTarget Version was set to "[16.0,)" on the x86 architecture.
Version of Microsoft.VisualStudio.Component.CoreEditor was set to "16.0"
Details on missing reference. But after that when opening the Tools->Options->Visual ChatGPT I got the error "Could not load file or assembly Microsoft.VisualStudio.Shell.15.0, Version=17.0.0.0".
Log info from: %AppData%\Microsoft\VisualStudio\16.0_7e1bb266\ActivityLog.xml
<entry>
<record>863</record>
<time>2023/03/17 03:07:36.540</time>
<type>Information</type>
<source>VisualStudio</source>
<description>Begin package load [VisuallChatGPTStudioPackage]</description>
<guid>{A8EB0343-B35C-4175-95D8-50549E609FF3}</guid>
</entry>
<entry>
<record>864</record>
<time>2023/03/17 03:07:36.563</time>
<type>Error</type>
<source>VisualStudio</source>
<description>CreateInstance failed for package [VisuallChatGPTStudioPackage]Source: 'mscorlib' Description: Could not load file or assembly 'Microsoft.VisualStudio.Shell.15.0, Version=17.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
System.IO.FileLoadException: Could not load file or assembly 'Microsoft.VisualStudio.Shell.15.0, Version=17.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'Microsoft.VisualStudio.Shell.15.0, Version=17.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>{A8EB0343-B35C-4175-95D8-50549E609FF3}</guid>
<hr>80004005 - E_FAIL</hr>
<errorinfo></errorinfo>
</entry>
Changed the version number for the extension
The InstallationTarget element in the .vsixmanifest file is specifically targeting Visual Studio version 16.0 and not any versions higher than 16.0 on x86 architecture. Therefore, if you have a higher version of Visual Studio installed, such as Visual Studio Professional 2019 version 16.11.23, the extension may not be compatible.