CODEWITHSUNDEEP
linqlinq-to-sql
alchemical
alchemical

Reputation: 13995

LINQ to SQL - How to deal with changes to database

I'm fairly new to LINQ to SQL, so I could be missing something basic here.

I created a LINQ to SQL layer, generated all the dbml files etc., and created a LINQ query which worked fine. I then made a change to the database, and wanted to get that change reflected in the ORM layer. To do this, I deleted my ORM layer and created a new one (may not be the best way?).

Now my code is not able to see the datacontext object in intellisense and won't compile. I imagine this may be something simple, but I'd also like to understand the bigger picture of how to update the LINQ to SQL ORM layer when the database changes.

Upvotes: 0

Views: 464

Answers (3)

Robert Harvey
Robert Harvey

Reputation: 180858

You can also use SQLMetal to update your DBML classes. Some people even write a script or batch file to automate the process.

Upvotes: 0

Frank Schwieterman
Frank Schwieterman

Reputation: 24480

Yeah, you don't want to delete your whole DBML file. Open it in the designer, and delete the table that changed. Then drag'n'drop it again from the "Server Explorer" (in the view menu). This will load an updated copy of teh database... Note that if server explorer is already open while you make the change to the SQL schema, you'll need to refresh server explorer so it has the latest versions.

The drawback to this approach is that if you do customizations to the table in the DBML, those need to be redone. This is an infrequent case for me.

Upvotes: 2

JoshJordan
JoshJordan

Reputation: 12975

I remember having this issue a bunch. The fix is simple, really. Rebuild your solution! The DataContext and other such classes are generated during a build.

Quite a headache - I wish the DBML tool did this for you when you closed it.

Upvotes: 0

Related Questions