-
-
Notifications
You must be signed in to change notification settings - Fork 171
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
Could not load file or assembly Microsoft.DotNet.PlatformAbstractions under dotnet tye
#466
Comments
Thanks for sharing. I'm unfamiliar with Tye, and can only guess that as part of running it, it executes some part of your msbuild projects (again) but in some environment that isn't what we are prepared for. For this to be actionable, can you provide the OS of the agent, including version? |
Is this enough? |
I'm afraid when I try on ubuntu 16.04 it works. And you reported it works too, except under |
dotnet tye
@AArnott |
I am working on removing the So if your task relies on PlatformAbstractions, you will need to package the assembly with your task assembly (just like any other 3rd party library). Alternatively, an API to get the current machine's RID was added to .NET 5 with |
I just looked where you are using Nerdbank.GitVersioning/src/Nerdbank.GitVersioning.Tasks/GitLoaderContext.cs Lines 61 to 65 in 8e21b4b
Another alternative that is available in .NET Core 3.0+ is to use the new System.Runtime.Loader.AssemblyDependencyResolver class. Check out https://docs.microsoft.com/en-us/dotnet/core/tutorials/creating-app-with-plugin-support for more information. Basically, the idea is that you ship a |
This just broke me locally on Windows with
|
Can someone who was hit by this please verify the fix is effective by acquiring 2.3.7-beta from here: |
Done, that fixed it for me |
I see the following in logs for an azure-pipeline job for a dotnet core 3.1 application. These lines appear in the tye step of this pipeline.
Regardless of this error, the versions still seem to be updated correctly, for both the pipeline, dotnet assembly and node script. As such I post this here for informative purposes only.
The text was updated successfully, but these errors were encountered: