What could make Castle Windsor Dependency Injection differ by build config? Castle.MicroKernel.ComponentRegistrationException from name collision

Question

I support a WPF application with multiple build configurations (local, dev, stage, etc) that uses Castle Windsor for dependency injection, and click-once for deployment. I had to update the certificates for click-once and when I was testing I started getting Castle.MicroKernel.ComponentRegistrationExceptions but only when testing the stage build configuration. local and dev build configurations work fine but stage gets the above exception with the following message:

Component X could not be registered. There is already a component with that name. Did you want to modify the existing component instead? If not, make sure you specify a unique name.

I tried breakpoint-ing the registration code and it only appears to hit once but the one time is when it crashes.. How else can I troubleshoot this and has anyone seen this before?

foldinglettuce · Accepted Answer · 2022-03-11 01:25:33Z

0

Deleting the bin folder and rebuilding made the dependency injection behave.

answered Mar 11, 2022 at 1:25

foldinglettuce

54010 silver badges28 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

What could make Castle Windsor Dependency Injection differ by build config? Castle.MicroKernel.ComponentRegistrationException from name collision

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related