Comments on Alanta Developer Notes: Castle: PerWebRequestLifeStyle won’t work from App...

Looks good Mauricio. Especially since it also has ...

2011-01-27T09:58:11.075+01:00

Looks good Mauricio. Especially since it also has the contextual life style you commented about on my Stack Overflow question a while back.

A while ago I created a contrib project with several lifestyles not included in stock Windsor (hybrid transient-web included).

As far as I know the position of the Castle team i...

2010-09-18T14:54:15.816+02:00

As far as I know the position of the Castle team is that the behavior of the PerWebRequest lifestyle is by design. They are not planning to fix or change it.

Anything new about this issue? I'm using Castl...

2010-09-17T17:36:41.034+02:00

Anything new about this issue? I'm using Castle 2.5 and in my project your solution doesn't solve my problem (I can access the container but not the registered components).

Hi Bhoomi, I've updated the demo code to make...

2010-01-07T10:04:51.534+01:00

Hi Bhoomi,

I've updated the demo code to make it a bit simpler to use. Please download the code again and see if that works for your application.

2010-01-07T09:42:25.415+01:00

This comment has been removed by the author.

Hi Murki, Thanks for the code. Yes your code work...

2010-01-07T06:10:36.498+01:00

Hi Murki,

Thanks for the code. Yes your code works correctly.
I replicated your Web.Config file but still I am getting the same error that is :

Looks like you forgot to register the http module Castle.MicroKernel.Lifestyle.PerWebRequestLifestyleModule
Add '' to the section on your web.config

It comes from :
ServiceLocator.Current.GetInstance(commandHandler);

here commandHandler is a generic of type : ICommandHandler

Any ideas wht's wrong??

Thanks again..

Hi Bhoomi, I've created a basic demo applicat...

2010-01-06T10:09:18.593+01:00

Hi Bhoomi,

I've created a basic demo application that demonstrates my solution and added a link to the blog post.
Please try the application and let me know if this works for you.

Visual Studio 2008.

2010-01-03T18:17:44.825+01:00

Visual Studio 2008.

Hi Bhoomi, What version of Visual Studio are you ...

2010-01-03T16:37:51.722+01:00

Hi Bhoomi,

What version of Visual Studio are you using?

I am still having the same problem. Tried various ...

2009-12-31T11:54:41.887+01:00

I am still having the same problem. Tried various things. Implemented your code also. Tried out ploeh's way also. Nothing seems to work for me. I am using Castle.Windsor 2.0.0.0.
I am running my solution from VS Integrated environment.

Pl help.

Regarding getting PerWebRequest to work on IIS7, s...

2009-11-17T13:49:50.887+01:00

Regarding getting PerWebRequest to work on IIS7, see my blog post Using Castle Windsor's PerWebRequest lifestyle with ASP.NET MVC on IIS7.

Hi Mausch, Good point. I haven't had a chance...

2009-09-30T18:01:26.949+02:00

Hi Mausch,

Good point. I haven't had a chance to report the issue so I've gone and done it right away.

Thanks,
Marnix

Hi Marnix, did you try asking on the castle users ...

2009-09-30T17:20:50.406+02:00

Hi Marnix, did you try asking on the castle users group? If this is bug it should be fixed.

Hi Murki, I haven't read the book, but I thin...

2009-07-23T09:28:25.344+02:00

Hi Murki,

I haven't read the book, but I think I agree with the author.

For simple applications where you have a single point of interaction with the datacontext in each request, transient lifestyle would do just fine. When things get more complicated problems will start to appear. For example, I use a filter to inject the current user into controller methods:

ActionResult DoStuff( [CurrentUser] User current ){
myRepo.DoStuffWithUser( current );
}

The filter retrieves the current user object from the database. In the action method the current user is passed to a repository to do some operations on it.
If the datacontext has a transient lifestyle the filter and the repository used here would each have their own instance of the datacontext. Using an object retrieved by one datacontext to perform database operations in another will cause problems because datacontexts track their objects. The second datacontext does not 'own' the object retrieved by the first datacontext and will either throw an exception or try to insert it (again!).

PerWebRequest lifestyle will prevent these problems because both the filter and the repository would get the same instance of the datacontext.

Hi Marnix, Yeah, I'm basing some parts of my ...

2009-07-23T01:07:11.764+02:00

Hi Marnix,

Yeah, I'm basing some parts of my design on the suggestions of the book of "Pro ASP.NET MVC Framework" about using a PerWebRequest lifestyle in conjunction with Linq 2 Sql DataContext, but there the author contrast it against the default of "Singleton" which makes a lot of sense. Still I can't see how using a Transient lifestyle would make impossible to still use the DataContext, it would be an overkill maybe, but I don't think "impossible".

Hi Murki, A transient lifestyle would mean that e...

2009-07-15T18:16:41.348+02:00

Hi Murki,

A transient lifestyle would mean that every time you resolve a service a new instance is created. That may not be a problem in itself but needless creation of objects is a waste of server resources (mostly memory).
Also, I tend to use PerWebRequest lifestyle for things like a Linq DataContext. This ensures that every change to the database happens within the same context and all objects retrieved from the database are tracked by the same datacontext.
This would be impossible with a transient lifestyle.

Hey! Thanks for your great post, you're the on...

2009-07-15T17:30:35.432+02:00

Hey! Thanks for your great post, you're the only person I've seen addressing this problem, even though I have taken a different approach, do you know what would be the implications of using a Transient lifestyle instead of a PerWebRequest?