I have the WindsorControllerFactory already running without any problems in .Net 3.5 Since I wanted to try Entity Framework 4.0 I upgraded to .Net 4.0 But I still have some helper Methods (e.g. RenderAction from the MVC Futures), which are still .Net 2.0. As soon as I use any of those "old" methods, the ControllerFactory registration doesn't work any more. Maybe I just try to get those helper methods upgraded to .Net 4.0, too, and see it that works.
On Jul 18, 3:31 pm, Tuna Toksoz <[email protected]> wrote: > You can simply implement IControllerFactory or IControllerBuilder, whatever > the name is. > And call thing like > > ControllerBuilder.Current.SetCurrentFactory etc > > and you'll be okay. > > Tuna Toksöz > Eternal sunshine of the open source mind. > > http://devlicio.us/blogs/tuna_toksozhttp://tunatoksoz.comhttp://twitter.com/tehlike > > On Sat, Jul 18, 2009 at 3:16 PM, Jason Meckley <[email protected]>wrote: > > > > > I haven't worked with MS MVC, but I know you need to create a custom > > Controller Factory and register this with the MVC framework. your > > custom controller would resolve the controller from Windsor. > > > MvcContrib, by HeadSprings, has this factory (and other extensions) as > > part of the package. > > > On Jul 18, 7:33 am, "Henrik Feldt" <[email protected]> wrote: > > > Without testing 4.0 with Windsor, my way of trying to debug this would be > > to > > > get a trace where you see how the logic has gone when selecting the > > > controller factory in MSMVC. If you are calling CLR 2.0 methods, then for > > > some reason the Windsor controller factory doesn't get called; you need > > to > > > find out why. See if you can give a stacktrace as well as a more detailed > > > description as that helps. > > > > -----Original Message----- > > > From: [email protected] > > > > [mailto:[email protected]] On Behalf Of Name > > > Sent: den 17 juli 2009 16:59 > > > To: Castle Project Users > > > Subject: Castle Registration for different frameworks > > > > Hi, > > > > I'm pretty new to Castle Windsor and want to use it for asp.net mvc. > > > I'm using the latest .net 4.0 Framework and Visual Studio 2010. > > > Castle has to be registered as a HttpModule in web.config and jumps in > > > whenever you instantiate a controller with an interface constructor. > > > Everything works fine, until I start mixing up .net Frameworks. > > > Whenever I call a Framework 2.0 Method which needs to instantiate a > > > controller, Castle Windsor seems not to be involved anymore. Of course > > > I get an error, since there is no object injected. > > > "No parameterless constructor defined for this object". > > > Does anyone know if Castle Windsor that can be configured somehow to > > > jump in for different frameworks? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
