2010 Database Projects in RC
For Database Projects there are no major changes since the Beta 2 release other than numerous bug fixes and other incremental improvements.
Here are a couple of notes for known issues in the RC release.
1.) There are 6 deprecated deployment options. These options are no longer supported. These options did not provide true benefits to deployment automation so they have been removed. If you have previously checked these in your deployment options you will have to manually remove these options from Database.sqldeployment file by hand editing the file. These options include: IgnoreAutoGeneratedNames; IgnoreBodyDependencies; IgnoreCollations; IgnoreFileAndLogFilePath; IgnoreFileSize; IgnoreFullTextCatalogFilePath; IgnorePasswords; IgnoreQueueEventNotifications.
The error you will get will be similar to:
*** SQL00256 <ProjectPath>\sql\debug\<Project>_Database.sqldeployment (0,0) The deployment property IgnoreQueueEventNotifications could not be used to configure deployment. *** The deployment configuration file could not be loaded. Deployment cannot continue
2.) You experience issues building SQL database project on 64-bit installation of TFS 2010 RC Build Controller. Receive an error indicating that the .targets file cannot be found. You must copy the targets to the correct directory and register them. The steps to accomplish that is documented here on the forums.
Both of these issues will be resolved in the RTM release.
The new features in 2010 are listed here on the Beta 2 Release announcement.
GDR Power Tools will not be released
Given that the 2010 release candidate is available and contains all the power tools previously identified for the GDR Release we have decided to not release the Power Tools for the GDR version of the product. In 2010 you can find the Power Tools that were previously release, but not in the GDR release. These Power Tools include:
- Data Generation Wizard – This is in the 2010 RC release, but is now called Data Transform Plan. This feature creates a Databound Generation Plan for a whole database for you instead of having to manually create it.
- Expected Schema Unit Test Condition – Determines if the columns and data types of the result match those specified for the test condition.
- Data Checksum Unit Test Condition – Determines if the checksum of the result set returned from the Transact-SQL script matches the expected checksum specified in the test condition.
Thanks and have fun evaluating Visual Studio 2010.