Closed richard-edwards closed 7 years ago
I was looking in the code and was able to change the reference to xbuild for non-windows environments temporarily to msbuild and get a proper build going. On my Mac I'm getting the following for xbuild and msbuild references:
RICHARD-MACMINI:~ Richard$ which msbuild /Library/Frameworks/Mono.framework/Versions/Current/Commands/msbuild RICHARD-MACMINI:~ Richard$ which xbuild /Library/Frameworks/Mono.framework/Versions/Current/Commands/xbuild RICHARD-MACMINI:~ Richard$
Yeah I will change the detection to use msbuild when it is available. Thanks for reporting
Thanks, I can try and do a pull request if you want. Seems pretty simple fix and I've never done one on an OS project before.
Of course, feel free :)
After some time away from my Xamarin project, I had to upgrade to Visual Studio for Mac from Xamarin Studio after Microsoft purchased Xamarin. I can do a normal build in VS Mac for my Android project but when I do it through the gulp task I'm getting a null object reference on the build. If I do a command line build using msbuild the project builds fine but the gulp task is using xbuild still and I'm not sure if it should be in this instance.
I build with diagnostic logging and I'm getting the following. I'm wondering if xbuild can deal with .NETStandard targets or not yet and if that is the culprit. Is there a way to force the task to using msbuild and not xbuild?