Re: [Mono-dev] Porting HttpApplication and associated classes

2014-11-20 Thread 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 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? > >

Re: [Mono-dev] Porting HttpApplication and associated classes

2014-11-20 Thread Martin Thwaites
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 wrote: > >> First, we need to the fork and sub-module up and running for the >> reference sour

Re: [Mono-dev] Porting HttpApplication and associated classes

2014-11-20 Thread Miguel de Icaza
> > > 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

[Mono-dev] Porting HttpApplication and associated classes

2014-11-19 Thread Martin Thwaites
Hi All, I'm planning on taking on the porting of part of System.Web, so I thought I would make people aware so that we're not all working on the same thing. My process is to start with importing HttpApplication in it's entirety, then pull in the surrounding classes so it compiles. I can then sta