Bug 10102 - Support StartAction/StartProgram/StartArguments/StartWorkingDirectory
Summary: Support StartAction/StartProgram/StartArguments/StartWorkingDirectory
Status: NEW
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Project Model ()
Version: 3.1.x
Hardware: PC Windows
: --- enhancement
Target Milestone: ---
Assignee: Lluis Sanchez
Depends on:
Reported: 2013-02-06 18:39 UTC by alex
Modified: 2013-02-07 03:36 UTC (History)
1 user (show)

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 for Bug 10102 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description alex 2013-02-06 18:39:41 UTC
Hi folks,

I've just noticed that I couldn't launch&debug a Dll project in MD.
So I've got my Dll project in my solution and I've marked that one as Start Program, but now I'm not able to neither execute nor debug it.

I have tried the solution provided by mhutch, http://stackoverflow.com/questions/9637994/how-can-i-debug-monodevelop-add-ins-with-monodevelop, but that didn't help much because I still can't actually _debug_ my project inside MD.

As part of the solution for this request I recommend you to make use of the 


inside the <PropertyGroup Condition="..."> nodes in the .csproj file.

Both Visual Studio and #Develop support these options and handle them so I'll be able to just press 'Debug' and the IDE 'debugs' the executable specified in <StartProgram>. 

I really miss this feature and thought that it was a kind of standard feature which every .Net/Mono IDE should provide.

Thanks in advance,
Comment 1 Mikayla Hutchinson [MSFT] 2013-02-06 20:03:11 UTC
The custom run command is debuggable, as long as the "command" is a .NET executable (no arguments, etc) and you have a debugger installed and working.
Comment 2 alex 2013-02-06 23:15:25 UTC
But couldn't this be available by default, without having to fix in some custom data into the project file? 
I mean, the command override still could remain, it's only about the little effort that the user doesn't have to spend in order to get a exe-less project running.. - also mind the compatibilty to other IDEs.
Comment 3 Mikayla Hutchinson [MSFT] 2013-02-07 03:36:19 UTC
You can add custom run command from project options, you don't have to edit the project file. Editing the project file is only necessary to set environment variables.