Alistair Evans

Took a look at possible changes to the ContainerBuilder this morning. Two possible options as I see them; @tillig, would be good to get your opinion. 1. Define a list...

Took a look at this this morning; all was going well, until Modules came into play. Modules get their own `ContainerBuilder` built from the `IComponentRegistryBuilder`. If we want the Module's...

Might have to end up with a doc per-error; redirects don't seem to like anchor tags very much. If so, probably a section per exception type, then divided again by...

The approach to modifying the registration pipeline in a module, where you attach to the `PipelineBuilding` event, and add your middleware there, is the required approach to adding behaviour to...

I suspect this may be better addressed in the DynamicProxy issue (https://github.com/autofac/Autofac.Extras.DynamicProxy/issues/42), by exposing the middleware we have there more directly, to allow custom behaviour to add that middleware (with...

I've taken a look at our options here, and I'm going to split my thoughts into two. ## Modifying Pipelines in AttachToComponentRegistration If you want to add to the Resolve...

@xumix, your module code will get a little simpler, but not much. Fundamentally, the module you've got here is the right way to do things, all we've done is make...

Instead of using bit.ly links, could be not just create pages on autofac.org that redirect to places in our docs? Pretty trivial to do I believe with a custom Jekyll...

I've taken a look at options for the shortener. bit.ly will provide the functionality we need 'for free', including creating links with custom path content, e.g. http://bit.ly/autofac-scope-docs (link works). The...

According to the ReadTheDocs people, our docs are set up as a translation of a different set of docs, `autofaccn`? @tillig, do you know what that's about, I don't have...