[Mono-dev] Porting HttpApplication and associated classes

[Miguel de Icaza]

Yes.

We will add the defines to the build profile so you get them soon

On Thursday, November 20, 2014, Martin Thwaites <monoforum at my2cents.co.uk>
wrote:

> Thanks Miguel, I'll get started properly tonight.
>
> So the DEFINE will be #if !CROSS_PLATFORM to exclude anything that is
> native and won't work on non-windows?
>
> On 20 November 2014 13:27, Miguel de Icaza <miguel at xamarin.com
> <javascript:_e(%7B%7D,'cvml','miguel at xamarin.com');>> wrote:
>
>>
>>> First, we need to the fork and sub-module up and running for the
>>> reference source, so I can doing pull requests on there.
>>>
>>
>> The referencesource submodule is there
>>
>>
>>> Second, come up with a way to exclude code without deleting it (I'm
>>> assuming we won't to go down the #ifdef route rather than simply removing
>>> the code from the fork).  I'm thinking there's probably something we can
>>> use already, so just need to know what that is.  (something like #if !MONO
>>> ??)
>>>
>>
>> We should introduce a define, yes.
>>
>> Perhaps we can introduce a "CROSS_PLATFORM" define that we use on the
>> Reference source to annotate those cases.
>>
>> Third, Miguel had an idea of how to do the String resources so we don't
>>> need to refactor large amounts of the referencesource.  The script needs
>>> work, and is probably a job in it's own right.
>>>
>>
>> That will get you running for now ;)
>>
>> Finally, as I won't be replacing every file, some will just have large
>>> amounts of additions/fixes, it's probably worth getting the legacy #ifdef's
>>> before I send a pull.
>>>
>>
>> Nah, I think it is easy.
>>
>> The way you replace a class, is to remove the file from the .sources and
>> add the new one.   That should cover most bases.
>>
>> Miguel
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-devel-list/attachments/20141120/351158e1/attachment.html>