Prism is a composite application framework created by Microsoft P&P.

There is a sample integration here: http://autofac.googlegroups.com/web/prizm.zip_.

Please add your vote if you'd like to see this added to Autofac Contrib.

Create an end-to-end walkthrough showing how to set up Autofac with Windows Forms (WinForms). Include a sample application.

Add a build configuration for .NET CF.

Create an end-to-end walkthrough showing how to set up Autofac with Windows Presentation Foundation (WPF). Include a sample application.

The documentation is good, although I still find I run into problems.

a) I can't find what I'm looking for,
b) I find what I'm looking for but the examples aren't clear enough to understand.

Better use cases, or examples of what people are more likely to do. And also structured documentation rather than the flat wiki that currently exists.

Most Autofac applications use code to register services, and where necessary register only Modules via XML.

Some users have expressed interest in adding more fine-grained component registration to the XML sytax:

Examples:

* Constructor selection policy
* Tags
* Factory Methods
* Open generic types
* Resolve named services as constructor parameters

Create an end-to-end walkthrough showing how to set up Autofac with ASP.NET MVC. Include a sample application (can be based on the Remember example in the Autofac source tree.)

Entlib 5 can be configured to use a third-party IoC container (other than Unity.)

Please add your vote if you'd like to see an adapter added to Autofac Contrib.

Dynamic instantiation, and parameterisation is supported via func's, it would be very use if it was also supported via FSharpFunc's

Create an end-to-end walkthrough showing how to set up Autofac with ASP.NET WebForms. Include a sample application.

Currently it has the IScope but internally it uses the enum which restricts to create custom scope such as PerWebRequest. The current recommended way to create a child container is very similar to Unity but not like other container.

Support resolving open generics by the most specific constraint. For example:

class MyService<T> { }
class MyFooService<T> : MyService<T> where T : IFoo { }

b.Register<MyService<>>();
b.Register<MyFooService<>>().As<MyService<>>()

c.Resolve<MyService<object>>() // gets a MyService
c.Resolve<MyService<FooImplementor>>() // gets a MyFooService

Support Export(typeof(IModule)) in Builder implementation. Perhaps add the support of named IModule types through the use of an attribute to filter the modules at load time.

Maybe this is already supported, so maybe a walkthrough/wiki about how to inject dynamic components

This would aid in the goal of Zero Intrusion (Components don't need to reference Autofac). It would allow components to be descriptive about their relationships without needing to reference the Autofac assembly.

I typically use a fair amount of interfaces to make testing/stubbing easier.

One slight pain I have with Autofac is registering a type .As() an interface it implements. Not a huge pain, but it would be nice to be able to write it much more cleanly.

At current I use reflection to do this. It would be nice instead if RegisterTypesFromAssembly() or RegisterTypesMatching() could be extended to do this. Something like:

RegisterTypesAssignableFrom(ICommand).AsInterface()

where AsInterface works out the interface the type implements directly. Bit messy but you get the idea.

I would like to be able to register "internal" components which only can be accessed from within the same assembly as the requested type.

It's quite easy to implement. Simply call Assembly.GetCallingAssembly() when a component flagged with "Internal" are requested.