When testing code for PDM tasks, I have found once you run any part of your code the only way to get PDM to let go of the .dll file is to restart. When testing out code on other PDM commands I usually just restart explorer and I can rebuild my .dll file. I've also tried exiting the PDM client program and ending the EdmServer.exe in the task manager.
Anyone have an easier method to get PDM to let go of my .dll file when I'm testing custom tasks.
Testing custom PDM task
Testing custom PDM task
Yes, I was. I have found a workable solution. My main issue was I was still running the addin as a debug addin. Once, I fully loaded the addin simply shutting everything down before I rebuilt the dll allowed me to keep going. I just had to relaunch whatever I was using to test out the task.
Go to full post
Re: Testing custom PDM task
Are you updating the dlls through the PDM Admin tool, Add-ins node, and Files tab of the add-in? Remove the files then add the new ones. This is how I was taught to update them after recompiling.
Re: Testing custom PDM task
Yes, I was. I have found a workable solution. My main issue was I was still running the addin as a debug addin. Once, I fully loaded the addin simply shutting everything down before I rebuilt the dll allowed me to keep going. I just had to relaunch whatever I was using to test out the task.
Re: Testing custom PDM task
You cannot debug the task hooks using the debug add-in option from the administration tool, unfortunately. Even hooking into the host process is very annoying. We have a unit and integration testing framework for task add-ins : https://bluebyte.biz/product/orca-unit- ... m-add-ins/