When using LINQ to SQL, it can be very useful to see the SQL commands that are generated by your LINQ expressions. Sometimes the results are surprising and you might be able to improve performance by tweaking the LINQ.All you have to do is set the Log property of the DataContext object. ...
When using LINQ to SQL, it can be very useful to see the SQL commands that are generated by your LINQ expressions. Sometimes the results are surprising and you might be able to improve performance by tweaking the LINQ.
All you have to do is set the
This will cause the SQL commands generated by MyDataContext to appear in the output window in the debugger. You probably shouldn't leave this in your code without at least wrapping a
All you have to do is set the
Log property of the DataContext object. For example.MyDataContext.Log = Console.Out;
This will cause the SQL commands generated by MyDataContext to appear in the output window in the debugger. You probably shouldn't leave this in your code without at least wrapping a
#if DEBUGaround it.
No comments:
Post a Comment