Bug 122 - Custom commands cannot be debugged
Summary: Custom commands cannot be debugged
Status: RESOLVED INVALID
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Project Model ()
Version: 2.6 RC 1
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2011-07-30 20:34 UTC by Mikayla Hutchinson [MSFT]
Modified: 2011-09-06 15:50 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:
Status:
RESOLVED INVALID

Description Mikayla Hutchinson [MSFT] 2011-07-30 20:34:41 UTC
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.
Comment 1 Mikayla Hutchinson [MSFT] 2011-07-30 20:40:44 UTC
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.
Comment 2 Lluis Sanchez 2011-08-16 06:01:21 UTC
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?
Comment 3 Mikayla Hutchinson [MSFT] 2011-09-06 15:50:20 UTC
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.