when building a desktop app in wpf can you read documentation of problems and safely subsititute 'app.config' when people's answer's refer to 'web.config'?
if so are there any glaring GOTCHAS you have to look out for?
tnx
when building a desktop app in wpf can you read documentation of problems and safely subsititute 'app.config' when people's answer's refer to 'web.config'?
if so are there any glaring GOTCHAS you have to look out for?
tnx
Web.Config is used for asp.net web projects / web services.
App.Config is used for Windows Forms, Windows Services, Console Apps and WPF applications
Your question isn't providing all the information as to where the gotcha's may lie for you.
Can you give us more info on what you are trying to do in terms of these config files?
Here's a nice article.
http://www.cyberactiva.com/dettaglio.asp?id=356
And
http://stackoverflow.com/questions/1380352/problems-with-web-config-and-app-config
Web.config is parsed at runtime, whereas app.config is done at compile time. So if you edit the App.config on the machine then it will not update when you start the service. If you edit the web.config file then this will be checked when the website starts.
I have updated the output config (config.depoly), and the modifications are not read. I have to recompile for the changes to take.