[Mono-dev] Compiling System.Web with CSC
eyala at mainsoft.com
Wed Sep 28 11:52:04 EDT 2005
The option of playing with ilasm/ildasm will mess out completely the debug
information. PDB uses the tokens from the DLL to identify the class, method,
etc. The tokens will be completely messed up by this exercise.
I will look at the output of ildasm to analyze better the .Net 2.0 dependencies
to see if we can come up with some kind of hack for using the CSC 2.0 compiler.
On Tue, 27 Sep 2005, Miguel de Icaza wrote:
> Date: Tue, 27 Sep 2005 18:12:03 -0400
> From: Miguel de Icaza <miguel at ximian.com>
> To: Eyal Alaluf <eyala at mainsoft.com>
> Cc: martin at ximian.com, Noam Lampert <noaml at mainsoft.com>,
> Philippe Cohen <philc at mainsoft.com>, mono-devel-list at lists.ximian.com
> Subject: Re: [Mono-dev] Compiling System.Web with CSC
>> 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.
> Alternatively to upgrading mcs, you can use csc, and then do:
> ildasm /out:output file.dll
> sed script
> ilasm output.il
> Where the sed script would remove the couple of new keywords on ildasm
> and replace the 2.x references with 1.x references.
More information about the Mono-devel-list