Today my main compiled strategy stopped showing in WL7 list of strategies.
There was no indication in the log file why WL fails to recognize the dll as WL compiled strategies.
Later I found out that I have a Dictionary Data structure with a duplicate key. It compiles fine under VS 2022, but WL7 runtime throughs exception.
I tried the same code directly in WL7. WL7 compiler was smarter than VS 2022. It generated an error.
Question:
Where to look to find out why WL7 refuses to load and recognize a dll as a compiled strategy? I expected log file viewer to show an error, but it didn't.
There was no indication in the log file why WL fails to recognize the dll as WL compiled strategies.
Later I found out that I have a Dictionary Data structure with a duplicate key. It compiles fine under VS 2022, but WL7 runtime throughs exception.
I tried the same code directly in WL7. WL7 compiler was smarter than VS 2022. It generated an error.
Question:
Where to look to find out why WL7 refuses to load and recognize a dll as a compiled strategy? I expected log file viewer to show an error, but it didn't.
Rename
Please update any extensions you may have installed and recompile your project. Apparently there was a breaking change in some API.
The latest build of WL7 is already installed so a reinstall isn't necessary.
The latest build of WL7 is already installed so a reinstall isn't necessary.
I am aware of the issue with latest build. I have all extensions up-to-date. The issue I have is repro in at least builds 33 and up.
Let me suggest you set a breakpoint in your solution and step through the code to determine why your strategy does not load.
https://www.wealth-lab.com/Support/ExtensionApi/StrategyLibrary
https://www.wealth-lab.com/Discussion/New-instruction-for-using-Visual-Studio-to-develop-and-debug-strategies-5494
https://www.wealth-lab.com/Support/ExtensionApi/StrategyLibrary
https://www.wealth-lab.com/Discussion/New-instruction-for-using-Visual-Studio-to-develop-and-debug-strategies-5494
Is your solution targeting .NET framework 3.1?
Yes.
Then you need to follow Post #1 (recompile it, making sure that any dependent assemblies - such as extensions - are up to date and you're not picking them from any folders outside Wealth-Lab's) and then #3, if required (set a breakpoint and step through).
Your Response
Post
Edit Post
Login is required