The one challenges when developing extensions or strategies is that when you compile a new version of the DLL you need to close WL to be able to copy the new DLL since the file is locked. Which is problematic if you are running strategies at the same time.
I was wondering if this would work to solve that.
Have two directories in the WL8 directory
- Custom Release
- Custom Debug
By default have the application automatically load the Custom Release DLL's and create a execution flag when running the application that directs the application to load the Custom Debug DLL's instead of the Release DLL's for development which should avoid the file lock issue.
I was wondering if this would work to solve that.
Have two directories in the WL8 directory
- Custom Release
- Custom Debug
By default have the application automatically load the Custom Release DLL's and create a execution flag when running the application that directs the application to load the Custom Debug DLL's instead of the Release DLL's for development which should avoid the file lock issue.
Rename
This is not required. Talked about this several times on the forum already. See part re: "Edit and Continue":
https://www.wealth-lab.com/Support/ExtensionApi/StrategyLibrary
https://www.wealth-lab.com/Support/ExtensionApi/StrategyLibrary
Boom! Thank you very much.
Hello mjj3,
if you like you can give a thumb up in the feature request.
https://www.wealth-lab.com/Discussion/WL-Working-Folder-VS-debugging-mode-8184
Although this can be implemented and there are certainly good reasons, there is one argument that should be considered in any case. If an instance of WL is in trading mode (not backtesting, evolving etc.), one should consider well whether to develop on the same machine at the same time.
if you like you can give a thumb up in the feature request.
https://www.wealth-lab.com/Discussion/WL-Working-Folder-VS-debugging-mode-8184
Although this can be implemented and there are certainly good reasons, there is one argument that should be considered in any case. If an instance of WL is in trading mode (not backtesting, evolving etc.), one should consider well whether to develop on the same machine at the same time.
Your Response
Post
Edit Post
Login is required