Thanks for the great for Jerry.

BTW, I am happy that you will write again about your old topics. I wonder the changes in your ideas over years. Or ideas becoming experiences…

Sorry to read about the reasons you stopped blogging first time round. Life is too short for the ranting and getting upset with people, let alone at those you may or may not know or respect.

Welcome back.

Jerry was my grandfather’s name, but I’ll be happy to answer here:

1.) You *could* go run thru the IContainer.Model structure and figure out what has been created as an IDisposable transient during the nested container. Not really something I anticipated here.
2.) For().Use() is destructive. Do For().Use() once to get the default, and a second call to For().Add() to get the 2nd registration. Look at the Xml comments for those 2 API calls.

Maybe you could address these issues? Thanks for your great work.

http://stackoverflow.com/questions/8710006/log-structuremap-nested-container-disposing
http://stackoverflow.com/questions/7501207/structuremap-odd-behavior-when-using-default-instance-and-named-instance-option

Looking forward to hearing and learning more

I don’t want to ramble on here so i’ll sum up with a simple “thank you” for everything that you do. You have a profound impact on scores of developers even if don’t always see it. We are anxiously looking forward to your future writings. Thanks for jumping back in – we missed you!

Scan(cfg =>
{
cfg.Assembly(dal);
cfg.LookForRegistries();
});

whereas this works:

Scan(cfg =>
{
cfg.Assembly(dal); cfg.AddAllTypesOf();
});

dal is const with assy name. No need to reply here if you’re going to do a blog as I have already cluttered your BIO page enough .

Let me get a blog post together for you by the end of the weekend.

“Should the Registry be in its own assembly that references both the interfaces assy and the concrete types assy?”

Yes, that’s one way to go about it. The Scan() business can be used (don’t have the code open, so the call might not be exactly right) like so:

Scan(x => {
// specify how you wanna suck in all the other assemblies
x.LookForRegistries(); // this will make it use any Registry classes it finds in the other assemblies

});

No xml necessary.

Thanks for StructureMap. It is a great product.

I have been using it for some time very succesfully with a config file where the pluginTypes and pluggedTypes are nicely organized. Of course, the assemblies that contain the concrete types are NOT referenced in the calling assembly.

I am trying to use the concept of Registry DSL instead but there is something that I don’t seem to comprehend when using the For.Use(). In order for this to work, the concrete types MUST be in a referenced assembly but …. this really kills the purpose of IoC as far as I am concerned because the calling assemlby should NOT have any knowledge of the concrete assy, just the interfaces.

I tried to use the Scan with Assembly and AddAllTypesOf. This resolve my problem but it does not allow passing any constructor parms like the For.Use does and so I cannot pursue this avenue.

Am I missing the obvious? Should the Registry be in its own assembly that references both the interfaces assy and the concrete types assy?

Thanks, Yves