-
Notifications
You must be signed in to change notification settings - Fork 68
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
dotnet build fails #52
Comments
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. |
Any solution to this problem? I've been having the same problem. |
@eyaldar Got a sample project with the commands you are using? Cannot debug and fix this if I cannot reproduce. |
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.
|
The assembly seems to be Microsoft.Build.Utilities.Core instead of a specific version.
|
@mistial-dev There is currently a hard dependency on 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 👍 |
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. |
@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. |
…encies to work in .NET Core only environments. Fixes issue #52.
@mistial-dev
|
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. |
Looks good. Thank you so much!
|
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 ?
The text was updated successfully, but these errors were encountered: