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 or GitHub 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.
I installed Norton on a VM with the current stable products installed, and Norton flagged msbuild.
From Norton: http://screencast.com/t/F1ehjBpUXkL
And then this output in MD: https://gist.github.com/1960600 (MSBuild errors. Not surprising!)
While this is a problem with the way Norton identifies suspicious files, we should try to find some good workarounds for this issue so users with Norton installed can still use MfA.
This issue was reported here: https://xamarin.desk.com/agent/case/6703
Windows 7 VM
Norton's heuristic is probably triggered by the way that we generate multiple versions of MonoDevelop.Projects.Formats.MSBuild.exe into the cache directory at runtime.
We can probably work around this by building all the versions at compile time and shipping them in the MD bin directory.
Implemented the workaround in master, should we backport to 2.8.x?
Commit is 7585c51c8a47603322dd4083ba799f5f5396140e
Checked the commit .msi, verified fixed.