MSIL? Compiling in VS.NET creates MSIL, so you have no problems. The command
line compilers (C# = csc.exe; VB.NET = vbc.exe) also produce MSIL.
---
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
***************************
Think Outside the Box!
***************************
> HOWTO Build a C# app to MSIL/CIL?
>
[quoted text clipped - 3 lines]
> information in MSDN on how to do it. I want VS.NET to automatically build the
> MSIL each time my project builds. How can that be done?
ATS - 31 Jan 2005 14:29 GMT
Thank you for the reply,
I was "Seeing" that as the answer, especially as the ILasm compiler said
that the output was "EXE" or "DLL", and that threw me for a loop? Now here's
a tougher question. Is the EXE/DLL that VS.NET makes for a C# project for
.NET a "TRUE" .NET/MSIL compatible app? That is, can one run the DLL/EXE on a
seperate .NET architecture like Mono on the Mac?
Wiktor Zychla - 31 Jan 2005 15:03 GMT
> I was "Seeing" that as the answer, especially as the ILasm compiler said
> that the output was "EXE" or "DLL", and that threw me for a loop? Now
[quoted text clipped - 3 lines]
> on a
> seperate .NET architecture like Mono on the Mac?
yes you can. the CLI file format is an extension to PE file format. it
contains standard PE header followed by CLI header and CLI data.
you will find detailed description in ECMA's CLI draft, part II, section
24.1.
http://www.ecma-international.org/publications/standards/Ecma-335.htm
regards
Wiktor Zychla
It's automatic. Noting for you to do.
> HOWTO Build a C# app to MSIL/CIL?
>
[quoted text clipped - 4 lines]
> the
> MSIL each time my project builds. How can that be done?