How to use this with Visual Studio? about cr

[fungos]

That is supposed to work, as cr was created to solve the dll lock issue. Debugging the host should not lock the plug-in in any way, not sure what may be happening on your case. Try to validate that the plug-in is actually being copied and versioned in the output folder.

[sbond75]

I saw that the plugin was copied in the output folder with a "1" appended. What is the copy of the DLL used for? I would imagine it would be better to unload the DLL, invoke the compiler, then reload the DLL?

[fungos]

cr host will monitor any timestamp change on the original dll, once detected it will unload the current loaded which is a copy that cr host does before loading one dll, and so it will copy this dll over and append a number which is used to track live rollback. Which this, the host will never lock the original dll compiled as it never uses that but only a copy. There are some details though though, just the copy will not actually guarantee the original dll isn't locked as cr needs to patch some debug info inside the copied dll.
in your case, you may have a problem there, where cr is unable to patch this data for some reason (path invalid? too long?), best would be to enable cr tracing and debug the cr host loading the dll.

[sbond75]

I found that I needed to link against the DLL from the host with /DELAY:UNLOAD and /DELAYLOAD: with the dll name appended, following this MSVC feature. However, I have not tested it with cr.h and am now using this for hot reload. If I need to switch back to it, it would probably work fine since this also seems to fix the pdb lock.