StructureMap Exception after adding the WebApi.HelpPage to a webApi project

Question

I followed the instructions here to add the webApi.HelpPage area and views to an existing project, which uses structureMap - but when accessing the /Help url:

StructureMap Exception Code:  202 No Default Instance defined for PluginFamily System.Web.Http.HttpRouteCollection, System.Web.Http, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35

So I'm missing something on the structureMap configure:

ObjectFactory.Configure(x => x.Scan(scan =>
            {
                scan.TheCallingAssembly();
                scan.AssembliesFromApplicationBaseDirectory();
                scan.AddAllTypesOf<IHttpModule>();
                scan.WithDefaultConventions();
            }));

Can anyone point a structureMap newbie in the right direction?

Plexus

This bug has been reported to stuctureMap devs too on github - hoepfully they will update with fix: github.com/webadvanced/Structuremap.MVC4/issues/6 – Plexus

Answer 1

In structuremap 3.x I used the following in my Registry, with success:

For<HelpController>().Use( ctx => new HelpController() );

Onstage

thanks for that - we've moved to using swagger.io now for api documentation and testing - but hope this helps others – Plexus

Thanks, Being a beginner with StructureMap, your post helped me a lot – Disremember

Answer 2

I also had the same problem. What I found to be the issue was that there are two constructors in the HelpController. One that takes an HttpConfiguration, and another that takes a GlobalConfiguration. I forced StructureMap to call the GlobalConfiguration constuctor by making the Http constructor private.

    public HelpController()
        : this(GlobalConfiguration.Configuration)
    {
    }

    private HelpController(HttpConfiguration config)
    {
        Configuration = config;
    }

That seemed to do the trick.

Underplot

Answer 3

Ensure to skip System.Web.* assemblies from your assembly scanner.

ObjectFactory.Configure(x => x.Scan(scan =>
    {
        scan.TheCallingAssembly();
        scan.AssembliesFromApplicationBaseDirectory(assembly => !assembly.FullName.StartsWith("System.Web"));
        scan.AddAllTypesOf<IHttpModule>();
        scan.WithDefaultConventions();
    }));

It is a bug and we both commented on the Github of StructureMap. I hope that we won't be needed this in the future but for now, it's a quickfix.

Paling

This worked like a charm. The only suggestion I would have is to separate the excluded assemblies in a separate call (in case you have many assemblies being excluded), i.e. - scan.ExcludeNamespace("System.Web"); – Williamson

This doesn't work for me at all. I need to use seeking27's suggestion. – Imaginal

Please note that this was for an MVC 4 web app with basic assembly names. If you are using something different (MVC 5 or MVC 6), you millage may vary. – Paling