MacOS release needs notarization

[zemien]

Hi, I saw your request to help test the MacOS release so here's the outcome:

TL/DR: dotnet tools approach works really well and should be the recommended approach for MacOS if they can't use the Linux docker container approach.

The .zip releases can't run properly on newer MacOS's because it hasn't been notarized by Apple. I think you need an Apple developer account for that. I get a warning that it won't run binaries:

I can go into Security & Privacy to "Allow Anyway":

But I continue to be prompted with warnings for each and every .dll! And I can only Allow Anyway one .dll at a time, so it becomes an endless whack-a-button game:

I was interested to see what would happen if I allowed all of it, but I gave up after about the 20th allow.

The dotnet tools approach on the other hand worked well, and I didn't get any security warnings. It installed as an executable in the tools folder:

Hopefully this gives you enough information to either:

• notarize the MacOS release
• push MacOS users to use dotnet tools or the Linux container

[rnwood]

@zemien Thank you for the feedback on this.

[rnwood]

Help wanted please from someone with access to a MacOS machine.

[zemien]

I can help, what do you need?

…

On Fri, 2 Apr 2021 at 2:53 AM, Rob Wood ***@***.***> wrote: Help wanted please from someone with access to a MacOS machine. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#323 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACAEP6ED4UIDHGLKVBS2YLDTGR3HNANCNFSM4MDZLEVQ> .