SqlMetal DBML1055 error

I'm getting this error with the June .Net FX 3.5 CTP:

error DBML1055: The DeleteOnNull attribute of the Association element 'FK_Account_Currency' can only be true for singleton association members mapped to non-nullable foreign key columns.

This is using almost the same command line (changed xml to dbml) from a project that worked without problems with the May 2006 CTP.

sqlmetal /pluralize /server:.\sqlexpress /database:%projectName% /dbml:"%metadataDir%Model.DB.tmp"

Any ideas as to why this is not working?

Regards,

Pablo

[595 byte] By [melkor] at [2008-1-6]
# 1
That error message is wrong. We've fixed it already.
MattWarren-MSFT at 2007-9-28 > top of Msdn Tech,Visual Studio Orcas,LINQ Project General...
# 2
Where can I get that fix!?
melkor at 2007-9-28 > top of Msdn Tech,Visual Studio Orcas,LINQ Project General...
# 3
I too would like to know how to get the fix...

I am getting the same error.

Davidd at 2007-9-28 > top of Msdn Tech,Visual Studio Orcas,LINQ Project General...
# 4

I'm experiencing the same error message. Is there a fix available Matt?

AndersBorum at 2007-9-28 > top of Msdn Tech,Visual Studio Orcas,LINQ Project General...
# 5

Ditto, me too. Please provide a link to the fix or at least a suitable workaround other than removing the cascade setting from the DB?

Is there an acceptable way to have Visual Studio ignore this error?

Thanks.

kfrost at 2007-9-28 > top of Msdn Tech,Visual Studio Orcas,LINQ Project General...
# 6
bump.... Sad

bodhialok at 2007-9-28 > top of Msdn Tech,Visual Studio Orcas,LINQ Project General...
# 7

FYI, so far, I'm opening the DBML file and doing a replace on the DeleteOnNull="true" and replacing true with false. Not ideal but looks to have gotten me past the compiler error.

kfrost at 2007-9-28 > top of Msdn Tech,Visual Studio Orcas,LINQ Project General...
# 8

I'm using VS2008 Beta 2, but the error is still there. How can I get the fix?

Thanks!

VS05User at 2007-9-28 > top of Msdn Tech,Visual Studio Orcas,LINQ Project General...
# 9

The fix will appear in the next release, which as far as I know will be RTM.

MattWarren-MSFT at 2007-9-28 > top of Msdn Tech,Visual Studio Orcas,LINQ Project General...

Visual Studio Orcas

Site Classified