Rhino Commons UnitOfWork and ASP.NET MVC Controller seem to be caching parameters?

My guess is that the whole UnitOfWork thing is a red herring... The controller being passed values from previous requests sounds like the same instance of the controller is being re-used for multiple requests. The ASP. NET MVC framework works under the assumption that each request is handled by a fresh instance of the controller.

My guess is that the whole UnitOfWork thing is a red herring... The controller being passed values from previous requests sounds like the same instance of the controller is being re-used for multiple requests. The ASP. NET MVC framework works under the assumption that each request is handled by a fresh instance of the controller.So, with that in mind, how are you constructing your controllers?

For example if you're using a IoC framework like Spring. NET make sure your controllers are not singletons.

I was using some sample code with Castle Windsor. Modifying the method to create the controllers fixed it. Thanks for pointing me in the right direction.

– rjester Jul 24 '09 at 12:52.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.