Visual Studio 2010 Release Candidate bug: SQL deployment property IgnoreFileAndLogFilePath

As you are probably aware by now, Microsoft this week made available the Release Candidate of Visual Studio 2010. It's looking like a nice product but still has a few issues.

I was keen to upgrade an existing database solution I am working on so opened the solution and allowed the project upgrade wizard to complete. Everything looked great. All my projects were there, all the database objects and code were there, and it built successfully. But it wouldn't deploy. I would get this error on deployment;

------ Build started: Project: BillingDB, Configuration: Debug Any CPU ------
BillingDB -> D:\VS 2010 tests\Billing\Database\sql\BillingDB.dbschema
------ Deploy started: Project: BillingDB, Configuration: Debug Any CPU ------
D:\VS 2010 tests\Billing\Database\sql\Billing_BillingDB.sqldeployment(0,0): Error SQL00256: The deployment property IgnoreFileAndLogFilePath could not be used to configure deployment.
BillingDB.dbschema(0,0): Error TSD01234: The deployment configuration file could not be loaded. Deployment cannot continue
Done executing task "SqlDeployTask" -- FAILED.
Done building target "DspDeploy" in project "BillingDB.dbproj" -- FAILED.
Done executing task "CallTarget" -- FAILED.
Done building target "DBDeploy" in project "BillingDB.dbproj" -- FAILED.
Done building project "BillingDB.dbproj" -- FAILED.

Build FAILED.
========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========

After some investigation it seems that the VS 2008 database deployment property IgnoreFileAndLogFilePath is no longer available in VS 2010, and that the upgrade process for database projects does not delete or modify this setting. Selecting Edit for the sqldeployment options, making a change, then saving the change, also does not remove the property from the file.

The workaround is to open the <project>.sqldeployment file in an editor of your choice and delete the line containing;

<ignorefileandlogfilepath>True</ignorefileandlogfilepath>

Save the file and your database project should now deploy successfully.

I didn't investigate further to see if there were any other deployment properties that no longer exist but now know how to fix it if I get the problem again.

I created a Microsoft Connect bug detailing the problem and I have had offline verification that it is a bug by Microsoft staff. They have now scheduled this to be fixed for the RTM of VS 2010.