Sandbox Compare is for use with dbproj files, which are Database project files generated with DBPro (not tested on VS 2008 version)

TOC

File
Screen shoot
Features
Requirements
What is SandBox Compare?
What is the Point?

File: SandBoxCompare.zip (16.35 kb)
(note this is Beta software! Highly reconmend backing up the dbproj file before saving over it)

Screen shoot:

Features:

• Highlights and has a count for the number of differences
• Highlights and has a count for the missing elements (nodes present in the user file but not the main)
• Copy the selected node (click on a node its information is shown in the bottom right corner)
• Copy all differences and missing nodes
• shows the Xpath for selected the node (I like that one :) )
• allows the user to specify a different output (Highly recommend backing up the dbproj before saving over it)

Requirements

• .Net 2 framework

What is SandBox Compare?

It’s a very small tool, which allows the developer to compare the contents of his/hers dbproj.user file to the dbproj file. The GUI will highlight inconsistencies allowing the user to easily scroll to the difference and then copy the required change from the dbproj.user to the dbproj file.

Whats the point?

Well to answer this one, you will have to know why there are 2 files, not just one. Well the dbproj file is the main one, this will be saved in Source control and be used by the build server (thus keeping this upto date is critical). On the other hand the dbproj.user is like a "Sandbox" it can differ slighlty between developers where the developer may want or require a slightly different settings.

"This is done this way, because target database and target connection are deployment artifacts which most of the time very by user. You can set a value in the dbproj file, if you want to do this, mainly because you would be using something a like a build server like Team Build which does not have a dbproj.user file.-GertD"

Taken from
<http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1603131&SiteID=1>

On the local development box (with lets say VS 2005 and DB Pro), the developer can alter the project properties, however some settings will be persisted into your dbproj.user file. (Creating a safe sandbox to test new settings) The combination of both files is used to compile and deploy from the developer box. However when it comes to the updating the dbproj file to save into Source Control, the developer will have to manually look at both files in a text editor and copy the new (required) settings over. Now this is where SandBox Compare comes in, you can now open the 2 files to be shown the differences highlighted for you. Then it’s all up to you to change the file by clicking on a button! Phew no need to look at 100's of lines of XML :P

I hope you like it!