ReedCopsey
commented
7 years ago I'll put out an update, and sign it, this week. Seems perfectly reasonable.
Out of curiosity, what vsix are you producing using FsXaml?
On Feb 12, 2017 1:02 PM, "Kirill Gerasimenko" notifications@github.com wrote:
Hi, Thanks for the awesome library! Description
Unable to load FsXaml.Wpf assembly from signed VSIX project.
This is the message from the original exception: "Could not load file or assembly 'FsXaml.Wpf, Version=3.1.2.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. A strongly-named assembly is required. (Exception from HRESULT: 0x80131044)" Known workarounds
Do not sign VSIX project. In this case everything works fine, exception is gone.
Would it be possible to sign the assembly?
-- Kirill
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/fsprojects/FsXaml/issues/62, or mute the thread https://github.com/notifications/unsubscribe-auth/AFCUmt9BsF0ew-gzPHZzO6SfUHPGJw4yks5rb3NmgaJpZM4L-nXK .
kirill-gerasimenko
Hi, Thanks for the awesome library!
Description
Unable to load FsXaml.Wpf assembly from signed VSIX project.
This is the message from the original exception: "Could not load file or assembly 'FsXaml.Wpf, Version=3.1.2.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. A strongly-named assembly is required. (Exception from HRESULT: 0x80131044)"
Known workarounds
Do not sign VSIX project. In this case everything works fine, exception is gone.
Would it be possible to sign the assembly?
-- Kirill