Windsor PerWebRequest resolution in Application_Start

Question

I am injecting HttpContextBase into a caching class. HttpContextBase is registered as PerWebRequest. I interact with the caching class on each web request and this works fine, but I also need to initialise the cache at application start.

I understand that PerWebRequest does not work in Application_Start though:

castle PerRequestLifestyle not recognize

What is the best way to resolve this in my situation?

Krzysztof Kozmic · Accepted Answer · 2010-06-11T14:17:49.573

4

Not use stuff that depends on per-web-request stuff outside of web request.

If you need to depend on a class you registered as PWR I'd suggest getting another component for that service with different lifestyle and using it in Application_Start and using IHandlerSelector to return PWR one when you're within a web request, and the other one otherwise

edited Jun 11 '10 at 14:17

answered Jun 11 '10 at 13:39

Krzysztof Kozmic

27,267
12
73
115

it is not unreasonable to want to pre-populate a cache on application start, so what options do I have if I want to use Windsor to resolve the caching class which depends on HttpContextBase? – Paul Hiles Jun 11 '10 at 13:46
How can you use HttpContextBase outside of web request? – Krzysztof Kozmic Jun 11 '10 at 13:48
You still have an HttpContext in the Application_Start event – Paul Hiles Jun 11 '10 at 13:53
Updated the answer with _workaround_. I'd still try to restructure your code not to rely on something you chose to bind to web requests outside of web requests. – Krzysztof Kozmic Jun 11 '10 at 14:18
+1 Krzysztof's workaround is correct. Use a transient for Application_Start() – Mauricio Scheffer Jun 11 '10 at 15:29

score 4 · Answer 2 · answered Jun 25 '10 at 19:43

4

Try using an hybrid webrequest/transient lifestyle.

answered Jun 25 '10 at 19:43

Mauricio Scheffer

98,863
23
192
275

althought I still say - refactor should be your first option – Krzysztof Kozmic Jun 25 '10 at 21:45
@mauricio-scheffer I'm a bit confused, let's say I register IDBcontext with hybrid webrequest in my applicaiton_start, now when the app starts there is no httpcontext, so it will be registered as tansient. So how will IDBcontext ever be registered as perrequest lifestyle? – Saber Nov 09 '15 at 08:55
@Arvand if there is a HttpContext the container will try to resolve it from the context. Otherwise it will create a fresh instance. – Mauricio Scheffer Nov 09 '15 at 14:10

score 0 · Answer 3 · answered Jun 11 '10 at 23:22

0

To warmup caches when the container starts I usually use the Startable Facility. Here is an example on how to use it: http://blog.bittercoder.com/PermaLink,guid,a621ddda-acb5-4afd-84ff-faafb96a2fa1.aspx

answered Jun 11 '10 at 23:22

John Simons

4,288
23
41

it will still eagerly instantiate the service – Krzysztof Kozmic Jun 12 '10 at 04:03

Windsor PerWebRequest resolution in Application_Start

3 Answers3