Referencing the library from a custom build causes DI issues about identityserver3.wsfederation HOT 4 CLOSED

The code is designed to be referenced via NuGet. If you must reference it directly then you must setup the right environment (such as the correct dependencies in the DI system).

from identityserver3.wsfederation.

Hmm, I understand.. I'm trying to debug the code for a better understanding of the WS Federation signout functionality. I've tryied in various ways but couldn't yet handle it the right way.

var configuration = new HttpConfiguration();
            var builder = new ContainerBuilder();
            var container = builder.Build();

            configuration.DependencyResolver = new AutofacWebApiDependencyResolver(container);
            DependencyResolver.SetResolver(new AutofacDependencyResolver(container));

            app.UseAutofacMiddleware(container);
            app.UseAutofacMvc();
            app.UseAutofacWebApi(configuration);

Can you please show the bare minimum in order to make it work. Or at least point to the right direction. Thank you.

from identityserver3.wsfederation.

@brockallen Is this somehow related to this issue IdentityServer/IdentityServer3#611

from identityserver3.wsfederation.

Yea, not sure. Perhaps the best way to debug into the ws-fed code would be to run the sample host that's in the ws-fed repo. It's referencing the code at the project level (and not via nuget).

from identityserver3.wsfederation.