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 a solution configuration is mapped to a nonexistent item configuration, there is no indication that this is the case, except that the item does not build.
Improved - the projects are now highlighted red in the solution tree and the solution mappings. But we should probably have a build warning too.
It would be better to show the project in grey, and show an error message like we do when the build is not active for a project.
No, it should be possible to easily distinguish projects that are intentionally not built (grey) and projects that are accidentally not (red) built because the configuration mapping is broken. The latter is an actual problem. That's why I think we need build warnings too.
Ok, as long as the error message is shown I don't care about the color.
The red warning icon should be enough as red text might be considered noise.
Closing the bug as already fixed.