![]() Thus giving a consistent way of updating configuration files for both web.config and app.config files #Powershell xml tools update#```The values in this **parameters.xml** file can be updated using a CI/CD replace tokens task, we use Colin's (), (), in exactly the same way as we would for a **web.config** Finally the following PowerShell can be used to update the **app.config** from this **parameters.xml** ```My extension generates a tokenised **parameters.xml** file``` For example, if we have the app.config``` C:ABC1111 C:abc2222 We wanted to extend this to configuring services and the like where for example a DLL based service is configured with a file The injection process of the parameters.xml into a web.config file is automatically done as part of the WebDeploy process (or a VSTS extension wrapping WebDeploy), but if you want to use a similar model for app.config files then you need some PowerShell. ![]() ![]() It makes it easy to take release variables and write them, at deploy time, into a parameters.xml file to be injected into a machine’s configuration. ![]() This release adds support for generating parameters.xml files from app.config files as well as web.config files Why you might ask why add support for app.config files when the parameters.xml model is only part of WebDeploy? Well, at Black Marble we like the model of updating a single file using a tokenised set of parameters from within our DevOps CI/CD pipelines. I recently released an updated version of my Generate Parameters.XML tool for Visual Studio. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |