I ran into my first problem with LINQ TO SQL a couple of days ago and forgot about it. I ran into again today and decided to let everyone know about it.
What I ran into was if you change an underlying table in SQL Server there is not a way to "refresh" or "sync" the table in the LINQ TO SQL Designer. The only way to get the updated table is to delete the current table from the designer and then add it again to the designer.
A significant problem with this method is if any of your stored procs have a return type of the table being deleted you have to change the return type before deleting the table (or delete the proc and add it in again). For instance if you have a User table and one of your stored procs have the return type of User the table cannot be deleted.
At this point it's not so terrible that I don't want to use it anymore but I'm looking to Microsoft to fix this problem pretty quickly as it's a very ugly "feature".
Technorati Tags:
LINQ,
LINQ TO SQL,
.NET 3.5
posted @ Thursday, January 17, 2008 11:25 AM