Applies To
-
AgilePoint Envision
-
AgilePoint Developer
Objective
Testing and debugging custom AgileShapes
Summary
When testing and debugging custom AgileShapes (including AgileParts and AgileWorks), how can I ensure that AgilePoint Envision is using the correct version because once it is installed in the GAC, it is hard to tell whether AgilePoint Envision is using the latest version especially when you are changing the code frequently.
Details
- When making minor implementation changes to an AgilePart or AgileWork, use the same assembly version number when you recompile. (i.e. make sure that the AssemblyInfo file in your project uses a hard-coded version number, and does not include any wildcards).
- After compiling a new version, add it to the GAC, or use the AgilePart Deployment Utility to deploy it.
-
If AgilePoint Server is already running and has already loaded an older copy of the assembly into memory, then you will need to reset IIS (e.g. run "iisreset") or restart the AgilePoint Server application in order to force AgilePoint Server to load the newer copy of the assembly into memory the next time it is needed.
-
If you compile a new copy of the assembly with a
new assembly version number (as opposed to #1 above), then you will also need to unregister and reregister the AgileShape's assembly in Envision. However, if you followed the recommendations in #1 above, then you do not need to unregister or reregister the AgileShape's assembly from Envision (other than the single, initial registration of the assembly before you first use it.
If you follow the above steps, then you should be able to test and debug your custom AgileShapes without any problems.
