Krzysztof,
Currently or ongoing? From a previous thread it sounded like there would be a build of Windsor without that reference in the future. From: [email protected] [mailto:[email protected]] On Behalf Of Krzysztof Kozmic Sent: Monday, May 24, 2010 3:57 PM To: [email protected] Subject: Re: Castle Windsor together with Composite WPF we're not building Windsor for ClientProfile, but for full .NET For example per-web-request lifestyle uses System.Web On 2010-05-24 21:53, Lundberg, Per wrote: Hi, It seems like the IContainerFacade interface isn't used in the most recent version (October 2009) of Prism. I looked a bit into updating the Castle Prism bootstrapper to work with the current release, but didn't finish it. One side note: I've started using Castle MicroKernel now in a .NET 4.0 application (with Visual Studio 2010). But, it complains about a reference to System.Web v4.0 which is not included in the .NET 4.0 "client profile", and rightly so (in my opinion). How come you (in Castle.MicroKernel and Castle.Core) are referring to that assembly? Best regards, Per From: [email protected] [mailto:[email protected]] On Behalf Of Krzysztof Kozmic Sent: den 23 maj 2010 11:16 To: [email protected] Subject: Re: Castle Windsor together with Composite WPF Per, I don't know about changes in Prism itself, but Windsor didn't change much between v2 and v2.1 so I'd expect the update to be quite straightforward... What exactly are you having issues with. krzysztof On 2010-05-22 23:21, Lundberg, Per wrote: Hi guys! I have looked a bit into trying the Composite WPF Contrib project, where Hadi Eskandari has written a Castle Windsor Adapter for the Composite WPF (a.k.a. Prism) framework. However, the CompositeWPFContrib.Composite.WindsorExtensions doesnt seem to work very well with the most recent (October 2009) release. There is no longer any IContainerFacade interface (or at least, this seems to be the case). Has anyone done any attempt to update this project to the most recent Composite WPF release? What I am trying to do is to replace the default Unity container in Composite WPF, and use the Castle Windsor/Microkernel container instead Shouldnt be impossibly, should it? If you have any links or hints whatsoever, please do tell. (Cc:s are appreciated, since I dont read the mailing list regularly) Best regards, Per Lundberg -- 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. -- 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. -- 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. -- 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. -- 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.
