-
Notifications
You must be signed in to change notification settings - Fork 486
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 on .net standard projects not working for ubuntu-latest #37
Comments
I am seeing the same. |
@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. |
I'll have to set it up. |
@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: |
@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 ? |
@rainersigwald I've made 2 tests:
Both of them haven't worked on Ubuntu. |
@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? |
@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! |
@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. |
@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 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 Also, I remember using 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 😂 |
Oh, I thought I saw a reference to MIDTesters from OpenProtocolInterpreter project. But think I was mistaken. |
Ah... I think I've found the problem. I'll raise a PR on your project soon hopefully |
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... |
The problem really was extension in uppercase. GitHub actions build is working as expected now. |
I've been trying to build my .net standard 2.0 project with github actions, tried many times with ubuntu-latest and mac-latest but couldn't achieve anything.
ubuntu throw me weird errors like missing assemblies and mac seems to not even run.
Fortunately, could run it with windows image.
My current .yml file:
Running with ubuntu output:
Also running on windows output:
mac not running:
Any thoughts on it? Am I missing something?
The text was updated successfully, but these errors were encountered: