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
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 3284 [details]
MS Build error
When trying to compile an older third party solution,and using an older version of the monoadroid (4.0.6) unable to create the package. After the device selection step, the msbuild give the “not found” error (attached to this bug). Using using a third party sdk, and trying to compile and debug solution with the new version, yet it results in multiple errors. The older setup file gives multiple errors as well.
Attempted to remove and re-install all the components in the specified order.
But when attempted to try to debug the project on the device, still receive the same error
When the Android Debug log was run, when debugging runs, the log stops writing.
Also checked that the path existed in that registry key: Only had the key (HKEY_LOCAL_MACHINE\Software\Microsoft\ASP.NET\4.0.30319.0\) but the Path string was not there.
Also tried to add it manually but it doesn’t work.
In addition, also tried to install the latest version of Mono for Android and tried to deploy a test project on the device: it worked fine. Instead, since installing the 4.0.6 version to work on our solution, it started showing the MSBuild error.
Both errors attached.
Created attachment 3285 [details]
SystemNullReference Error message
@Dominique: Are we still explicitly launching `msbuild.exe` as a separate process? This bug may be moot/fixed.
This bug is most likely fixed since VS now uses the in-process msbuild engine. Daniel, can you confirm and close the bug if it is so?
As we are not getting any response since 2014-07-30. So I am closing this issue.