For example it may delete a attributes, delete elements, etc. The problem with transforming the web.config that you are currently running is that a transform can perform destructive actions to the web.config. Obviously you’ll have to be careful with passwords depending on your application/team. This is the transform that is applied when you publish your application to the “production” environment. This would make changes to the web.config which are required for the target environment. This is the transform that is applied when you publish your application to the development staging environment. You should strive for this to work on dev machines without changes. For instance you could use localhost for DB strings, and what not. Ideally you should get this to be standardized. This is the config file which developers should use locally. When i publish a web app, visual studio automatically transforms the web.config based on myįirst let me explain, as I did to that question, the purpose of the files: web.config//. The question states: Hello, I want to use the web.config transformation that works fine for publish also for debugging. For example here is just one question on StackOverflow. I have heard a lot of questions and confusion regarding and. DIsclaimer: You may experience some in-consistent behavior using this technique.
0 Comments
Leave a Reply. |