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.
Xamlc is a great idea, and I look forward to it.
However, it comes with the price of totally screwing up debugging. We are told we can turn it on or off. I work on typically large projects with workspaces that contain many projects.
Can we please be sure that there is a mechanism to toggle this feature for an entire workspace, or by configuration? I would hate to have to go through all my projects toggling this every time I need to debug.
I'd also like to be able to drop it in whenever I like (perhaps through config) to see if I have performance issues or not.
What I'd really like, of course, is that it is smart enough to not completely hose break-point debugging. But I doubt we're going to get that.
Before answering, note that XamlC is still work a in progress, and not yet ready for release.
We are working on making sure debugging works. It's very unlikely that XamlC will make it to stable with broken debugging.
We can consider having a configuration directive that acts as a default, and can be overridden by assembly, module, or class attributes.
Thank you for taking the time to submit this report. After reviewing the description of this bug, we believe it no longer affects the current version of Xamarin.Forms. If you are still experiencing the issue after updating your packages, please reopen this report with an attached reproduction.
For your convenience, we have created some reproduction best practices viewable here: https://gist.github.com/jassmith/92405c300e54a01dcc6d
Xamarin Forms Team