Performance.Web - Share common parts of the application model to reduce startup time and memory use

Currently, as a workaround, you can use this approach:

C#
protected void Session_Start(Object sender, EventArgs e) {  
            lock (this) {  
                if (parameters == null) {  
                    DictionaryNode.ReaderWriterLockWrapperCreator = new ReaderWriterLockWrapper();  
                    XafApplication dummyApplication = new MainDemoWebApplication();  
                    dummyApplication.SettingUp += new EventHandler<SetupEventArgs>(dummyApplication_SettingUp);  
                    dummyApplication.Setup();  
                }  
                MainDemoWebApplication application = new MainDemoWebApplication();  
                if (application.Security != null) {  
                    SecuritySystem.SetInstance(application.Security);  
                }  
                WebApplication.SetInstance(Session, application);  
                application.MySetup(parameters);  
            }  
            if (ConfigurationManager.ConnectionStrings["ConnectionString"] != null) {  
                WebApplication.Instance.ConnectionString = ConfigurationManager.ConnectionStrings["ConnectionString"].ConnectionString;  
            }  
            WebApplication.Instance.Start();  
        }  
        ExpressApplicationSetupParameters parameters;  
        void dummyApplication_SettingUp(object sender, SetupEventArgs e) {  
            parameters = e.SetupParameters;  
        }  

Feel free to contact us in case of any difficulty.
Thanks,
Dan

Please check out the complete Code Central example showing a workaround here: OBSOLETE - How to improve the XAF ASP.NET application performance (startup and memory use)..
See Also:
Performance - Public results of benchmark tests of XAF Win and Web applications
Thanks,
Dennis

The improvement described in this suggestion was implemented during the application model improvements done in the v2010 vol 1 release. Starting with this version, common parts of the application model are setup only once for the global HttpApplication.
Thanks,
Dennis