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.
If i build MonoDevelop on windows using msbuild, or on MacOS using msbuild, I end up with this error message:
/Users/alanmcgovern/Projects/monodevelop/main/Main.sln (default targets) ->
(Build target) ->
/Users/alanmcgovern/Projects/monodevelop/main/po/po.mdproj (default targets) ->
/Users/alanmcgovern/Projects/monodevelop/main/po/Gettext.targets (_GettextPrepareInputs target) ->
: error : Error initializing task PropertyGroup: Not registered task PropertyGroup.
You won't get this building MD with *MSBuild*, because it's a well-known xbuild bug / missing feature.
Oh, strange. I should double check the error message I get on windows then. I thought it was the same issue as what I got with xbuild on MacOS as it happened on the same project, but it must not be.
And this isn't really a problem. The Gettext targets were specifically written for WIndows. Other platforms use make.
To fix this, implement support for properties/items in targets in xbuild (MSBuild 3.5 feature).
To work around this, change the Gettext targets to use the CreateProperty task (the MSBuild 2.0 mechanism).
I would guess that you're missing Gettext tools from the build prerequisites:
We could change the build targets to have a better message, but it wouldn't be easy without a custom tasks assembly.
This is no longer an issue