Home - Forums-.NET - Spices.Net - Problem with application config file

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
Problem with application config file
Link Posted: 13-Nov-2006 21:12
gambit avatar
gambit
Total Posts:0
Joined:4/19/2024
I am currently evaluating all sorts of obfuscating tools on the market to be able to choose a \"good\" one.

I noticed the following behaviour with Spices.NET and I am not sure, if I missed an option somewhere or how to come around it.

After obfuscating with Spices.NET my application ignores the contents of its configuration file:
MyApplication.exe
MyApplication.exe.config
that means any changes to the XML file MyApplication.exe.config have no effect!

Does anyone knows a solution for this ?
Link Posted: 14-Nov-2006 06:27
NineRays avatar
NineRays
Total Posts:0
Joined:4/19/2024
Can you send us (mail: )your app, config file and spices.project used for obfuscation to more precisely answer on your question?
If you can't send us your app, please send at least .config and spices.project(.iloprj) for analysis.
Link Posted: 14-Nov-2006 19:51
gambit avatar
gambit
Total Posts:0
Joined:4/19/2024
I made a very simple test application to get rid of all the unnecessary stuff!

It is a simple console application that displays the string in the config file,
That works fine for debug and release, but not for the obfuscated app.
The obfuscated app takes the default value (Spices.NET) instead of “Spices.NET obfuscated” (see below).

image 1
image 2
image 3



    
        
            
        
    
    
        
            
                Spices.Net obfuscated!
            
        
    
Link Posted: 15-Nov-2006 02:10
NineRays avatar
NineRays
Total Posts:0
Joined:4/19/2024
As I have understood, you use custom ConfigurationSectionGroup/ApplicationSectionGroup class to serialize/deserialize some settings from config file.
In this case you should exclude custom ConfigurationSectionGroup/ApplicationSectionGroup class and its public members from obfuscation. Your app uses this class System.Reflection (original member names) to serialize/deserialize data from config file, using class name and its member names to tech data - these names should be untouched.
Link Posted: 15-Nov-2006 02:28
gambit avatar
gambit
Total Posts:0
Joined:4/19/2024
Thanks a lot.
Very fast and precise solution.
Share:

Company  |  Privacy  |  Legal Information

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