linking

[styko]

I've got an executable file which references assembly compiled into separate
dll. How to compile this dll into my executable- I simple want to distribute
only my executable.

Thanks for any advices!

[styko]

I know that I have to have .NET Framework installed, but this assembly which
I want to link statically is not from .NET Framework. It is assembly that
has class for password generation. I can't include it in my executable
because I'm writing my project in C#, and function that generates password
is in VB, so I compiled it as a standalone assembly. I want to link it into
my exe to make disassembly process harder. Maybe there is better solution to
this problem???

Thanks for any advices!!!

styko,

There is a utility on gotdotnet that will do this. However, in most
cases I think that static linking is a bad idea.

Also, because you have the dll statically linked into your executable,
you still have to have the .NET framework installed on the machine that you are going to deploy this to.

Hope this helps.

[Nicholas Paldino [.NET/C# MVP]]

styko,

You can compile your projects into modules, by using the command line
compiler for each language and setting the target to "module". Once you
have these modules, you can combine them into one assembly by using the
assembly linker (AL.EXE) program.
--
- Nicholas Paldino [.NET/C# MVP]
- ni**************@exisconsulting.com

"styko" <st***@atos.wmid.amu.edu.pl> wrote in message
news:bg**********@nemesis.news.tpi.pl...

I know that I have to have .NET Framework installed, but this assembly which I want to link statically is not from .NET Framework. It is assembly that
has class for password generation. I can't include it in my executable
because I'm writing my project in C#, and function that generates password
is in VB, so I compiled it as a standalone assembly. I want to link it into my exe to make disassembly process harder. Maybe there is better solution to this problem???

Thanks for any advices!!!

styko,

There is a utility on gotdotnet that will do this. However, in most
cases I think that static linking is a bad idea.

Also, because you have the dll statically linked into your executable, you still have to have the .NET framework installed on the machine that

you

are going to deploy this to.

Hope this helps.

[styko]

Thank you for your help, that is what I was looking for!!!

styko,

You can compile your projects into modules, by using the command line
compiler for each language and setting the target to "module". Once you
have these modules, you can combine them into one assembly by using the
assembly linker (AL.EXE) program.
--
- Nicholas Paldino [.NET/C# MVP]
- ni**************@exisconsulting.com