Bug 6073 - Cannot get debugging funtionality
Summary: Cannot get debugging funtionality
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: 3.0.x
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
Depends on:
Reported: 2012-07-11 06:33 UTC by Dave Gautrey
Modified: 2012-07-11 14:57 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 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:

Description Dave Gautrey 2012-07-11 06:33:46 UTC
I have installed the latest Monodevelop 3.x both stable and latest Beta launched via Unity sync Assets menu, but neither give me the option to debug the project.

There is no option in the options menu to point the editor back to Unity so i am at a loss as to how to use.

The internal Monodevelop 2.x works fine, in terms of allowing me to start a debugging session.

I am using Windows 7 x64, fully updated, i do not have any version of visual studio installed.

Other than the debugging issues Monodevelop 3.x seems to function great.

Is there some setup i am missing ???


Comment 1 Mikayla Hutchinson [MSFT] 2012-07-11 14:57:17 UTC
In order to debug Unity projects from MonoDevelop, you need the version of MonoDevelop provided by Unity. This is because they have made modifications to it that have not been contributed upstream, and they include additional custom MonoDevelop addins that have not yet been ported to the MD 3.0 API.