.NET IoC Roundup including some mis-information about Structuremap?

[Steven Harman]

I just stumbled across a roundup-style comparison of various .NET IoC Containers and I think there are a few incorrect statements made about the capabilities of Structuremap. Specifically I think the roundup is missing out on the power offered by the new convention/type scanner, auto-registration, etc... However, I've been out of the loop for a few months so I'm probably not the best source of accurate info.

http://blog.ashmind.com/index.php/2008/09/08/comparing-net-di-ioc-frameworks-part-2/

Anyone (ahem... chad) else care to take a look and offer proper advise/info to the author?

-steve

//---- 90% of being smart is knowing what you're dumb at ----//
http://stevenharman.net/

[Jeremy Miller]

My reply:

http://codebetter.com/blogs/jeremy.miller/archive/2008/09/10/using-the-structuremap-container-independently-of-objectfactory.aspx

On Sep 10, 8:41 am, "Steven Harman" <stevehar...@gmail.com> wrote:
> I just stumbled across a roundup-style comparison of various .NET IoC
> Containers and I think there are a few incorrect statements made about the
> capabilities of Structuremap. Specifically I think the roundup is missing
> out on the power offered by the new convention/type scanner,
> auto-registration, etc... However, I've been out of the loop for a few
> months so I'm probably not the best source of accurate info.
>

> http://blog.ashmind.com/index.php/2008/09/08/comparing-net-di-ioc-fra...