All geek questions in one place

Endpoint Software Configuration vs. web / app.config

Are there any thoughts in this? Personally, I believe that managing endpoints in configuration files is a pain. Are there any pros and cons to doing one on top of the other?

+3
source share
8 answers

Only points in favor of configuration files from me.

Managing endpoints in configuration files means that you do not need to update your application if (or maybe I should say when) the endpoints change.

You can also have multiple instances of an application that works with different endpoints.

+5
source

config, , .

, WCF, , , XML-, , . , , , .

, Visual Studio "", XML, VS , , , .

:

xml- , . ;

/ .dll, WCF-.

, , CommonClients.dll, WCF - , " 100 xml, app.config , ". , , .

"".NET 3.5, , wcf, . , , , nnumber, . , .NET 4 .

+3

, , . , "" "UAT" "".

- , . - enpoint, , .

+2

app.config , . . , ( , ) . , . : " ". .

+1

, . , , , userSettings, system.ServiceModel.

+1

. , . , .

, ( ) , . , , , , , . , .

+1

, . .

0

Check out the .NET StockTrader app . It uses a repository to store configuration data and has a separate configuration management application. The settings and structures are quite advanced, and there is an honest cue ball for those who look like me, only has the basics of WCF configuration, but I would say it's worth a look.

0
source

Source: https://habr.com/ru/post/1710760/

More articles:


All Articles