I just uploaded a new incremental release of StructureMap with a bunch of bugfixes and a few new features.  Download it here.

From the release notes:

* Fixed issue with With<T>(object).GetInstance<U>() functionality.  This is now much more robust.
* Bug fix for Hybrid scoping
* TryGetInstance() and TryGetNamedInstance(). 
* Ignore setter emitting for indexer properties -- fixed a bug reported on the forum
* Multithreading lock problem fixed by Josh
* Patch for session lifetime.  There is now an option for "CacheBy(InstanceScope.HttpSession)"
* Fixed Public IDictionary setter injection in xml : http://groups.google.com/group/structuremap-users/browse_thread/thread/21265544d73cd395?hl=en
* Pete Johnson's fix for ObjectFactory.Configure() setting policy.  You can now set the scoping/lifecycle of a PluginType from Configure()
* EjectAllInstances<T>() clears out Singleton objects now (and calls Dispose() if appropriate)
* Josh has added an experimental debugger visualizer for StructureMap Container's

* The AutoMocker isn't as whiny about RhinoMocks versions.  There is also an AutoMocker strategy for Moq now as well 

* A minor performance enhancement that stops StructureMap from doing a scan of all types on the StructureMap assembly itself.

Please send all questions to the StructureMap Google list.

The Future

I'm hoping to complete the new StructureMap website and documentation over the holidays, and that's the next priority.  After that, I'd like to get a new 2.6 release out in the early quarter of '09.  Here's what I'm thinking about in no particular order:

1. A Silverlight ready version (i.e. a cutdown StructureMap)
2. Finish the Mono support.  It's very close, but I want to make sure
3. The *#%$ "BuildUp" functionality that allows you to do setter injection on an object that's created somewhere else.  Thank you ASP.Net.
4. Convention based setter injection (low hanging fruit)
5. A guarantee that StructureMap will function in partially trusted environments, or at least real guidance on what it can and cannot do
6. "Missing Instance" handlers
7. A "ConditionalInstance" that will give you easier ways to do conditional construction
8. Improved diagnostics.  The error output and the output from StructureMapDoctor and ObjectFactory.AssertConfigurationIsValid() could be a lot better

Now's a good time to ask for things.

Ok, that's it for me this year.  Merry Christmas and Happy Holidays, and I'll see you in January.