Skip to content
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

Containerize the solution in linux with .NET Core 3.1 #183

Closed
filipendo125 opened this issue Feb 24, 2022 · 4 comments
Closed

Containerize the solution in linux with .NET Core 3.1 #183

filipendo125 opened this issue Feb 24, 2022 · 4 comments

Comments

@filipendo125
Copy link

Hi!
I have an existing .NET Core 3.1 project which I am trying to containerize via Linux docker containers, but it seems that I am not able to do so, and I get an error coming from MrAdvice upon dotnet build.

error MSB3073: The command ""/root/.nuget/packages/mradvice/2.9.7/build/../tools/net5.0/MrAdvice.Weaver.exe"
AssemblyPath="obj/Release/netcoreapp3.1/Webscheduler.Common.dll"
ReferencePath="@obj/Release/netcoreapp3.1/Webscheduler.Common.dll.MrAdvice.ReferencePath.txt"
ReferenceCopyLocalPaths="@obj/Release/netcoreapp3.1/Webscheduler.Common.dll.MrAdvice.LocalReferencePath.txt"
AssemblyOriginatorKeyFile="" SignAssembly="false"" exited with code 1. [/src/Webscheduler.Common/Webscheduler.Common.csproj]

I am using mcr.microsoft.com/dotnet/sdk:3.1 to build. I don't seem to be allowed to run the exe, and the even when I investigated MrAdvice.targets, it seems that this is the preferred way if I have .NET Core. I tried to modify the project to .NET 6, to use the dotnet command but as there are lots of dependencies on the project, I would need to have multiple SDKs installed, which are not installed.

What should I use to satisfy the requirement to build within Linux container with .NET Core 3.1?

@picrap
Copy link
Member

picrap commented Feb 27, 2022

I have no idea how to build with .NET Core 3.1 😓. Maybe you could try to run the weaver from command line to see if you have more details about the error. But that’s a big “maybe”.

@jorgenbosman
Copy link
Contributor

Perhaps you can also use "dotnet MrAdvice.Weaver.dll" instead of calling the exe directly as it is now done for .Net 6

@picrap
Copy link
Member

picrap commented Dec 19, 2022

Hi @jorgenbosman, shall we consider this as closed?

@jorgenbosman
Copy link
Contributor

I think so yes

@picrap picrap closed this as completed Dec 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants