Make RedGateDatabaseInfo.xml easier to merge
When we look at the RedGateDatabaseInfo.xml file, it appears as one long line of text. Merging this is nigh on impossible because the one line conflicts. It would be nice if it was written in a pretty xml format to help with merging
Geoff Pate
shared this idea
Form Source Control version 2.1, RedGateDatabaseInfo.xml should now be in a more structured format.
Please comment on this suggestion if this new structure does not meet your requirements.
Please visit our product page for more information on the latest version of SQL Source Control:
http://www.red-gate.com/products/sql-development/sql-source-control/
-
Kieron O'Connor
commented
Some problems we have encountered when merging this file are:
The encoding on the file in TFS is set to utf-8 but the xml declaration has it as utf-16. This caused a problem with VisualStudio when the file was edited manually as it could no longer do a compare.
Can it not just infer the <Count /> element?
When the merge goes wrong e.g. a script is checked into Data\*, but not added to RedGateDatabaseInfo.xml, you can then not re-enable the table as static data as it cannot check in the change. Is there a better way for it to cope with this issue? Can it fix the issue automaitcally or at least show a warning as SQL Compare does when dealing with a scripts folder?