>The real gain would be in using static constructors to initialize the Framework. It would certainly help with handling the global level properties - static constructors would, as Rick says, only run once (the very first time the framework is instantiated) - subseguent instantiations would have those properties already set - and that might reduce the initialization overhead enough to make using new Framework objects on each page hit acceptable ?

Using what I have now, by creating a new application object at every hit, would static be useful for me? Because, I am executing Initialize() at every hit now.