-
Notifications
You must be signed in to change notification settings - Fork 19
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
Does not load with VS 2017 #1
Comments
I get this error too. |
Hmm... I think I have seen that before. I'll check it out. |
I turned on assembly signing for the DSL project and updated the release. Version is set to 2.0.3. Hopefully it works. I have a custom build of this tool installed on my dev machine here, so it is difficult to test the VSIX adequately. |
UPDATE: Found a possible versioning issue. Resolved and uploaded as 2.0.3.1. |
Where do I download the installation from? http://csd.codeplex.com/releases doesn't seem to be updated. |
It is in the Releases part of GITHUB: https://github.com/hybridview/ConfigurationSectionDesigner/releases |
I changed the message to use a link to the releases page as suggested. |
Getting an error after installing CSD.VS2017.vsix, from AppData\Roaming\Microsoft\VisualStudio\15.0_e960bf7d\ActivityLog.xml:
LegacySitePackage failed for package [ConfigurationSectionDesignerPackage]Source: 'ConfigurationSectionDesigner.DslPackage' Description: Could not load file or assembly 'ConfigurationSectionDesigner.Dsl, Version=2.0.1.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. A strongly-named assembly is required. (Exception from HRESULT: 0x80131044) System.IO.FileLoadException: Could not load file or assembly 'ConfigurationSectionDesigner.Dsl, Version=2.0.1.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. A strongly-named assembly is required. (Exception from HRESULT: 0x80131044) File name: 'ConfigurationSectionDesigner.Dsl, Version=2.0.1.0, Culture=neutral, PublicKeyToken=null' at ConfigurationSectionDesigner.ConfigurationSectionDesignerPackageBase.Initialize() at Microsoft.VisualStudio.Shell.Package.Microsoft.VisualStudio.Shell.Interop.IVsPackage.SetSite(IServiceProvider sp)
The text was updated successfully, but these errors were encountered: