[Mono-dev] MonoSummit: Planning the Sessions

[Brock Reeve]

Thanks guys.

This will help with debugging on windows, but the "holy grail" I was after 
was to be able to debug MWF and System.Drawing on MacOSX. Does anyone know 
if remote debugging works on the MacOSX? I know it works from Windows to 
Windows. Basically, my setup is to build an app using WindowsForms on 
Windows. I have that same directory shared to the MacOSX. I build it on 
windows and then from the Mac run it from the command line to see if 
things are working. I would like to step through the code on Windows while 
it is running on the Mac. Currently, running on Windows doesn't work 
because it can't find the Carbon API's on Windows.

Brock




Jonathan Pobst <monkey at jpobst.com> 
11/06/2007 03:55 PM

To
Brock Reeve <Brock.Reeve at ni.com>
cc
Petit Eric <surfzoid at gmail.com>, Miguel de Icaza <miguel at ximian.com>, 
mono-devel-list at lists.ximian.com
Subject
Re: [Mono-dev] MonoSummit: Planning the Sessions






Hey Brock!

Us VS.Net brats are looking at what we can present to help out our 
fellow brats.  I work pretty much exclusively in VS2005 and completely 
understand the advantage of staying with tools you already know 
(especially ones that have integrated debuggers).

In the meantime, the following article is what we had put together to 
show how to debug Mono winforms apps in VS.  Since this was written, we 
added another project "Mono.Mozilla" to the Managed.Windows.Forms 
solution to support the upcoming WebBrowser control.  You will need to 
add this project to the local solution (there is a project file for it 
in SVN/Mono.Mozilla).

Unfortunately, this doesn't extend down to the other Mono class 
libraries, as many of them do not maintain solution files.  But it 
should get you started.

http://www.mono-project.com/Guide:_Debugging_With_MWF

Hope this helps!
Jon


Brock Reeve wrote:
> 
> I like the idea of having a debugging session. I am a VS.NET brat and am 

> struggling with the best way to debug (hunt down issues) and learn some 
> of the Mono framework. I have created VS.NET solutions for 
> System.Drawing and System.Windows.Forms so I could browse the source 
> with VS.NET which helps. My current way is to build on Windows, copy the 

> assemblies and use Console.Writeline to debug and learn stacks. Let's 
> just say this is not ideal. So the session could be titled something 
> like "Debugging Mono for VS.NET brats". Some ideas for a debugging 
session:
> 
> - What tools/processes do Mono developers use to develop?
> - What is the easiest way for VS.NET developers to debug the framework?
> - What is the process for submitting code changes (patch files)?
> 
> 
> I also would like to see a session on the dependencies and the way 
> modules are organized. For example, what the mono framework libraries 
> call into and their dependencies. What parts are unmanged and which 
> parts are managed etc. Here is some examples (the dependencies are 
> things I have read and learned from buildling and might not be totally 
> correct):
> 
> - Class libraries -> [glib-2.0] - [gthread-2.0] - [libgc]
> - Moon -> [ffmpeg] - [GTK -> GDK] - [ALSA]
> - System.Drawing -> [libgdiplus -> Cairo (statically linked into 
> libgdiplus)]
> 
> Brock
> 
> 
> 
> *"Petit Eric" <surfzoid at gmail.com>*
> Sent by: mono-devel-list-bounces at lists.ximian.com
> 
> 10/31/2007 10:03 AM
> 
> 
> To
>                "Miguel de Icaza" <miguel at ximian.com>
> cc
>                monodevelop-list <monodevelop-list at lists.ximian.com>, 
> mono-devel-list at lists.ximian.com
> Subject
>                Re: [Mono-dev] MonoSummit: Planning the Sessions
> 
> 
> 
> 
> 
> 
> 
> 
> Dam Gmail, it doesn't includ the list by defaut when answering
> 2007/10/31, Petit Eric <surfzoid at gmail.com>:
>  > At this time there is a way/method/howto for have a simalar debuging
>  > tool as MS in MD, to folow own code step by step, pas throug and so 
on
>  > directly in MD IDE/RAD, during execution of the program ?
>  >
>  > 2007/10/31, Miguel de Icaza <miguel at ximian.com>:
>  > >
>  > > > I would be happy to hear about debugging applications with mono, 
> the state of
>  > > > the debugger, etc.
>  > > >
>  > > > Also, in relation to this, debugging mono itself: when you 
> _really_ think what
>  > > > you observe is not a bug in your program, how to go about 
> checking mono
>  > > > against the C# standard, MS implementation, whatever.
>  > >
>  > > Great suggestion;
>  > >
>  > > We will add a "Debugging with MDB" tutorial, and we probably will 
> have a
>  > > Tips and Trick BOF session.
>  > > _______________________________________________
>  > > Mono-devel-list mailing list
>  > > Mono-devel-list at lists.ximian.com
>  > > http://lists.ximian.com/mailman/listinfo/mono-devel-list
>  > >
>  >
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/mono-devel-list


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20071108/54058a0e/attachment.html