[Mono-dev] Fork of certmgr - any ideas? (Mono-devel-list Digest, Vol 117, Issue 32)
Miguel de Icaza
miguel at xamarin.com
Sat Jan 24 18:04:21 UTC 2015
Yes, we have a partial project that does this.
Not sure where we are at on it, but the last time I checked, it did most of
the class libraries.
On Sat, Jan 24, 2015 at 12:24 PM, Arthur Peka <artur.peka at gmail.com> wrote:
> >In the case of certmgr, was there any complexity in creating the solution
> in MD? If it's trivial, it might be reasonable for people to just
> >generate them when they need them. If it's non-trivial, it might not be
> unreasonable to include those in the mono sources.
> I beg to differ. There wasn't really any complexity there, but scaffolding
> takes time and energy. Proper solution file could at least be generated
> with make.
> On Thu, Jan 22, 2015 at 2:25 PM, Edward Ned Harvey (mono) <
> edward.harvey.mono at clevertrove.com> wrote:
>> > From: mono-devel-list-bounces at lists.ximian.com [mailto:mono-devel-list-
>> > bounces at lists.ximian.com] On Behalf Of Jo Shields
>> > it's
>> > easier to work with a standalone MD project than the whole Mono tree,
>> > when doing breakpointing & object inspection
>> Something I've certainly done in the past to debug mono sources, was to
>> create a MD/XS solution in the mono source dir locally on my system, with a
>> really basic console application that referenced some mono classes, so I
>> could then debug my console app & step through mono source in the IDE.
>> After doing stuff, I chose to commit mono source changes and discard the
>> IDE scaffolding because it was trivial.
>> In the case of certmgr, was there any complexity in creating the solution
>> in MD? If it's trivial, it might be reasonable for people to just generate
>> them when they need them. If it's non-trivial, it might not be
>> unreasonable to include those in the mono sources.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mono-devel-list