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.
Custom commands cannot be debugged. This is really annoying for developing projects that have to be run with some kind of host, such as external addins for MD itself. Such projects cannot be debugged at all.
It would be nice if the custom run commands used the execution subsystem properly, so they could take advantage of execution handlers, execution modes, custom runtimes, parametrized execution, etc.
Marking major since this blocks use of the debugger for a whole class of projects.
Since SolutionItem can have custom commands, maybe we should move the OnExecute/DoExecute implementation down from DotNetProject/Project, and have an abstract GetExecutionCommand method on SolutionItem. OnExecute/DoExecute would use the custom command's execution command if it's present, else call GetExecutionCommand.
Custom commands already use the execution system. I have add-ins for which I have set a custom command which starts MD.exe, and I have no problem with debugging.
Which specific case is not working for you?
I guess I didn't realize that my MD build on Windows didn't have the .NET debugger, and I didn't understand the way that the execution system was passing ExecutionHandlers to CustomCommand.CanExecute.
BTW, that seems a bit wasteful, recreating the ExecutionCommand when querying the state of every handler.