tag:blogger.com,1999:blog-35403832.post3703438181457559430..comments2010-12-12T14:23:16.197+01:00Marnixhttp://www.blogger.com/profile/00913090261390882195noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-35403832.post-67101830567122122402010-12-12T14:23:16.197+01:002010-12-12T14:23:16.197+01:00@dbones Yes, you&#39;re missing the point. PWR works ok, but breaks when used <em>during</em> initialization or when running outside a web context, for example in unit tests.<br />This means that it&#39;s not possible to use components with PWR-lifestyle to initialize the application before the first request is handled.<br />Note that I have successfully deployed several applications using the fix I described in my previous post on this topic (i.e. with a hybrid lifestyle that falls back to transient for scenarios where PWR doesn&#39;t work)Marnixhttp://www.blogger.com/profile/00913090261390882195noreply@blogger.comtag:blogger.com,1999:blog-35403832.post-57760918649546887232010-12-12T04:19:49.399+01:002010-12-12T04:19:49.399+01:00(have you fixed this? as it looks like you did not do another follow up post)<br /><br />I have PWR working in my MVC2 app.<br /><br />1. Add the required in the web.config<br />2. in the App start, create then call a function to register all the components, trans, Singleton and PWR<br /><br />done, it will now inject the dependences<br /><br />I think I may be missing the point.<br /><br />ps, for IIS7 you have to register it twice http://stackoverflow.com/questions/258011/problem-with-windsor-castle-with-iis7dboneshttp://www.dbones.co.uknoreply@blogger.com