Jon,
I think he means the Table<T- on the RDBMS there wouldn't be
anything triggering assemblies being loaded etc (typically, anyway).
But yes, some more clarity would be nice :)
I'm sorry I was not clear.
Table<Tobject instantion causes assembly containing type T to be loaded.
So my issue is: is it possible and reasonable to change sqlmetal generated
code
so that it does not create tables in Data Context constructor?
Is it possible and reasonable to move table creation to table property
getter by implementing getter like
public readonly MTable<CustomerCustomers {
get { if ( customers=null )
customers = new MTable<Customer>(this);
return customers;
}
Will Linq-SQL work well in this case in design and run times ?
Or will only reference to Table<Tin assembly cause assembly containing
type T to be loaded ?
If so I think I will create whole extended properties assembly at runtime
and load it fully. If this causes perfomace decrease I hope I can cache this
extented assembly in isolated storage.
I havent seen any .NET application with uses background assembly loading at
startup like windows logon.
Andrus.