-
Notifications
You must be signed in to change notification settings - Fork 228
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
Version 4.0.4 - Strong name signature could not be verified #661
Comments
Same problem here |
Getting the same issue with version 4.0.5, in .NET 4.8 Framework website/apps |
Getting the same issue with version 4.0.5, in .NET 4.8 Framework website |
Getting the same issue with version 4.0.5, in a .NET 4.8 Framework WebForms project. Reverting to latest v3 makes project work again. |
Can an issue be ralated to logic changed here? 3add778 |
I'm getting the exact same error under .NET Framework 4.8 and Minio 4.0.5. Downgrading to 4.0.0 seems to be the only option at the moment. |
Getting the same issue with version 4.0.6, in .NET 4.8 Framework website. 🙁 |
@itssimple, @brz , @anton-chayka , @ddudda174 , @heidgert , @VI-oscar It looks like this is a known issue in the Microsoft .NET and Visual Studio community and it is called
Another reference I found is a visual studio msbuild errors link.
I believe, in your cases, the issue is either GAC has references to old DLLs and/or MVC Web Applications dependency on |
@tih2010 , #712 is closed as a duplicate of this issue as they are the same problem. So, this issue still tracks the problem. Please take this as a note: I think PR#732, currently in the code review process, might also address this issue as |
@ebozduman Can you review this again? |
@martijn00 |
What I mean is that it could possible be fixed by #732 but i haven't checked. Since that PR the new build system is used, which is better and more stable. If you check if it works now, you can close this issue |
Got it. This is something we could not reproduce in house. |
@ebozduman yes, I can confirm that Minio v.5.0.0 (.netstandard 2.0 for .net framework 4.8) is working fine! I've built it from master branch and pack it with |
Thank you @anton-chayka Closing this issue as fixed by PR #732 |
Just like in #643, we are seeing problems with the strong name signature in 4.0.4 when running in a .NET 4.8 Framework (ASP.NET WebSite/Application)
OS: Windows 10 Enterprise 21H2 (19044.1741), Windows Feature Experience Pack 120.2212.4180.0
VS: VS 2022 Enterprise
Default ASP.NET Web Application (WebForms)
TestMinio.csproj
Downgrading to 4.0.0 (4.0.3 still has the signature error) works, but 4.0.4 contains fixes that I want to try.
The text was updated successfully, but these errors were encountered: