Nov 10, 2010
I have this situation where LoadWithPartialName appears to be the only good alternative, although it is marked as Obsolete. I work in a very tight dev environment with versioning and deployment policies that cannot be easily changed or bypassed. Let's say there's a .NET executable that I have no control on (from another division). Let's call this the client AppA application. AppA's version is 10.11.12.x. Application AppA has a direct reference to one of our class library that provides some service to the caller (returns some information).
View 2 Replies
Let's call it SvcB and the version is also 10.11.12.x. Now, AppA's division does not need to update their system as often as we do, so AppA's version will stay 10.11.12.x for some time, probably until we decide to change the format of the class that is exchanged between us. Our division needs to change the logic behind the service SvcB more often and the version must change with every major deployement.
So let's say we change the logic and we deploy a new version of SvcB, 11.02.11.x. AppA will still reference the old version, so the logic being used is now incorrect. We are thinking of creating a new "facade" to our service. Let's call it SvcFrontB. SvcFrontB's version will stay the same, in sync with the AppA's own version. Now I need SvcFrontB to load the most recent version of SvcB through reflection. This way, I am sure the latest logic is always used. How do I achieve that without using LoadWithPartialName ?