When Registering a Custom AgilePart, the Assembly is Not Updated with the Latest Version of the DLL

Applies To

Symptoms

When using the AgilePart Deployment Wizard to remove and re-add a custom AgilePart DLL, it doesn't seem to update the assembly with the latest version of the DLL that was compiled.

Cause

If a previous version of the assembly was already loaded into memory by AgilePoint Server, any changes to the assembly would not take effect until after AgilePoint Server is restarted.

Resolution

Modifying the assembly will not automatically cause AgilePoint Server to restart. If you want any DLL changes to take effect immediately, you will need to restart IIS or the AgilePoint Server (please refer to the AgilePoint User's Guide for instructions on how to safely shut down and/or restart AgilePoint Server).

NOTE: Modifying any file in the BIN directory will automatically cause IIS to restart AgilePoint Server. So copying the DLL into AgilePoint Server's BIN directory should force the changed DLL to take effect immediately. However, if an older version of the DLL is also in the machine's GAC (Global Assembly Cache), the older DLL may still be used if you only put the newer DLL in the BIN folder.