We have implemented the new(?) LifeStyleScope. We begin a new scope for each new dialog/window to enable e.g. an optimale use of unit of works. It works well, but I had a lot of trouble to enable using factories (for our view models). Reason: because the components are created lazily within a factory, Windsor cannot select the correct instance. What we have done is to also make the factory's lifestyle scoped and pass all scoped components to it right after creation. The factory then passes those cached components as anonymous types during creation. That works for most scenarios.

What I am missing and what would best resolve that use case would be an overload of Resolve, like: ResolveInScope<IFoo>(IDisposable scope [, object args]). This way I could define the scope in which the type and its dependencies have to be resolved.

Is this possible or does it break some meaning I don't have in mind?

Many-to-one relationships are not correctly implemented, and the description on http://www.castleproject.org/activerecord/gettingstarted/relations.html is wrong.
"Belongs to" and "Has many" both express a one-to-many relationship, and in fact are complimentary attributes.

A "many to one" relationship consists of foreign keys in table A which reference ONE record in table B, but a record in table B may be referenced by MANY records in table A, hence "many to one". Just to clarify, table A is on the left, and many A records can reference one B record.

As an example, consider some database that holds people records, automobile records, and the trips they take. A given automobile can be driven by any legal driver, but for a specific trip only one person drives. Therefore, a trip record has one vehicle, and one driver. However, a vehicle might make more than one trip, and a given driver might also make more than one trip. So each trip record has two many-to-one relationships:
The trips table --> vehicles table, and the trips table --> people table.

This data arrangement cannot be expressed using "belongs to" terminology because a given vehicle does not "belong to" a trip - having a trip ID column on the vehicles table would not be semantically correct. Any case where "belongs to" applies is a "one-to-many" relationship, since the right-hand table references directly a single record on the left-hand side.

I downloaded ActiveRecord 2 and the BlogSample. After two hours I got it to compile... Incorect References, "CountAll" not defined and otehr erros. Then after two more hours I got it finally load a config file without gaking. Then I get an erro about a proxy factopry not initilized. After two more ohours trying to sort that out I gave up and posted here. The first place I could find. But then I don;t expect an swers here so I'm to find a user support forums.

My First look at Castle/Active record wasn;t impressive. I'm still keen since it looks like very useful project I just with the documentation was up to date and in sync with the lates download version... Or even if I could just down load the older version.. but I don't know what version of ActiveRecord/NHibernate are the writer ones for the smaple.

Sorry for ranting but after 6 hours...

Argggggghhhhhh