-
Notifications
You must be signed in to change notification settings - Fork 375
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
No instances of MSBuild could be detected #933
Comments
Maybe this is the case? microsoft/MSBuildLocator#153 |
would you be able to test a couple of private builds that i send you? and maybe chat besides so we can get it done more quickly? slakc would be good |
Sure, ill be available after 21:00h UTC+2 time |
ping me next week plz |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Usage Information
Nuke Version: v6.0.3 / Dotnet Version: 6.0.301 / Operation System : Mac Os Monyerey 12.4, M1 (CPU)
Description
When i try to init setup in solution folder of i got this problem. I did try different solutions and project but result is same.
Reproduction Steps
Type command nuke :setup in your terminal on mac os with m1 cpu
output from terminal:
NUKE Global Tool version 6.0.3 (OSX,.NETCoreApp,Version=v3.1)
No instances of MSBuild could be detected.
Try calling RegisterInstance or RegisterMSBuildPath to manually register one.
Expected Behavior
Should init Nuke without problem.
Actual Behavior
Throwing error in terminal :
No instances of MSBuild could be detected.
Try calling RegisterInstance or RegisterMSBuildPath to manually register one.
Regression?
No response
Known Workarounds
For now i didn't find any workaround.
The text was updated successfully, but these errors were encountered: