Release:	2012.02.0019
Date:	April 18, 2013
Description:	Hot-fix release

Fixes:

• Using the Object Editor to edit the structure of a SQL stored procedure, results in being unable to edit the SQL stored procedure's signature via the "SQL Body" tab

Release:	2012.02.0018
Date:	April 09, 2013
Description:	Hot-fix release

Fixes:

• Editing a live object whose SQL script is under version control results in the incorrect version of the script being checked out by the add-in

Release:	2012.02.0016
Date:	January 15, 2013
Description:	Minor feature, medium fix release

Enhancements:

• Navigation through the Object Explorer has been significantly improved in all SQL Server Management Studio versions. The speed gain depends on the number of the objects in the database and starts at 500% when working with a database containing a few hundred objects of the same type
• The generation time of the "Database mapping status" report has been significantly lowered particularly on databases mapped to Subversion via native drivers. The speed gain depends on the number of objects in the database and starts at 1700% for databases containing few hundred objects
• Mapping databases to a remote Subversion server via native drivers as well refreshing the Object Explorer for such databases has been greatly improved. The speed gain depends on the number of the object types mapped. For databases containing several hundred objects of different object types, the mapping process can be up to several times faster
• A progress indication dialog is now shown while the "Database vs. Source control differences" report is being generated
• A progress indication dialog is now shown in the "Configure mappings" step of the "Source control wizard", while adding a database to source control
• The add-in doesn't affect the time needed to generate a CREATE script for SQL full text stoplists any longer
• Checking out databases and objects mapped to Subversion is now up to 300% faster

Fixes:

• Navigating databases and tables in the SQL Server Management Studio's Object Explorer on a remote SQL Server connected via VPN is five times slower if the add-in is installed
• ApexSQL Version commands are not disabled for databases that are not linked to source control
• Changes made to the contract object type in the "Visual editor" cannot be saved when VisualSVN is used
• Services created under the queue object type cannot be versioned via the add-in, as an update script is not generated for modifications performed via the "Visual editor"
• Message types cannot be properly handled via the add-in, as an update script is not generated for modifications performed via the "Visual editor"
• The "Modify remote service binding" command via the add-in fails because the update script is not generated
• Updating routes via the "Visual editor" does not work because the update script is not generated
• There is no warning during the add-in's installation process which informs the user if Visual Studio and/or SQL Server Management Studio is running
• The add-in can be uninstalled while SQL Server Management Studio is active resulting in an incomplete uninstall
• The "ErrorFileAlreadyExists" error is encountered after connecting a database to the Team Foundation Server 2010 using a MSSCCI provider and initiating a source control object status refresh
• Cancelling during the "Confirm mapping" step of the "Source control wizard", results in SQL Server Management Studio being non-responsive
• The synchronization script is not updated in the "Generated script" tab after adding a new SQL search property when editing the SQL search property list object
• The "Use version from source control" option in the Select object version dialog, loads the database version when editing a table which differs between the source control and the database
• The "Use version from source control" option in the Select Object Version dialog, loads the database version when editing a procedure which differs between the source control and the database, and was previously edited and checked into the database that was mapped to Subversion via the Native driver
• The changes are automatically applied to a database after object editing, when the "Apply to database after editing" option is set to "Never"
• The Object Explorer context menu commands "Database vs. Source control differences" and "Show database/Source control script differences" don't open the corresponding reports in SQL Server Management Studio 2005 without Service pack 1
• The Help request invoked by F1 or the "?" button while an object edit dialog is active, opens a non-existing web page
• The text of the two options in the Select the object version dialog is not fully visible when using the 120 DPI system font resolution
• The text of the Edit queue dialog options, "Maximum queue readers" and "Poison message handling", is overlapped by their corresponding value entry controls when using the 120 DPI system font resolution
• The Check-out comment dialog text overlaps the comment edit box, and the "Don't show this again" checkbox text is not fully visible when using the 120 DPI system font resolution
• SQL Server Management Studio displays a depreciated "ApexSQL Version Edit" toolbar with all commands disabled
• High memory leakage and CPU load lead to SQL Server Management Studio 2012 unresponsiveness when expanding a database node, in scenarios where 3 or more large databases are linked to Subversion via native drivers
• The error message "Nije uradjen check-out", when updating an object that was not checked out, is not in English
• Immediately after linking a database to a source control, the differences report shows that all database objects are different from their source control versions
• Objects cannot be linked to a source control via Team Foundation Server native drivers if each object type is not mapped to its appropriate subfolder
• The "access to the path <working folder location> is denied" error is shown on attempting to check-out any object, if the database is linked to a Team Foundation Server via MSSCCI drivers
• The "access to the path <working folder location> is denied" or the "Error AccessFailure" error is shown on attempting to check-out any object, if the database is linked to a SourceGear Vault via MSSCCI drivers
• SQL full text stoplists created via system stoplists cannot be processed by ApexSQL Version, as changes applied via the "Visual editor" are not handled
• The "Object reference not set to an instance of an object" error is encountered when attempting to processing SQL FileTables using "Visual editor"
• Database objects removed from source control are marked as different in the "Database vs. Source control differences" report
• Displaying the context menu for any database object linked to source control does not retrieve the correct information on whether the object has been linked to source control
• A checked out without saving, and then changed and saved SQL table is always reported as the same as the version in the source control
• When adding ole members while editing a SQL role, the "Select a database role or user" dialog doesn't have a system menu icon in the top left corner and can be resized to hide all of the UI elements
• Increasing the number of objects significantly increases the time needed for the "Confirm mappings" operation
• The add.in doesn't follow the proper version number form in "Add/Remove Programs"

Changes:

• The Source control wizard requires "/vaultservice" to be appended to the SourceGear Vault server address when connecting to the SourceGear Vault server via the native drivers
• The "Object source control status check-up interval" option has been disabled by default in order to improve SQL Server Management Studio's responsiveness
• The "View history" command has been removed on the database level

Release:	2012.01.0006
Date:	July 27, 2012
Description:	Hot-fix release

Fixes:

• Dropdown on properties panel in Visual object editor dialog is empty when editing all object types excluding Tables
• Evaluation notice dialog is displayed multiple times consecutively when clicking on 'ApexSQL Version' context menu while add-in is in trial mode
• Object script opened using 'View' command is not read-only
• Object Explorer context menu group 'ApexSQL Version' is missing for Table Trigger objects
• 'NO MINVALUE' and 'NO MAXVALUE' options cannot be set when editing Sequence using Visual object editor
• Visual object editor generated script for Sequence has syntax errors when the Sequence has numeric option values larger than 999

Changes:

• Visual object editor dialog 'Script' tab caption has been changed to 'Generated script' for consistency with Table editor dialog

Release:	2012.01.0004
Date:	June 06, 2012
Description:	Initial release

Enhancements:

• The add-in now fully supports the following SQL Server 2012 object types:
• FileTable
• Sequence
• Search property list
• Columnstore indexes
• Poison message handling attribute for queues
• Geometry and geography auto grid tessellation scheme for spatial indexes
• Visual editors have been introduced for editing versioned objects allowing the following to be edited:
• DDL
• Properties
• Extended properties
• Permissions
• Improved security: Certificates cannot be versioned any more

Fixes:

• Context menu commands not applicable for the selected object are always enabled if the add-in is installed under SQL Server Management Studio 2005 pre-Service Pack 1
• A database mapped to a SourceGear Vault server 5.1 repository via Native driver is no longer displayed as mapped after restarting SQL Server Management Studio 2005 pre-Service Pack 1

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