Updating web config
With either method, your custom settings can be reapplied post-upgrade.
I have a huge web application that have consists of many modules, DLLs and source code files.
Here is the code if you really want to change the value in web.config.
Codes: Sincerely, Zong-Qing Li Microsoft Online Community Support Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question.
Changes that you define through the object model or through XML are always applied when you create a Web application.
Web.config files are contained in the following folders within the file system: When a Share Point Foundation Web application is created, a top-level web.config file is placed within the content root folder of the Web application, which defines configuration settings for the server such as HTTP handling for Web Parts.
If you want to change the value in web.config permanently, you need to access and write into the web.config file.
However you are required to restart your appplication, to let the value get updated.
For an example that shows how to modify settings programmatically, see How to: Add and Remove Web.config Settings Programmatically.
I wasn't suggesting that you remove the xmlns as a permanent solution, but rather to help identify a bug iis MSDeploy.
If it starts working when the xmlns is removed, that means there is still a product which can be fixed before final release later this summer.
Another web.config file used for Web Part resources is placed in a \wpresources folder within the same root folder.
Warning Changes that you make to any of the web.config files that are built into Share Point Foundation, or that are created when a Share Point Foundation Web application is created, may be overwritten when you install updates or service packs for Share Point Foundation, or when you upgrade an installation to the next product version.
Search for updating web config:
This seems like an easier way to do it, without having to go through my DBA to get a small table deployed, having to make a stored procedure, and write the ADO. I think someone mentioned to me being able to use WCF but I think they were mistaken.