For ASP.NET developers who are used to name their configuration files “web.config” , working with configuration files of Windows forms application in VS.NET is a little bit tricky. Let’s assume that you have an application called “TestConig”<\/STRONG> which generates the executable TestConig.exe. If you ever decide to add a config file to this app using visual studio ,there are couple of things to remember: Deployment<\/STRONG>: In deployment you need to make sure that the App.config file is renamed TestConig.exe.config or just simply pick up TestConig.exe.config from debug or release folder.<\/P><\/p>\n","protected":false},"excerpt":{"rendered":" For ASP.NET developers who are used to name their configuration files “web.config” , working with configuration files of Windows forms application in VS.NET is a little bit tricky. Let’s assume that you have an application called “TestConig” which generates the executable TestConig.exe. If you ever decide to add a config file to this app using […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[],"tags":[],"class_list":["post-1128","post","type-post","status-publish","format-standard","hentry"],"_links":{"self":[{"href":"https:\/\/blogs.devhorizon.com\/reza\/wp-json\/wp\/v2\/posts\/1128","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.devhorizon.com\/reza\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.devhorizon.com\/reza\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.devhorizon.com\/reza\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.devhorizon.com\/reza\/wp-json\/wp\/v2\/comments?post=1128"}],"version-history":[{"count":0,"href":"https:\/\/blogs.devhorizon.com\/reza\/wp-json\/wp\/v2\/posts\/1128\/revisions"}],"wp:attachment":[{"href":"https:\/\/blogs.devhorizon.com\/reza\/wp-json\/wp\/v2\/media?parent=1128"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.devhorizon.com\/reza\/wp-json\/wp\/v2\/categories?post=1128"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.devhorizon.com\/reza\/wp-json\/wp\/v2\/tags?post=1128"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
1) Add an new item to your project and name it App.config<\/STRONG> which is basically nothing more than an XML file.
2)Build your project and look in the build output directory. The binRelease or binDebug directory for C# projects
Surprisingly you’ll see that there is a file called TestConig.exe.config<\/STRONG> and App.config is not what the configuration file ends up getting called, this is just what it’s called inside a Visual Studio .NET project.
I guess the question is that why VS.NET behaves like that? and the answer is simple:
TestConig.exe.config file is a copy of the App.Config file.VS.NET copies it so that you don’t need to maintain a separate debug and release version of this file. And they use the name TestConig.exe.config because that’s the magic name they’ve chosen for this behavior<\/P>
\n