> From: Sebastien Pouliot [mailto:sebastien.poul...@gmail.com]
> Sent: Tuesday, March 18, 2014 7:52 AM
> 
>> Any better ideas?
> 
> Contribute! :-)

Honestly, I *do* like this idea, and I'm trying.  I'm a C# developer, and have 
never been a mono developer (I've been a user of C#/mono, but never a 
contributor), and I'm finding the learning curve to be pretty steep...

In a recent thread, I pushed through to the point of being able to build the 
mono sources, build something linked against the mono source, and step through 
the mono source.  I tried to do the same thing this time, but when I step into 
AuthenticateAsClient, all the code is grayed out, and if I step one step 
further, the debugger crashes.  So I spent some time trying to figure out why I 
couldn't step into that code any further, and then I started sprinkling 
WriteLine statements...  And there *has* to be a better way.

I wouldn't say I gave up.  I posted here and thanks to Sebastien, got a 
workaround, which takes the pressure off so I can focus on our product 
deliverable.  But I'd like to get a better understanding of this mono source 
and how to properly debug it.  Or maybe I just need to suck it up and work 
through the WriteLine debugging workflow?  I hope not.
_______________________________________________
Mono-devel-list mailing list
Mono-devel-list@lists.ximian.com
http://lists.ximian.com/mailman/listinfo/mono-devel-list

Reply via email to