By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,986 Members | 2,042 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,986 IT Pros & Developers. It's quick & easy.

Embeding a module into and executable

P: n/a
I have an application which is similar in function to Setup.exe. The user
downloads it, uses it once in most cases and throws it away. I am trying to
coax .NET into making it one file and it is fighting me all the way.

If I do a full build from my source files I get what I want, one exe file.
The problem comes when build the program as a library and then try to make
an exe file out of it. I have to add this extra step because the code
obfuscator works on libraries, it cannot take a "signed and sealed" exe file
and obfuscate it into another exe. If I try to add the library to a Visual
Studio project it simply creates a reference to the external module. I get
a tiny exe file which breaks if run without the larger module file in the
same directory. I tried using the AL.exe tool which has an /embed directive
which looked promising but that turns out to only embed resources.

Does anyone have a solution to this? Maybe there are security issues or
something that would cause Microsoft to disallow embedding of libraries
without source code. It seems like a strange restriction.
Nov 22 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
If you want to merge/link .NET assemblies together, you
can use our linker tool:

http://www.remotesoft.com/linker

I think Microsoft research has a free ILMerge tool, search
google to find it.

By the way, why would an obfuscator not to handle an EXE?
Are you really sure? it seems very strange.

Our salamander obfuscator,
http://www.remotesoft.com/salamander/obfuscator.html
will automatically resign EXEs/DLLs if they have strong
names.

Huihong
Remotesoft
-----Original Message-----
I have an application which is similar in function to Setup.exe. The userdownloads it, uses it once in most cases and throws it away. I am trying tocoax .NET into making it one file and it is fighting me all the way.
If I do a full build from my source files I get what I want, one exe file.The problem comes when build the program as a library and then try to makean exe file out of it. I have to add this extra step because the codeobfuscator works on libraries, it cannot take a "signed and sealed" exe fileand obfuscate it into another exe. If I try to add the library to a VisualStudio project it simply creates a reference to the external module. I geta tiny exe file which breaks if run without the larger module file in thesame directory. I tried using the AL.exe tool which has an /embed directivewhich looked promising but that turns out to only embed resources.
Does anyone have a solution to this? Maybe there are security issues orsomething that would cause Microsoft to disallow embedding of librarieswithout source code. It seems like a strange restriction.
.

Nov 22 '05 #2

P: n/a
Thanks, that is exactly what I was looking for.

Since you asked, we were trying to obfuscate "on the cheap". Since the
original source was in Java we used the OpenSource ProGuard obfuscator on
the Java byte code and then used jbimp.exe to convert it to obfuscated IL
code. The jbimp.exe tool can create an exe but with few options, so we have
jbimp make a library instead and then use AL.exe to add the icon, version
info, etc. Therefore it's ironic that the final piece of the puzzle would
be filled in by the very people we were trying to avoid paying! This is a
"proof of concept" project and once funded yours will be the obfuscator we
buy, I PROMISE!

Mike
Nov 22 '05 #3

P: n/a
Got it, thanks for sharing the inside story. :)
-----Original Message-----
Thanks, that is exactly what I was looking for.

Since you asked, we were trying to obfuscate "on the cheap". Since theoriginal source was in Java we used the OpenSource ProGuard obfuscator onthe Java byte code and then used jbimp.exe to convert it to obfuscated ILcode. The jbimp.exe tool can create an exe but with few options, so we havejbimp make a library instead and then use AL.exe to add the icon, versioninfo, etc. Therefore it's ironic that the final piece of the puzzle wouldbe filled in by the very people we were trying to avoid paying! This is a"proof of concept" project and once funded yours will be the obfuscator webuy, I PROMISE!

Mike
.

Nov 22 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.