-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extension crashes on start of Visual Studio 2017 #6
Comments
We're also getting this issue on the latest version of AnkhSVN, but older versions work fine. |
Same error for me... How can i install previous version? thank you |
You can try downloading it here https://ankhsvn.open.collab.net/daily/2.7.x |
Do you have VS 2019 installed as well? |
We're using Visual Studio Professional 2017 - Version 15.9.36 |
Thank you for reply, but i need .vsix extension to install in visual studio... I can't install with .msi file... Can you help me? |
We're trying to figure out how to downgrade as well, that msi file didn't work for us either. We just have multiple people running the extension and all the one's that haven't updated work fine. |
Same issue here. I have VS 2005, VS 2010, and VS 2017 installed (no VS 2019). The crash only appears to happen in VS 2017. As @AndreaTalentum states, the supplied link to the .msi does not install the extension to VS 2017. |
Here's the error we're getting (in English) It looks like a specific file / dependency is missing. CreateInstance failed for package [AnkhSVN - Subversion Support for Visual Studio]Source: 'mscorlib' Description: Could not load file or assembly 'Microsoft.VisualStudio.Shell.15.0, Version=16.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=16.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=16.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]. |
Visual Studio 2017 and 2019 need a .vsix file. The .msi files work only for older versions. We just released a first official version for 2017 and 2019, but it appears the 2017 support is broken. Help debugging would be welcome. (Just open the .sln from GitHub with either git or via GitHub's subversion support on https://github.com/AmpScm/AnkhSVN/trunk ) I'm trying to setup a VM to diagnose this further myself, but may take a bit. |
Tried opening the solution in VS2017, it won't build for me. I've never worked on Extensions for VS so I have no idea what I'm doing. Lots of *** is not compatible with net46 errors. |
@rhuijben I tried the latest 2.9.48 build from here https://github.com/AmpScm/AnkhSVN/actions/runs/850508145, but it still did not work. Here's the error: CreateInstance failed for package [AnkhSVN - Subversion Support for Visual Studio]Source: 'mscorlib' Description: Could not load file or assembly 'Microsoft.VisualStudio.Shell.15.0, Version=16.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=16.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=16.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]. |
@rhuijben
|
Any chance of downgrading? this is a huge pain? |
I have an update ready. As I think it resolves the issue while having minimal impact for VS2019 users I'm going to publish it now. Can you please reply with your results? |
The updated version is AnkhSVN 2.9.50 and should be live on the update site now. |
The VS site doesn't support a proper downgrade and the reason we didn't deliver VS2019 support earlier was that our build system didn't support providing stable releases for these versions. All the scripting is in this public GitHub repository now... so I'm verry sorry that this happened, but once we get this fixed all the development can be done publicly right here... and everybody can help (or just pick old versions from the actions tab if they need them) |
Does not crash on loading, but as before when I got it to compile successfully, hitting 'update' from pending changes gives this error:
|
Hello, |
A .51 package is posted with fixes for the Update command and the new initialization problem explicitly reported against the new version (but which I'm unable to reproduce). A few newer packages are available via the Actions page here with cases that might help in less common commands. |
Hello, |
Thanks for confirming. Waiting for a few others to confirm as well before closing this issue. Please feel free to open new issues if you find them. |
It seems to be working now. Thanks. |
Extension suddenly cannot be loaded.
169 2021/05/17 14:10:46.820 InformationMy Visual Studio Version: 15.9.36
Extension Version: 2.9.37
Extracted from ActivityLog.xml:
The text was updated successfully, but these errors were encountered: