StructureMap vNext, StoryTeller Alpha 2, and a vacation

StructureMap 

Just a quick note, and to make myself a deadline, the next version of StructureMap will be dropping by the end of February.  This version is about fullblown Generics support, ease of use, and flexible configuration.  The new features are:

  • Full auto-wiring support for Generic template types with a caveat – IService<T> good.  IService<T, U> good.  IService<T,U,V> wacky exceptions.  I've got no answers on that one.
  • Bug fixes
  • Flexible configuration — move the configuration somewhere else, use multiple configuration files, pull from the .Net App.config, or something else altogether
  • Turn off configuration altogether and register dependencies programmatically with…
  • A Fluent Interface DSL API for programmatic "wiring" as an alternative to xml configuration or using attributes.  I hope it turns out to be useful, but if nothing else it's an excuse to play with Fluent Interface semantics on something nontrivial.
  • Flexible and more forgiving xml configuration.  I'm going to make the StructureMap.config file stop looking like a referential database.  There will be options to make the configuration more terse and require fewer repetitive data.  There will be a blog post later on applying the Don't Repeat Yourself principle to StructureMap in an attempt to make it easier to use

The Generics support is already in the Subversion trunk if you're so inclined.

StoryTeller

There's at least a couple shops that are doing some alpha testing on StoryTeller for me and I'm getting some useful feedback coming back.  Telerik has generously given us a license for their UI controls to be used for StoryTeller.  I've done quite a bit of work on the UI since Alpha #1.  As soon as I can get the UI prettier and eliminate some severe flickering I will make a second Alpha release some time in March.

 

 

Vacation 

I'm off this coming week, so you'll have to go somewhere else for unnecessarily long and opinionated blog posts.  I'm catching up on some long overdue family time on the family farm where the internet is still just a rumour;) 

About Jeremy Miller

Jeremy is the Chief Software Architect at Dovetail Software, the coolest ISV in Austin. Jeremy began his IT career writing "Shadow IT" applications to automate his engineering documentation, then wandered into software development because it looked like more fun. Jeremy is the author of the open source StructureMap tool for Dependency Injection with .Net, StoryTeller for supercharged acceptance testing in .Net, and one of the principal developers behind FubuMVC. Jeremy's thoughts on all things software can be found at The Shade Tree Developer at http://codebetter.com/jeremymiller.
This entry was posted in StoryTeller, StructureMap. Bookmark the permalink. Follow any comments here with the RSS feed for this post.
  • http://weblogs.asp.net/bsimser Bil Simser

    I’m wondering what your take is on the whole “commercial controls in open source apps”. I have the same dilemma with a couple of OSS projects I have. In one I want to use the DevExpress ribbon control (which I own) but don’t want to subject people who want to download the code to not be able to compile it because of the library. Even if I got a free copy from DevExpress (which I’m sure they might give me) it means I’m tied into something that might expire some day and then I’ve got to scramble to find a replacement (much like RSS Bandit did 3 times)

    I blogged about it here:
    http://weblogs.asp.net/bsimser/archive/2006/12/19/being-a-responsible-open-source-developer.aspx

    and here:
    http://weblogs.asp.net/bsimser/archive/2007/02/01/stuck-between-a-ribbon-and-a-hard-place.aspx

    As you mentioned you’re incorporating telerik’s controls in Story Teller, I assume you’re okay with it but just wondering if had gave it any thought or were concerned about the downstream implications?