Skip to content
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

The nuget package have no strong name #45

Closed
edwardmeng opened this issue Apr 4, 2018 · 3 comments
Closed

The nuget package have no strong name #45

edwardmeng opened this issue Apr 4, 2018 · 3 comments

Comments

@edwardmeng
Copy link

edwardmeng commented Apr 4, 2018

I'm getting error:
System.IO.FileLoadException: 'Could not load file or assembly 'DotNet.Glob, Version=2.0.1.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. A strongly-named assembly is required.
How I can use your package now? Or when will you fix it?

@edwardmeng
Copy link
Author

I have copied the source code instead of package reference until the nuget package strongly-named.

@dazinator
Copy link
Owner

Fixed as of 2.0.3 which will appear on nuget shortly (if not already). Thanks for reporting.

@dazinator
Copy link
Owner

and FYI, If you wanted to continue to build from source, as of the latest commit, Debug builds should work as normal and produce a non-signed assembly.. However Release builds now expect to find a DotNet.Glob.snk key file in the repo root directory which it will use to sign the assemblies. This is not checked in, so you would have to create your own key file or disable assembly signing in that case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants