 |
Infralution Support Support groups for Infralution products
|
View previous topic :: View next topic |
Author |
Message |
PaulS
Joined: 03 Jul 2013 Posts: 24
|
Posted: Fri Sep 19, 2014 12:37 am Post subject: Initial experience |
|
|
I finally was able to build my project with Encryptor. I had to disassemble, edit .il files, and re-assemble several unsigned 3rd party DLLs to get the signing to work. This took all day to figure out.
My visual studio solution has 3 .exe projects, so I assume I make 3 bootstrap projects, then name the output of the bootstrap projects the same name as my original exe files. Then edit the setup project to reflect these changes, take out the old exe files, and add the new ones. My automated build steps will not change at all. |
|
Back to top |
|
 |
Infralution
Joined: 28 Feb 2005 Posts: 5027
|
Posted: Sat Sep 20, 2014 2:04 am Post subject: |
|
|
.NET Encryptor does require the entry (exe) assembly to be signed. This does also mean that any DLLs used by the exe have to be signed as well. I assume that this is where you had the problem with unsigned third party DLLs. If they are from a commercial company then they should already be signed - if not I would be asking the company to sign the assemblies. For open source components you typically have the source code and can easily sign them yourself.
Quote: | My visual studio solution has 3 .exe projects, so I assume I make 3 bootstrap projects, then name the output of the bootstrap projects the same name as my original exe files. Then edit the setup project to reflect these changes, take out the old exe files, and add the new ones. My automated build steps will not change at all.
|
That is correct. _________________ Infralution Support |
|
Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|