On your second question, changes will not get picked up automatically because the Container.Component.config is not monitored for updates - so regardless of the lifestyle configured, it will be necessary to restart the app to get changes picked up. I did
think there was a way to get Windsor to monitor the external config file automagically and to reinitialise the container when changes are made, but a quick Google didn't get me very far - and I have no idea how this would play with the fluent registration
we use for the majority of the components.
This is what I suspected as well.
However, it seems as if I spoke too soon.
I re-looked at this, and it turns out that, at least in my current config, I am able to get the settings in Container.Component.config recognized by doing the following:
1) Change a value in Container.Component.config as desired
2) Touch web.config using the old trick: modify something harmless and save it, then modify it back, and save it again
By doing this, the changes I made to Container.Component.config are reflected in the next web request, without having to restart the IIS app.