csc or al

[CSharper]

Quick question, I have an application that has 3 dependent dlls they
are my c# project that were build outside my main project as they are
shared in multiple other projects. I compiled the app using csc and
got my exe created. Then I used ILMerge to merge all the dependent
dlls along with the main exe I created with csc and generated one
single output exe.
My question is, will it be possible to achive the result using csc or
al.exe?

Thanks,

 

[Jon Skeet [C# MVP]]

Quick question, I have an application that has 3 dependent dlls they
are my c# project that were build outside my main project as they are
shared in multiple other projects. I compiled the app using csc and
got my exe created. Then I used ILMerge to merge all the dependent
dlls along with the main exe I created with csc and generated one
single output exe.
My question is, will it be possible to achive the result using csc or
al.exe?

Not that I'm aware of. That's precisely why ilmerge was created -
although frankly I think it's almost always better just to live with
having multiple assemblies.

Jon

 

[CSharper]

Not that I'm aware of. That's precisely why ilmerge was created -
although frankly I think it's almost always better just to live with
having multiple assemblies.

Jon

Thanks and I think I found another one, iexpress (win XP tool), this
has command line options to create self extracting exe and then launch
the primary application. If that one works, I will be fine with that
as well.

 

[Ben Voigt [C++ MVP]]

Quick question, I have an application that has 3 dependent dlls they
are my c# project that were build outside my main project as they are
shared in multiple other projects. I compiled the app using csc and
got my exe created. Then I used ILMerge to merge all the dependent
dlls along with the main exe I created with csc and generated one
single output exe.
My question is, will it be possible to achive the result using csc or
al.exe?

I think you can generate .netmodule files for each project instead of .dll
files, then al.exe would link them together. But I think you might end up
with one assembly in multiple files, instead of multiple assemblies in one
file.