5/2/2024 2:31:22 AM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss the use of .NET Extensions in SalesLogix version 7 and higher. View the code of conduct for posting guidelines.
|
|
|
|
Configuration settings with .NET Extensions
Posted: 11 Jul 10 8:58 AM
|
| Does anyone have a good pattern for configuration settings and .NET Extensions. With your typical .NET application your dll's can read configation settings from an app.config or web.config file that get's built with the .EXE or deployed with a web site. Currently, we are storing connections strings to other databases in our SalesLogix database and passing those in as parameters to our .NET Extensions, which is fine and makes environment refreshes (test, staging, etc.) relatively painless but it's starting to get more complicated now that we want to call a web service from a .NET extension. Thanks. |
|
|
| |
|
Re: Configuration settings with .NET Extensions
Posted: 20 Oct 10 7:12 AM
|
fiogf49gjkf0d Raul, the best we could come up with is to store the settings (connection strings) in the CUSTOMSETTINGS table in the SalesLogix database. I think that is what the table is for anyway and it works fine as long as in your database refresh procedures into other environments you make sure the settings are accurate for that environment (you don't want your test environment pointing to your production database). |
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|