Is there a way to force LINQ-to-SQL to treat a column as dirty? Globally would suffice....
Basically, I\'ve got a problem with some audit code on a legacy system tha
If you want to go down the [dirty] reflection route, you could try something along the lines of:
1) Override SubmitChanges
2) Go through the change set
3) Use reflection to get hold of the change tracker for each updated object (see What's the cleanest way to make a Linq object "dirty"? )
4) Make the column dirty (there's a dirtyMemberCache field in the StandardTrackedObject class)