Sign in
Dinesh's Cyberstation
Translate This Page
Translate this page
Powered by
Microsoft® Translator
Options
About
Email Blog Author
RSS for posts
Atom
RSS for comments
OK
Search
Tags
Data Access
LINQ
Archive
Archives
October 2010
(1)
March 2009
(3)
August 2008
(2)
July 2008
(2)
June 2008
(4)
May 2008
(5)
April 2008
(1)
November 2007
(2)
October 2007
(8)
July 2007
(2)
June 2007
(5)
July 2006
(2)
June 2006
(1)
May 2006
(2)
March 2006
(5)
October 2005
(3)
September 2005
(7)
June 2005
(5)
April 2005
(2)
March 2005
(2)
April 2004
(1)
Posts
Subscribe via RSS
Sort by:
Most Recent
|
Most Views
|
Most Comments
Excerpt View
|
Full Post View
Dinesh's Cyberstation
An account of Bill Gates' farewell
Posted
over 5 years ago
by
Dinesh Kulkarni - MSFT
1
Comments
An unusual subject for this blog that has been mostly about components I have worked on. But the event yesterday was memorable and worth sharing. The event has been covered widely so I won't even try to broadly summarize. Insted I will list what I found...
Dinesh's Cyberstation
Design of LINQ to SQL - What was I thinking or was I?
Posted
over 5 years ago
by
Dinesh Kulkarni - MSFT
11
Comments
A little break from my "LINQ to SQL tips" series of posts. A recent vote of no confidence on a related component orchestrated by community activists reminded me of many questions I have fielded and how the design team approached the design of LINQ to...
Dinesh's Cyberstation
LINQ to SQL Tips 8: How to (and why) create a partial class in the designer to augment generated code
Posted
over 5 years ago
by
Dinesh Kulkarni - MSFT
5
Comments
The code generated for LINQ to SQL is a set of partial classes - one for your DataContext and one per entity mapped to a table or a view. That means you have the opportunity to augment the generated code with additional code in your partial class. I often...
Dinesh's Cyberstation
LINQ to SQL Tips 7: Minimal update when you don't want optimistic concurrency check
Posted
over 5 years ago
by
Dinesh Kulkarni - MSFT
2
Comments
The common guidance for updates is to keep the original values in view state so that you can recreate the object in its original state, Attach() it and then set the values that the user has modified. This works well for the most part. But at times, a...
Page 1 of 1 (4 items)