dotnet build on .net standard projects not working for ubuntu-latest about setup-dotnet

[Rickedb]

Checking https://github.com/Rickedb/OpenProtocolInterpreter/actions/runs/40249169, seems that it's really problem with the filename, since all errors are popping in the files that you changed for the pull request.

Going to check it at night and bring some news here...

[Rickedb]

The problem really was extension in uppercase. GitHub actions build is working as expected now.

[inhifistereo]

I am seeing the same.

[ZEisinger]

@Rickedb and @inhifistereo is your build working locally on a linux machine?

For mac, could you try macos-latest instead? I was able to get the project working on macos-latest.

[inhifistereo]

I'll have to set it up.

[Rickedb]

@ZEisinger Haven't tried locally on linux, I'll try it out and update you ASAP.

Tried macos-latest using the same yaml. Could setup and build project but could not test my .net core 2.0 test project. (I'm using version 3.0.100-rc1-014190)

Do I need to get .net core 2.0 SDK too when running action when on macos?

macos-latest try:
https://github.com/Rickedb/OpenProtocolInterpreter/commit/df5db7248d6739541aa28ef0084e03eb3be951f5/checks?check_suite_id=389147108

My tests:
https://github.com/Rickedb/OpenProtocolInterpreter/actions?query=branch%3Agithub-actions-test

[Rickedb]

@ZEisinger Same behaviour when running on a Linux environment (tried on Ubuntu 19.04)

Maybe .Net Standard references some .net framework library when building?? Any clue on it ?
Going to check .Net CLI GitHub if I can figure out something, if not, I might open this issue right there.

[rainersigwald]

@Rickedb the 3.0 SDK can build .NET Core 2.0 projects, but it can't run them if the .NET Core 2.0 runtime isn't also available on the test machine.

To build with 3.x but run on 2.x you might need #25.

[Rickedb]

@rainersigwald I've made 2 tests:

1. Switched in GitHub Actions to build with .NET Core 2.2 Here
2. Switched my .NET Standard project to 2.1 and .NET Core (tests project) to 3.0 Here

Both of them haven't worked on Ubuntu.
Also, I`m not having problem with .NET Core but with the .NET Standard project.

[coderpatros]

@Rickedb are you still hitting this issue? If so can you share the repo that is hitting it? I'm using this without issue (except the SxS install workaround).

Edit: just realised you did share the repo. I'll try to do some digging over the next couple of days. If you are still hitting it?

[Rickedb]

@coderpatros I've just set it to build in Windows environment and never tried again to work with Ubuntu or Mac. Probably still running the same issues.

Feel free to fork the repo and contact me if any help needed!

[coderpatros]

@Rickedb this isn't an issue with this action.

Your MIDTesters project targets full framework 4.6.1. The github hosted runners have that targeting pack installed out of the box for Windows which is why it works.

If you want you could look at using mono for non-Windows platforms. But I think, just from personal experience, it is probably better to attempt to migrate that project to standard or core if you can.

[Rickedb]

@coderpatros I don't remember how the workflow file was, since every log is now gone because I deleted the branch which I was testing it.

Looking at my file now, I use dotnet test src/MIDTesters.Core/MIDTesters.Core.csproj which is a .Net Core project not Framework.

Checking https://github.com/ZEisinger/OpenProtocolInterpreter/blob/master/.github/workflows/build.yml, this was when @ZEisinger forked it, seems like it was targeting .Net Core too and build runs only on OpenProtocolInterpreter.csproj, which is a .Net Standard project.

Also, I remember using mono to achieve publishing nuget packages.

Btw I need try again to validate if it still happens or if it was my dumb mistake of trying to build a .net framework in a Unix environment, everything points to the opposite, but you know, we do these mistakes all the time 😂

[coderpatros]

Oh, I thought I saw a reference to MIDTesters from OpenProtocolInterpreter project. But think I was mistaken.

[coderpatros]

Ah... I think I've found the problem. I'll raise a PR on your project soon hopefully