StructureMap 2.5 will be released on June 23rd

Several people have asked, and I’m getting anxious to get it out.  I’ve got just a couple little coding tasks to do, then about a week of writing docs, examples, and tutorial thingies.  I originally planned to make this release in .Net 2.0, but I gave in and switched the code over to .Net 3.5. 

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 Uncategorized. Bookmark the permalink. Follow any comments here with the RSS feed for this post.
  • Patrick

    Hi Jeremy
    As happens often in Corporate scenario it is difficult to migrate your codebase suddenly. In our case we will have to continue using .net 2.0 and 3.0. I wished I could use Structuremap 2.5.3 but bit dissapointed now.

  • http://codebetter.com/blogs/jeremy.miller Jeremy D. Miller

    @Erik,

    Yes and no. I’m going to put up a zip file of the Release Candidate binaries at lunch time. I’m lagging on the documentation for the full release, but I’m declaring Code Complete.

  • Erik

    Hmmmm,
    So I guess June 23rd doesn’t mean Monday June 23 at 12:01 a.m.?

    Things Still On track for today?

    Thanks for all your hard work,

    Erik

  • http://http:blogs.lessthandot.com Christiaan Baes

    Even us VB.Net guys are looking forward to it.

    Perhaps I need to switch to C# one of these years… nah.

    And thanks for all the effort you put in.

  • http://codebetter.com/blogs/jeremy.miller Jeremy D. Miller

    @Gabriel,

    Good point, but I would like to use expression trees for some of the configuration Fluent Interface.

  • http://www.enesyssoftware.com Frédéric Latour

    Well, even LINQ to Object can be used when targetting .net 2.0 by using LinqBridge…

  • Gabriel Schenker

    You know that lambdas are only a compiler feature and do not product .NET 3.5 specific MSIL! The only thing you cannot use when targetting .NET 2.0 (from VS 2008) are LINQ and expression trees…

  • http://codebetter.com/blogs/jeremy.miller Jeremy D. Miller

    @alberto,

    Yes I do know that, but that misses the point. I do think that the language features in C# 3 are compelling.

  • http://sharpbites.blogspot.com alberto

    You know you can target .net 2.0 with VS2008, right?

  • http://www.heliosfx.com Travis

    @Jeremy

    Where is the appropriate place to ask questions about SM? I have some implementation questions.

  • http://codebetter.com/blogs/jeremy.miller Jeremy D. Miller

    @Mike,

    One word: Conciseness

    I counted about 30 comments in the code like this:

    // TODO: Make this cleaner with 3.5
    // TODO: Use an extension method here with 3.5
    // TODO: This will be cleaner with 3.5 lambdas

    I’m using a *lot* of anonymous delegates and poor man’s Functional Programming. C# 3.0 is just flat out better. I found some places where a judicious usage of an extension method could take away a big chunk of duplicated code. The better type inference reduces noise as well.

    Of course, the real reason is that my personal notebook computer is sick at the moment, and I only had VS2008 on my work computer and I was too lazy to install VS2005.

  • http://blowmage.com/ Mike Moore

    Why did you switch to .Net 3.5? What benefits did you get for making the switch?

    Does using StructureMap 2.5 require you use it from .Net 3.5? Or can you use it from .Net 2.0 as well?

  • http://devlicio.us/blogs/derik_whittaker/default.aspx Derik Whittaker

    Rock on… Looking forward to this new release.

    SM is still my IoC container of choice.