in
Several ways to save Connectionstring in the .NET Data Access Architecture Guide:
In an Application Configuration File Advantages: Easy to deploy, easy programming control, support dynamic update Disadvantages: Security In a Universal Data Link (UDL) File (Supported Only by The Ole DB. NET DATA Provider) Advantages: Standard Solution Disadvantages: Performance, Safety, no support: security, easy programming shortcomings: deploy in a custom file advantages: no shortcomings: additional coding, deploying in the COM Catalog Advantages: Management Disadvantages: Security, Deployment, Component Maintenance Considering these methods, the first is the most common, but we do now is a C / S project. Since the safety of the anti-compilation, the security of the connection string is a problem, even if you use encryption, you can According to the anti-compiled thing, it will be connected to the confusing stroke, but according to the company's situation, it is impossible to buy the obfuscator. So it is currently thinking with Delphi to do a DLL. Inside the connection string, finally call it by .NET. Very simple question how to change it? Do you have any good way, please advise
