Home - Forums-.NET - Spices.Net - Verification of Assemblies getting a lot of errors...

Spices.Net

NET code security, tools to protect, obfuscate, tamper defense, code and data safety, recover, convert, optimize, explore, browse and analyze .Net software.

This forum related to following products: Spices.Net Suite, Spices.Net Obfuscator, Spices.Net Decompiler
Verification of Assemblies getting a lot of errors...
Link Posted: 23-Aug-2010 23:03
avatar
CrisDiaz
Total Posts:40
Joined:8/1/2010
I can send it from a different email account if you need me to send it again.

Best regards,
ct
Link Posted: 23-Aug-2010 23:08
avatar
ninerays
Status:Moderator
Total Posts:189
Joined:11/26/2009
I'm sorry, but we didn't receive your email (I've searched in spam also). Did you zip your attachment and change the extension to a .zap or .txt before attaching to your mail?
Link Posted: 23-Aug-2010 23:12
avatar
CrisDiaz
Total Posts:40
Joined:8/1/2010
No, it was a .rar file.

I'll resend it now.

Best regards,
ct
Link Posted: 23-Aug-2010 23:18
avatar
CrisDiaz
Total Posts:40
Joined:8/1/2010
I've just resent the project.

It's called CMConvert.zap.

It's out of my mailbox.

Did you get it?

I am going to send it from another email account as well.

Please let me know if you get it and which email address you got it from.

Best regards,
ct
Link Posted: 23-Aug-2010 23:29
avatar
ninerays
Status:Moderator
Total Posts:189
Joined:11/26/2009
Thanks, now we got it.
Link Posted: 24-Aug-2010 08:39
avatar
CrisDiaz
Total Posts:40
Joined:8/1/2010
I've stared and stared and stared at this for hours and hours yesterday.

Athough I could see some of the conflicts in the metadata, I have "no" idea how to resolve them.

Also, I have "no" idea what the varargs errors mean.

It appears that the issue is releated to com interop, but I can't be sure.

I am eagerly awaiting some feedback from you.

Best regards,
ct
Link Posted: 26-Aug-2010 00:57
avatar
ninerays
Status:Moderator
Total Posts:189
Joined:11/26/2009
Thanks again for the assembly for tests, we've solved this problem.
Problem was in incorrect processing of type attributes in procedure of assembly verification, so don't worry about obfuscation quality.
We plan to publish fixed version (cumulative update) to the end of this week.
Link Posted: 26-Aug-2010 01:07
avatar
CrisDiaz
Total Posts:40
Joined:8/1/2010
:) That's really good to hear! Thank you!

If you don't mind, please let me know as soon as the new version is available.

Best regards,
ct
Link Posted: 26-Aug-2010 01:09
avatar
ninerays
Status:Moderator
Total Posts:189
Joined:11/26/2009
Ok, I'll let you know when fixed version will be available for downloading.
Link Posted: 30-Aug-2010 03:47
avatar
ninerays
Status:Moderator
Total Posts:189
Joined:11/26/2009
Let you know that the fixed version of Spices.Net (v5.8.0.44) is available for downloading. Also this version supports macros in ObfuscationEvents:
Available for Obfuscation event macro Value Description
BeforeAssemblyGeneration,
BeforeAssemblySign,
AfterAssemblyGeneration,
AfterAssemblySign		 %TargetPath% d:\myProject\Output\MyAssembly.dll The full path of the obfuscated assembly, with file name
%TargetDir% d:\myProject\Output\ The output directory, where obfuscated assemblies generated
%AsmFileName% MyAssembly.dll The file name of the assembly
%AsmFileNameWithoutExtension% MyAssembly The file name of the assembly, without extension
%SourcePath% d:\myProject\bin\Release\MyAssembly.dll The full path of the original assembly, with file name
%SourceDir% d:\myProject\bin\Release\ The full path to the original assembly
BeforeProjectGeneration,
BeforeProjectObfuscation,
BeforeProjectSign,
AfterProjectGeneration,
AfterProjectObfuscation,
AfterProjectSign		 %ProjectName% MyProject.iloprj The file name of the project
%ProjectNameWithoutExtension% MyProject The file name of the project, without extension
%ProjectFileName% d:\MyProject\MyProject.iloprj The full path to the project, with file name
%ProjectDir% d:\MyProject\ The path to the project
Solution events:AfterObfuscation,
BeforeObfuscation		 %SolutionName% MySolution.ilosln The file name of the solution
%SolutionNameWithoutExtension% MySolution The file name of the solution, without extension
%SolutionFileName% d:\MyProject\MyProject.iloprj The full path to the solution, with file name
%SolutionDir% d:\MyProject\ The path to the solution

For example, to copy the .pdb files associated with obfuscated assemblies, you can specify following command: copy %SourceDir%%AsmFileNameWithoutExtension%.pdb %TargetDir% in the AfterAssemblyGeneration or AfterAssemblySign obfuscation event
Share:

Company  |  Privacy  |  Legal Information

© 1999-2024 9Rays.Net. All rights reserved.