[Mono-dev] [Mono-list] .NET and Mono integration, the plans

Martin Thwaites monoforum at my2cents.co.uk
Wed Nov 19 22:56:33 UTC 2014


So just replace them with static strings via a script? or create an
individual class somewhere and simply add to it as we implement new classes
from the referencesource?

On 19 November 2014 22:50, Miguel de Icaza <miguel at xamarin.com> wrote:

> I was thinking we just use a perl script ;-)
>
> On Wed, Nov 19, 2014 at 5:48 PM, Martin Thwaites <monoforum at my2cents.co.uk
> > wrote:
>
>> Hi Miguel,
>>
>> Have you come up with a plan on how to implement the resource methodology
>> that's used for strings? i.e. the SR.GetString(SR.Name) type stuff?  Are we
>> just going to implement some partial class that we can add extend for each
>> assembly?  Theres loads throughout HttpApplication.
>>
>> Thanks,
>> Martin
>>
>> On 19 November 2014 21:02, Martin Thwaites <monoforum at my2cents.co.uk>
>> wrote:
>>
>>> Will do, I'm on "Gardening leave" for the next week, so I've got
>>> sometime to look at it.
>>>
>>> Do you have an ETA on when the fork will be created and the sub-module
>>> added?
>>>
>>> On 19 November 2014 20:50, Miguel de Icaza <miguel at xamarin.com> wrote:
>>>
>>>> Hey,
>>>>
>>>> Xamarin's team is not likely going to do System.Web, so feel free to
>>>> step in.
>>>>
>>>> I am not sure if we can bring System.Web as a whole yet, I think it is
>>>> a clear case of something that will have to be done in steps and starting
>>>> with HttpApplication is as good as an idea as antyhing else.
>>>>
>>>> On Wed, Nov 19, 2014 at 2:50 PM, Martin Thwaites <
>>>> monoforum at my2cents.co.uk> wrote:
>>>>
>>>>> Hi Miguel,
>>>>>
>>>>> That sounds good.
>>>>>
>>>>> In terms of System.Web then, would you prefer your internal team does
>>>>> it? or am I ok to start replacing some files when the sub-module is added?
>>>>> I was thinking of trying to hit the HttpApplication class first and work my
>>>>> way out from there.
>>>>>
>>>>> Thanks,
>>>>> Martin
>>>>>
>>>>> On 19 November 2014 19:41, Miguel de Icaza <miguel at xamarin.com> wrote:
>>>>>
>>>>>> Hey,
>>>>>>
>>>>>> I do not think we would be moving the code.   We would do two things:
>>>>>>
>>>>>>
>>>>>>    - Make changes to the fork in mono/referencesoure
>>>>>>    - Reference the new files from mono/external/referencesource
>>>>>>
>>>>>> Miguel
>>>>>>
>>>>>> On Wed, Nov 19, 2014 at 2:26 PM, Martin Thwaites <
>>>>>> monoforum at my2cents.co.uk> wrote:
>>>>>>
>>>>>>> HI Miguel,
>>>>>>>
>>>>>>> Thanks, exactly what I've been waiting for!  I only really have 1
>>>>>>> question.
>>>>>>>
>>>>>>> In the ways that we are going to port things, you mention pulling in
>>>>>>> the entire assembly.  How exactly would you be thinking this would work?
>>>>>>> try building and fixing anything that it depends from other libraries in
>>>>>>> the other libraries? or are you going to fork the reference source,
>>>>>>> submodule it, reference all the files in the .sources files within mono,
>>>>>>> then fix (i.e. add #ifdefs etc.) to the fork?
>>>>>>>
>>>>>>> Essentially, are you thinking that there will be an assembly that
>>>>>>> can simply be copied without changes in the above circumstance?
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Martin
>>>>>>>
>>>>>>> On 19 November 2014 17:48, Miguel de Icaza <miguel at xamarin.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hey guys,
>>>>>>>>
>>>>>>>> As promised, the plans:
>>>>>>>>
>>>>>>>> http://www.mono-project.com/docs/about-mono/dotnet-integration/
>>>>>>>>
>>>>>>>> If you start work on something, please notify the list, and update
>>>>>>>> the Trello board:
>>>>>>>>
>>>>>>>> https://trello.com/b/vRPTMfdz/net-framework-integration-into-mono
>>>>>>>>
>>>>>>>> Miguel
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Mono-list maillist  -  Mono-list at lists.ximian.com
>>>>>>>> http://lists.ximian.com/mailman/listinfo/mono-list
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-devel-list/attachments/20141119/cb4953bc/attachment.html>


More information about the Mono-devel-list mailing list