With the intent to use feature flagging to revert any possible production issue introduced during development, we are exploring options to cover various scenarios and so fare we were unable to identify this one.
In a .net application how would you feature flag the update of a nuget package?
A few issues listed here:
- Two dlls with the same name can't co-exist in the same application (or web application) folder.
- renaming old dlls to let them use side by side with the new one can be a solution but this means that the assembly loading should be made dynamic more likely done at startup which most likely would need you do reboot the application
Online I could not find any information nor any mention, so maybe we are trying to walk towards an unusual direction.
Thank you in advance