Please don't send this back with a "cannot reproduce" comment. I believe that the attached .sql file proves the bug exists.
When attempting a deploy from datadude within Visual Studio just now I encountered this error:
Rename refactoring operation with key b4b0dfb7-9c4a-4ea2-875b-511ea95fd789 is skipped, element [account].[DF_accountAccount_AccountControllerIsActive] (ISql90DefaultConstraint) will not be renamed to [DF_accountAccountController_AccountControllerIsActive]
C:\Sandbox\PRS\trunk\Src\SQL\FinanceDB\sql\debug\FinanceDB.sql(551,0): Error SQL01268: .Net SqlClient Data Provider: Msg 342, Level 16, State 1, Line 1 Column "account" is not allowed in this context, and the user-defined function or aggregate "account.Default_accountAccountController_AccountControllerIsActive" could not be found.
This occurred when datadude attempted to deploy a default constraint defined as:
ALTER TABLE [account].[AccountController]
ADD [AccountControllerIsActive] BIT CONSTRAINT [DF_accountAccountController_AccountControllerIsActive] DEFAULT [account].[Default_accountAccountController_AccountControllerIsActive]() NOT NULL;
(see line 552 of FinanceDB.sql in attached FinanceDB.zip)
Later on in the script (line 6297) we see the following:
CREATE FUNCTION [account].[Default_accountAccountController_AccountControllerIsActive]
RETURN CAST(1 AS BIT);
Put simply, datadude is attempting to deploy a default constraint BEFORE it has deployed the function that is referenced by that constraint. This is a bug. Plain and simple.
I will attach 2 files:
1. FinanceDB.zip - A zip of FinanceDB.sql - the file produced by a datadude deploy
2. FinanceDB_project.zip - A zip of the datadude project that is throwing this error