Release:	2012.01.0002
Date:	April 25, 2012
Description:	Beta release

Enhancements:

• Add-in now works in SQL Server Management Studio 2012
• Add-in now supports SQL Server 2012

Fixes:

• 'Object <object name> not found in the database' error is encountered when using Update Object | To Specific Version in Source Control command for User Defined Type object
• Update Source Control command checks in an empty object script to the source control repository if the object was previously modified
• 'Method not found' error is encountered when using Update Object | To Specific Version in Source Control command if ApexSQL Refactor 2011.01 add-in is present
• 'The type initializer for 'ApexSql.Common.Activation.DllActivationManager 1' threw an exception' error is encountered when attempting to Check for Updates if ApexSQL Complete 2012.01 add-in is present
• 'Object reference not set to an instance of an object' error is encountered after linking a database to source control if the database was taken offline
• Database and source control versions of a recently mapped and unchanged table object will be reported as different when checking the table out
• Add-in log file contains log entries from other installed ApexSQL SQL Server Management Studio add-ins
• ‘ApexSQL Edit Automatic Operation’ comment is used when a new object script is checked in via the Update Source Control command
• Source Control Wizard opens ApexSQL Complete help when that add-in is installed
• 'Value does not fall within the expected range' error is encountered when using Add Object to Source Control command after modifying source control linked database’s working directory
• Background source control to object explorer object status refreshing stops working over time
• Object's script is checked in source control after closing the object's editing differences dialog
• '[Online] info operation error for...' error is encountered during object check-in if the user password the Subversion source control repository has been changed
• Logo image displayed in add-in generated reports is incorrect
• 'Could not connect to...' error is encountered after cancelling the source control login dialog appears after 'Add Object to Source Control', 'View', 'Edit', 'Update Source Control' or 'Remove Object from Source Control' commands are executed
• View Labels command for database linked to Subversion repository using Native drivers will display two messages that Subversion labels aren’t supported instead of one
• Source Control Wizard dialog doesn’t remember previously configured size and location
• Source control operation warning message dialogs have ApexSQL Refactor or ApexSQL Complete title when those add-ins are also installed
• ‘The database was successfully mapped to Source Control’ dialog doesn’t have the add-in name in the title

Changes:

• Source Control Wizard | Configure Mappings Export and Import file save/load dialogs default location is 'user's documents folder\ApexSQL\Version' now
• Object Edit command now displays the database and source control version selection dialog before the check out dialog if the database and source controlled object script are different

Release:	2012.01.0001
Date:	January 16, 2012
Description:	New product, Alpha release

Enhancements:

• Allows database, group and individual object versioning
• Native support for Microsoft Visual SourceSafe, Subversion, Team Foundation Server and SourceGear Vault
• Support for all MSSCCI-compliant source control systems
• Allows editing and automatic updating of both live objects and their versioned scripts
• Generates comprehensive reports on live and versioned object differences
• Displays the versioned object change history
• Performs version control operations on multiple objects simultaneously
• Provides configurable object to versioned script mappings
• Supports SQL Server 2008 R2, 2008 and 2005 SP1

Known issues:

• Background source control to object explorer refreshing stops working over time
• ApexSql.SourceControl.Exceptions.OperationException error is encountered if the password for connecting to a Subversion server is changed on the server itself