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.

Sign up for GitHub

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

Jump to bottom

Assembly is not strong named #118

Open
mathieuchateau opened this issue Feb 12, 2020 · 4 comments
Open

Assembly is not strong named #118

mathieuchateau opened this issue Feb 12, 2020 · 4 comments

Comments

@mathieuchateau
Copy link

Hello,

Can you strong name your assembly ?
I can't get it working without :'(

System.IO.FileLoadException: Could not load file or assembly 'NLog.Targets.GraylogHttp, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. A strongly-named assembly is required. (Exception from HRESULT: 0x80131044)
File name: 'NLog.Targets.GraylogHttp, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null'

Thanks in advance,
Mathieu Chateau
@mathieuchateau
Copy link
Author

I tried to do it through Pull request 119 #119

@dustinchilson dustinchilson linked a pull request May 7, 2020 that will close this issue
apply strong name #119
Closed
@dustinchilson
Copy link
Owner

Sorry, I completely missed this case.

what is you're use case for signing the assembily?

@dustinchilson
Copy link
Owner

Either way, seems like a good idea, https://docs.microsoft.com/en-us/dotnet/standard/library-guidance/strong-naming

@mathieuchateau
Copy link
Author

Sorry, I completely missed this case.

what is you're use case for signing the assembily?

I build a sotfware, which is protected by SmartAssembly. This require strong names

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

apply strong name mathieuchateau/NLog.Targets.GraylogHttp
2 participants
@dustinchilson @mathieuchateau