Let’s try this again, StructureMap 3.0 in en route as of now
I’ll be honest, I haven’t worked much on StructureMap since I originally shelved my original 3.0/rewrite work in the summer of 2010 — and yes, the documentation is almost worthless. Now that FubuMVC reached that magic 1.0 mark I’m turning my attention back to StructureMap for a bit, but I think I want some feedback about what I’m thinking right now.
For background, read:
- Kicking off StructureMap 3.0 – I just re-read this, and I’m still thinking all of the same things here and all the feedback is still valid.
- Proposed StructureMap 2.7 Release
A month ago my plan was to do a small 2.7 release on the existing codebase to remove all the [Obsolete] API calls and grab some pull requests along the way. Having done that, I would then turn my attention back to the 3.0 codebase where I planned to essentially rewrite the core of StructureMap and retrofit the existing API on top of the new, cleaner core. A week or so into the work for the 2.7 release and I’ve changed my mind. First off, by the rules of semantic versioning, I should bump the major version to 3.0.0 when I make the breaking API changes. Secondly, I’m coming around to the idea of restructuring the existing code in place instead of a full rewrite.
To reiterate the major points, the 3.0 release means:
- All [Obsolete] API calls are going away
- Removing the strong naming — if you absolutely *have* to have this, maybe we can make separate nuget packages. I suggest we name that “structuremap.masochistic.”
- Move to .Net 4.0. I don’t think it’s time to go to 4.5 yet and I don’t really want to mess with that anyway
- Taking a dependency on FubuCore — if that causes pushback we’ll ilmerge it
- Streamlining the Xml support
- Rewrite the “Profile” feature completely
- Make nested containers not be a crime against computer science
- NOT adding every random brainfart “feature” that Windsor has
- Make it faster
- Make the diagnostics much better
- Removing some obscure, clumsy features I never use and really wish you wouldn’t either
Additionally, we have a new “living documentation” infrastructure baking for the Fubu projects. I know some work already happened to transfer the StructureMap docs to Jekyll, but I’d far prefer to publish on the new fubu world website whenever that happens.
For right now, the 3.0 branch is in the original StructureMap repository at https://github.com/structuremap/structuremap/tree/three.