SoftPro Developer Forum

We are currently using two server packages and each one is referencing the same custom dll.
While working on the second server package, we added a few new fields to the custom dll and (without updating it for the first package) installed the second package.

The code in the non-updated server package is executed first, causing the "old" version of the dll to be loaded into the CLR and leaving our newly updated package without the fields we just added.

Is there a place we can store our shared dlls (to get them loaded before the package-specific version) so we don't have to re-deploy all of our server packages every time we change it?

This is a .NET question. There are .NET ways of loading specific assemblies into the Application Domain based on non-default criteria. Be aware that the order in which Select loads packages is indeterminate - do not depend on any specific order!