myDataContext.DeferredLoadingEnabled = false;
True by default? Yuk.
I suggest a name change to
myDataContext.DataLoadOptionsEnabled = true;
Or why not remove the property alltogether? if I set the property myDataContext.LoadOptions (that should be named .DataLoadOptions) isn't it clear that I want eager loading?
Or am I missing something?
- Michael Starberg
Interesting question - seems a bit redundant with the property, unless it's linked to other features than the LoadOptions.
Another thing I find strange is the casing in the DBML XML schema. Most XML configuration files from Managed Microsoft API (including the entire .NET framework configurations) uses camelCasing where as the DBML XML schema in LINQ to SQL uses PascalCasing (who decides when to use which schema - was Don Box on vacation when you decided on the schema? ).
I'd really like to see Microsoft standardize on casing when it comes to XML configuration files. Please bring the DBML XML schema inline with the rest of the .NET framework. That is, unless the rest of the configuration files are sharing casing by coincidence.
Current (PascalCasing):
<Database>
<Table Name="" AccessModifier="" />
</Database>
.NET Framework (camelCasing):
<database>
<table name="" accessModifier="" />
<database>
It's not RTM yet; You can still make it!
