Linq2sql code generator misbehaving

Posted by Martin on Stack Overflow See other posts from Stack Overflow or by Martin
Published on 2010-03-22T00:24:05Z Indexed on 2010/03/22 0:31 UTC
Read the original article Hit count: 406

Sometime the linq2sql just makes its mind up about things. I've been pulling my hair for the past hours trying to work out what I'm doing differently from all the other times when I don't get ForeignKeyReferenceAlreadyHasValueException.

Turns out that

    if (this._Activity.HasLoadedOrAssignedValue)
    {
        throw new System.Data.Linq.ForeignKeyReferenceAlreadyHasValueException();
    }

is present on my primary key in this particular table, and in no other. No matter what I do with the association, I've even tried deleting and dragging the thing back to the designer, it's still there and I'm sure it's not supposed to be.

I know why, of course, but I don't know why, so to speak. A while back the association went the other way. Whereas I've left that era behind me, the code generator seems to exhibit phantom pains. The same phenomenon, is responsible for me having to change the namespace in the designer.cs everytime I make changes in the designer. I made the mistake of renaming my namespace and the code generator just doesn't get it.

Somebody please help this poor boy out.

© Stack Overflow or respective owner

Related posts about linq-to-sql

Related posts about linq-to-sql-designer