[Mono-dev] Crash course on bringing .NET open sourced code to Mono.

[Martin Thwaites]

So has it been merged yet?

I'm going to look at the Buffer stuff I shy'd away from before.  Then look
at the MachineKey.Protect stuff to implement the things I missed.

I've got a separate question around the mismatch in conventions, but I'll
ask that on a different thread.

I'm struggling to contain my excitement at the moment!

Thanks,
Martin

On 15 November 2014 13:03, Miguel de Icaza <miguel at xamarin.com> wrote:

> Hello,
>
> We worked only on System.Configuration, regex, the crypto and web stack.
>
> The rest you can do, including the web stack.
>
> I took a look at asp.net.   I think in the long term we want to replace
> most of it, but it needs to be done in stages, as it still contains a bunch
> of native stuff.m
>
>
>
> Miguel
>
> On Saturday, November 15, 2014, Martin Thwaites <monoforum at my2cents.co.uk>
> wrote:
>
>> Hi Miguel,
>>
>> Is there an ETA on merging your "large fork".  I don't want to get
>> started on anything that you guys have already done?
>>
>> Or could you tell us which areas to stay away from for now?  Personally,
>> I would want to look at some of the system.web things.
>>
>> Thanks
>> Martin
>> On 15 Nov 2014 03:07, "Miguel de Icaza" <miguel at xamarin.com> wrote:
>>
>>> Hey guys,
>>>
>>> Sami reached out to me, and was wondering how to get started in bringing
>>> some code to Mono, in particular WCF to Mono.   So I wrote this small guide
>>> for newcomers.
>>>
>>> I would say it takes a couple of steps:
>>>
>>>    - Build your own local version of Mono on Linux.
>>>    - Make sure it works "mcs" should be able to run after installing it.
>>>    - Run a trivial self-hosted WCF server/client
>>>    - Make a trivial change to the WCF class library, and install this
>>>    version to test you can make changes locally and have them run:
>>>       - cd mono/mcs/class/System.ServiceModel
>>>       - Make changes
>>>       - make install
>>>       - Run your test again in another window
>>>       - Repeat
>>>    - Make sure you can run the test suite:
>>>       - cd mono/mcs/class/System.ServiceModel
>>>       - make run-test-local
>>>
>>> Once you are ready, you can start importing code.   Ideally, you want to
>>> go for high-value targets: the most buggy parts of Mono's stack (you can
>>> check bugzilla for reports on memory usage, bugs).   Or you can pick a
>>> missing feature.
>>>
>>> To import code, modify the relevant ".sources" file in the
>>> System.ServiceModel directory (where you ran the test) and replace a local
>>> file, with a reference to the "referencesource".
>>>
>>> Chances are, you will need to make changes to the "referencesource"
>>> code, since a lot of it is Windows specific.
>>>
>>> Miguel
>>>
>>>
>>> On Fri, Nov 14, 2014 at 5:25 PM, Sami Ben Grine <
>>> SBen-Grine at axarosenberg.com> wrote:
>>>
>>>>  Sweet – is there anything I can do to make progress?
>>>>
>>>>
>>>>
>>>> I am somewhat ignorant about Mono but I am pretty ok with .NET and
>>>> Linux.
>>>>
>>>>
>>>>
>>>> thanks
>>>>
>>>>
>>>>
>>> _______________________________________________
>>> 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/20141115/81b17723/attachment.html>