Hello,

After a longer break, I recently started developing new algos again and updated to Zorro 2.70.
I am using VS Code, so the compiled DLL files are produced “externally” and are therefore not directly managed by Zorro.

My workflow is the following: I modify the code, compile it, and run it in Zorro. However, after making further changes and compiling again, I frequently get this error from the C++ compiler:

It appears that Zorro does not release the DLL after a run, so the system cannot overwrite it. This happens with both Zorro and Zorro64. The workarounds I have found so far are restarting Zorro, or running a different script first, and only then compiling and running the updated one.

I am not sure when this behavior started to occur, but is there a way to explicitly unload or unlock the DLL after a Zorro run?

A strategy DLL cannot be released after a run, since it is still needed for chart and panel functions. It is released when the source has a newer timestamp, or when you run a different strategy, or close Zorro. If you debug it with VC++, you can simply click on the "Restart" button after modifying the code. It will then automatically close Zorro, compile, and restart it with the new DLL.