which method is best? The current control instantiation in the default.aspx code behind doesn't work with external assemblies. To support this, I had to add a column for the assembly name - So two issues: 1. performance - what are the options for instantiation,
there's alot of them Caching should be discussed 2. Flexibility - what is the most flexible method without hurting performance?
You two issues are pretty much null and void, because as soon as you use the assembly for the first time it is cached the same way that a web page is cached. So there really is no need to talk about performance, and flexiblity is provided with out limiting
the assemblies by trying to over define them. Just look for the assemblies automatically at the begining of application load and then grab all the instance of the type that you need out of the assemblies.
None
0 Points
1418 Posts
[1.2] Control Instantiation
Apr 11, 2004 01:14 PM|Sedgewick|LINK
Participant
792 Points
2233 Posts
Re: [1.2] Control Instantiation
Apr 11, 2004 09:45 PM|nberardi|LINK
Participant
792 Points
2233 Posts
Re: [1.2] Control Instantiation
Apr 11, 2004 09:52 PM|nberardi|LINK