Sharp architecture problem?

This has been fixed in the 1.9.6 release, but you need to register the default implementation of ISessionFactoryKeyProvider in the Windsor container.

This has been fixed in the 1.9.6 release, but you need to register the default implementation of ISessionFactoryKeyProvider in the Windsor container. In ComponentRegistrar. Cs in the CastleWindsor folder of the "Web" project add this code to the AddGenericRepositoriesTo method: container.

Register( Component . For(typeof(ISessionFactoryKeyProvider)) . ImplementedBy(typeof(DefaultSessionFactoryKeyProvider)) .

Named("sessionFactoryKeyProvider")).

Thanks I saw a similar post somewhere else. Everything is already there. Please note that I use things in a console app which used to work fine.

I don't think this stuff will ever be invoked ... – csetzkorn Feb 25 at 16:26 This was a change introduced in 1.9.5, DefaultSessionFactoryKeyProvider now needs to be registered in the Windsor container for it to work. You ought to be doing this anyway for other components e.g. IEntityDuplicateChecker, IValidator. – ChrisR Feb 25 at 16:43 1 In a console app you will have to explicity call ComponentRegistrar.

AddComponentsTo and pass in a Windsor container, you should also initialise the ServiceLocator with: ServiceLocator. SetLocatorProvider(() => new WindsorServiceLocator(container)); In a web app this is done in MvcApplication. Application_Start in Global.asax.

Cs, but you will have to add it to the start up code of your console app. – ChrisR Feb 25 at 16:58.

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.