Re: Table bloat in Linq-SQL

Tech-Archive recommends: Fix windows errors by optimizing your registry

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<T> object 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<Customer> Customers {
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<T> in 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.


.

Relevant Pages

  • Customizing localized applications
    ... says I should use ResourceManager and satellite assemblies. ... So there is no way to change resources except ... I don't want to distribute code to customers. ... check) included in SDK. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Lead times
    ... This happens in every company I deal with, customers order back-to-back and ... shipping the agreed amount each month. ... assemblies, or firmware programming. ... >> are about a million and one reasons why you have slow lead times. ...
    (comp.arch.embedded)
  • Re: Application security
    ... > - to prevent user from using my dlls directly, ... Assigning strong names to your assemblies is ... The ones you want to protect or the ones from which you want to ... > - I want to manage demo and customers version with license key policy. ...
    (microsoft.public.dotnet.security)
  • Re: Assembly could not be installed because existing policy would keep it from being used
    ... Our product allows customers to build custom applications using the ... against version 1 onto the new version 2 assemblies. ... It was these rebind policy assemblies ... we deleted the policies from the GAC and the problem disappeared. ...
    (microsoft.public.sqlserver.security)
  • Re: Assembly could not be installed because existing policy would keep it from being used
    ... Our product allows customers to build custom applications using the ... version 1 onto the new version 2 assemblies. ... It was these rebind policy assemblies ... we deleted the policies from the GAC and the problem disappeared. ...
    (microsoft.public.sqlserver.security)