mirror of
https://github.com/brutaldev/StrongNameSigner.git
synced 2026-04-25 11:26:04 +03:00
[GH-ISSUE #52] dotnet build fails #48
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @wolfkor on GitHub (May 17, 2019).
Original GitHub issue: https://github.com/brutaldev/StrongNameSigner/issues/52
Originally assigned to: @brutaldev on GitHub.
I tried to use it with a dotnet build (2.1).
I get ...Brutal.Dev.StrongNameSigner.targets (6.5): error MSB4062: The Brutal.Dev.StrongNameSigner.AutomaticBuildTask Task could not be loaded from the ...\ .nuget \ packages \ brutal.dev.strongnamesigner \ 2.3.0 \ build \ Brutal.Dev.StrongNameSigner.dll assembly. Could not load file or assembly 'Microsoft.Build.Utilities.v4.0, Version = 4.0.0.0, Culture = neutral, PublicKeyToken = b03f5f7f11d50a3a'. The system can not find the stated file....
Building locally within VS is working. Is it possible to build it with a newer Microsoft.Build.Utility reference ?
@brutaldev commented on GitHub (May 17, 2019):
Do you have a sample project to replicate this failure? I suspect it's because the build task does not support and has not been tested outside of Visual Studio so using the new Core command line tools probably doesn't provide the probing paths as VS does.
@eyaldar commented on GitHub (Jan 27, 2020):
Any solution to this problem? I've been having the same problem.
@brutaldev commented on GitHub (Jan 28, 2020):
@eyaldar Got a sample project with the commands you are using? Cannot debug and fix this if I cannot reproduce.
@mistial-dev commented on GitHub (Dec 4, 2021):
I'm getting the same error trying to build.
Sample Project: gl.zip
My build environment is a bit unusual, I suspect. Dotnet 6, using Rider, on an ARM Macbook Pro.
@mistial-dev commented on GitHub (Dec 4, 2021):
The assembly seems to be Microsoft.Build.Utilities.Core instead of a specific version.
@brutaldev commented on GitHub (Dec 5, 2021):
@mistial-dev There is currently a hard dependency on
Microsoft.Build.Utilities.v4.0because of the inheritance required for the automated build task and this is still being built for the full .NET Framework and not .NET Core.I'll need to convert this project to .NET Core (was planning to anyway) and target multiple frameworks with build directives to use the correct utilities reference. Thanks for the sample project, I'll use this for testing 👍
@mistial-dev commented on GitHub (Dec 6, 2021):
Appreciated.
We are doing cross platform development for an open source initiative, so we are trying to support as many platforms as possible.
It's security related, so we are hesitant to have things unsigned. If it comes to it we will recompile the upstream libraries, but this seems the more elegant solution, and I'm glad that you went through the effort to make it possible.
If there is anything on my side I can do to help test, please let me know.
@brutaldev commented on GitHub (Dec 8, 2021):
@mistial-dev Thanks. Almost done with the specific changes that fix this issue. I'll deploy a beta NuGet package you can bring into your project while I make the other fixes I want to for the official 3.1.0 release.
@brutaldev commented on GitHub (Dec 8, 2021):
@mistial-dev
Please use the beta package with your project: https://www.nuget.org/packages/Brutal.Dev.StrongNameSigner/3.0.5-beta
Tried and tested with your sample project on a Mac, this was a lot tricker to get working cross-platform that I thought...
<PackageReference Include="Brutal.Dev.StrongNameSigner" Version="3.0.5-beta" />@mistial-dev commented on GitHub (Dec 9, 2021):
Thank you.
I just did a big project restructuring, so I'll need to re-add the references and set up a test. I'll let you know how it goes.
@mistial-dev commented on GitHub (Dec 9, 2021):
Looks good. Thank you so much!