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
assembly Wangkanai.Detection, Version=3.0.0.0 does not have a strong name #364
Comments
Strong Name? I will investigate this later. What is your Visual Studio 2019 update? 15.5? |
Visual Studio 2019 Enterprise 16.5.1 |
What is your csproj structure? <Project Sdk="Microsoft.NET.Sdk.Web">
<PropertyGroup>
<TargetFramework>netcoreapp3.1</TargetFramework>
<Version>3.0</Version>
</PropertyGroup>
</Project> Because I'm not getting this kind of errors. I'm not sure if your issue is similar to CommunityToolkit/WindowsCommunityToolkit#1927 or not. |
here is my csproj structure:
References:
|
I tried to reproduce you project structure in the following branch https://github.com/wangkanai/Detection/tree/naji and still can't get the same issue.
I'm really not sure that is causing your issue. |
@wangkanai , i found it.. try to inject it in chtml file and rebuild
it also happens when add it to constructor:
|
Interesting! I can now reproduce this issue too. Its look like I would need to code sign my library before publishing it to nuget too. Would anybody like to sponsor me in code of code signing certificate? https://en.sklep.certum.pl/data-safety/code-signing-certificates/open-source-code-signing-1022.html |
I have publish 3.0 alpha10 with code signing. See does this solve your issue. |
No , the warning still exists
|
:( Back to the drawing board. Thank you |
I think this issue should have been resolved a while back already. I have a code signing in place and string naming. |
after upgrade to version 3.0.0.0, visual studio 2019 show me warning "Referenced assembly 'Wangkanai.Detection, Version=3.0.0.0, Culture=neutral, PublicKeyToken=null' does not have a strong name."
The text was updated successfully, but these errors were encountered: