Question

I have two completely independent web application that each use a shared core dll. For deployment and versioning purposes I’d like to be able to deploy a single copy of the “core” dll for both apps to use. I’d also like to be able to support, if needed, the ability to substitute the core DLL at deployment as an option. In other words, app1 could use core dll version 1, and app2 could use core dll version 2. Is there a DI container that will support resolving implementation classes in a single DLL by path to support these features? IOW, app1 would grab it’s implementation classes from c:\corev1\core.dll, and app2 would grab it’s implementation classes from c:\corev2\core.dll as a simple example? I need to avoid direct references to core.dll due to our deployment strategy where all applications are independent.

Answer 1

You don’t need DI or a container to do this. Assembly Versioning is supported by .NET out of the box.

Just deploy the core.dll alongside the rest of your application binaries for each application and version them independently of each other.