XML as storage backend or use XML in build task

Apr 22, 2009 at 10:37 AM

It would be of great benefit if we could have the tool use an XML file as it's data backend and at the very least, have the ability in the msbuild task to refer to an exported settings file rather than a DB. In most environments the settings are confidential and storing ALL the settings for ALL the environments in any one given environment's DB is too much of a risk and versioning / synching becomes an issue if left unchecked.

We welcome the idea of having the configuration DB tables seperate from our build environment. To bridge the gap we would export the settings from the DB to an source controlled XML file and then use MsBuild to determine the correct settings from this file.

What do you think?

Aug 13, 2009 at 11:43 PM

Hi Hein,

Just seen your comment, (sorry for the delay).  There is already import/export features in the tool which allow you to do just that.  You can manage the settings in the application for multiple projects and environments and then just export them to files and keep them as solution artefacts as required.

Although you can already do this, ive added some other utility features which should help you do similar things to this in the next release due in a few days.