[Mono-dev] Bug with Ssl cert validation

Bryan Crotaz bryan.crotaz at silvercurve.co.uk
Tue Mar 18 14:10:38 UTC 2014

I spent 4 days trying to get make to work on Cygwin. Followed those
instructions and others. Every post I found had significant errors in
it (eg Cygwin package names ) or was years out of date.

Bryan Crotaz
Silver Curve

On 18 Mar 2014, at 13:25, "Edward Ned Harvey (mono)"
<edward.harvey.mono at clevertrove.com> wrote:

>> From: Bryan Crotaz [mailto:bryan.crotaz at silvercurve.co.uk]
>> I'd love to contribute, but I have now spent several days trying and failing to
>> compile Mono for Visual Studio so that I can fix bugs in the C# libraries.  If
>> someone could write a VS2010 solution that can be used to debug Mono,
>> that would help hundreds of devs like me who just want to fix their favourite
>> bug.
> Did you see these posts?
> http://mono.1490590.n4.nabble.com/Getting-started-on-mono-sources-td4661906.html
> Scroll down to "step-by-step" and also  --disable-bcl-opt
> I know this is for Xamarin Studio on mac (or linux/unix)...  And also, I've only had mixed success in stepping / debugging mono sources this way, but maybe you have access to a non-windows machine?  Or maybe you care to build mono with cygwin on windows, and attempt to reproduce this result in Visual Studio?
> I know VS has a checkbox, like XS, to enable/disable stepping through assembly sources.  But of course, you can't step through the Microsoft closed source.  ;-)  And you'll probably have to figure out some tricks to make VS debug against the mono assemblies instead of .NET.  This might be easiest using MonoDevelop / XS (even on windows.)  I venture a guess that it's easier to make XS debug against mono sources.

More information about the Mono-devel-list mailing list