How embarrasing. I spelled my name wrong :-)
Anyway,
I am just referring to some of the things the Controller does to prepare the view. With a View represented as code, it may be simpler and more efficient to just create and manage stuff. In this case, I am talking about the Controller interating over all the Helper descriptors and calling
Activator.CreateInstance and adding them to a Dictionary. The Page would now have to index the dictionary by helper name and caste it to the appropriate helper. It seems simple enough for the Page to just do the new. In some cases, it may just be a static helper method.
craig
On 6/13/06, Ayende Rahien <[EMAIL PROTECTED]> wrote:
I am afraid that I don't follow you.
What overhead is there with creating the helpers?
On 6/13/06, Craig Neuwirt < [EMAIL PROTECTED]> wrote:Since ASP.NET Views are backed by code, do you think it woudl be a valid approach to instantiate and use Helper objects directly in the Page.Since there is so much extra overhead with ASP.NET Page Lifecycle, it might be nice to minimze additional overhead in creating the helpersdynamically.craug_______________________________________________
CastleProject-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/castleproject-users
_______________________________________________
CastleProject-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/castleproject-users
_______________________________________________ CastleProject-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/castleproject-users
