This isn't necessarily true.
You could always compile the code as a netmodule (the new stuff in C#)
and then link it to the main executable with AL.EXE. However, I agree that
using a DLL is generally the better way to go, it helps enforce better
design (on a fundamental level).
--
- Nicholas Paldino [.NET/C# MVP]
-
mv*@spam.guard.caspershouse.com
"Ignacio Machin ( .NET/ C# MVP )" <ignacio.machin AT dot.state.fl.us> wrote
in message news:OR*************@TK2MSFTNGP05.phx.gbl...
Hi,
AFAIK a DLL is the only way to go., either that or write the new code in
Vb.net of course :)
--
--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation
"UJ" <fr**@nowhere.com> wrote in message
news:%2****************@TK2MSFTNGP03.phx.gbl...I have a VB.Net app that was written about a year ago. We have switched
over to C# as our default language. I need to make changes to the VB app
(including adding some new modules.)
Is there a way I can write the new modules in C# and compile them in to
the program?
I realize I could write them as a DLL but I'd like to have all the code
together.
I'm working in .Net 1.1
TIA - Jeff.