Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
GitHub or Developer Community with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Created attachment 17828 [details]
Traditionally we've been able to do something like this in our code, running on Mono on OSX:
Mono would implicitly detect that it was a .NET managed assembly and start it up without explicitly invoking it through mono.
It appears that this detection does not work to detect assemblies compiled with dotnetcore's compiler, even when they are compiled to target the .NET 4.5 Framework and otherwise run just fine under mono.
I've attached a very simple repro case to illustrate the issue (README contained inside the .zip).
While this may be seemingly innocent, it's causing major issues with projects such as http://cakebuild.net which is now being compiled with dotnetcore and relies heavily on Process.Start invocations with the implicit managed assembly detection.
PR with fix: https://github.com/mono/mono/pull/3745
Fixed in master/f7b73f070a5031f04837461757d8cf9ea34b5f67 and mono-4.8.0-branch/dca5ff953f24cf6d88f5977f5c45032938d5cb32