How To Refresh Linq-To-SQL Classes After Schema Changes Without Dropping And Adding

All --

Please help. 

I need to know how to refresh Linq-To-SQL classes after schema changes without dropping and adding them.

Now, when I make a schema change (such as add or delete a column to a table), I want to "refresh" the Context.dbml file.

The only way that seems to work is to drop the table from the Context.dbml designer and then add it back in.

Is there a better way to do this?

How are others doing this?

Please advise.

Thank you.

-- Mark Kamoski