[Mono-dev] Compiling System.Web with CSC

Eyal Alaluf eyala at mainsoft.com
Wed Sep 28 11:48:45 EDT 2005

Hi, Miguel.

How easy is this solution and when do you estimate you can implement it?

I believe we will need to add additional non trivial tasks:
   * Integration and testings with our debugger to see that the pdb file indeed
     contains all the debug information we require and that all works correctly.
   * Integration of our compiler tools with mcs. Currently, mcs does not work
     with the IL code we generate from Java .jar files. I believe that the
     issues are mostly in our generator, but it's an additional effort we need
     to count.
Only after all of the above is resolved and working we can start to use mcs
for our System.Web build.


On Tue, 27 Sep 2005, Miguel de Icaza wrote:

> Date: Tue, 27 Sep 2005 11:50:41 -0400
> From: Miguel de Icaza <miguel at novell.com>
> To: Eyal Alaluf <eyala at mainsoft.com>
> Cc: mono-devel-list at lists.ximian.com, Philippe Cohen <philc at mainsoft.com>,
>     Noam Lampert <noaml at mainsoft.com>, martin at ximian.com
> Subject: Re: [Mono-dev] Compiling System.Web with CSC
> Hello,
>> I suggest that we decide together not to increase the dependency on c# 2.0
>> features in System.Web (1.1 configuration). I believe that it is a simple
>> and practical approach without many side effects.
>> What do you think?
> I think it is a bad idea, specially considering that it means that we
> have to write more and debug more code than we otherwise would.
> There is an easy solution that I mentioned before which is that we can
> add support to mcs to generate pdb files instead.
> MCS already uses the API to generate debugging information, the only
> difference is that it consumes a Mono-specific API instead of the
> cross-platform API.
> We did not use the cross-platform API in the past because we did not
> have information on how to use it, but now IronPython has code that
> shows how to use it.
> Miguel.

More information about the Mono-devel-list mailing list