How-to-write-data-from-Wealth-Lab-C-to-MongoDB

I’d suggest writing a middleware executable that can write to Mongo DB. It would read the data from a text file that is output from the WL Strategy.

I think this would be far less painful and avoid any DLL hell versioning issues.

The Mongo DB isn't a stat package. If you want to run statistics, why not write your data directly to R? You can even use R.NET to do it. The downside is that both applications have to be running together to use R.NET. See https://www.wealth-lab.com/Discussion/Using-the-R-statistics-program-with-WL-7247

QUOTE:
I’d suggest writing a middleware executable that can write to Mongo DB. It would read the data from a text file that is output from the WL Strategy.

That could be plan C. Plan B would be to develop a custom C# library that supports MongoDB updates within Welath-Lab. I did the same to transfer trading signals to WhatsApp via the Twilio-API.

QUOTE:
The Mongo DB isn't a stat package. If you want to run statistics, why not write your data directly to R?

I don't need to run statistics to analyze the data any further. The only purpose to transfer the data to MongoDB is to use them in a Next.js 13 fullstack application.

What about executing the CRUD operations via REST?
https://www.mongodb.com/blog/post/introducing-mongodb-atlas-data-api-now-available-preview

REST operations under native C# are too crappy. With RestSharp or Flurl it would be usable with very little boilerplate code, but a 3rd party library is needed as well.

Basically it would be quite simple. The MongoDB.Net Driver is just a DLL and an XML file. Therefore it is ok to copy the two files into the directory C:\Program Files\Quantacula, LLC\WealthLab 8. However, WL does not recognize the assembly, neither under the Assembly References nor in the Code Editor.

Is there another way "to marry" such a 3rd party assembly with WL?

QUOTE:
Therefore it is ok to copy the two files into the directory C:\Program Files\Quantacula, LLC\WealthLab 8.

Should be enough.

I don't see any "red squigglies" in the script. Did WealthLab complain about the compile?

Did you also copy all of the various DLLs required?

In fact, there were many more DLL's than first thought. I had to pick them all out of the NuGet package and copy them into the WL directory. Finally, the MongoDB classes are recognized and the collection updates are working with plain-vanilla code, directly out of WL.

And good thing you didn’t run into a conflict where some of those dlls conflict with ones WL already has but with differing versions. Glad you got it working!

Yes that would have been a no go if there had been a conflict. So I can send all the updates directly out of the SM. With more than a dozen of systems, this is much easier than controlling everything via a piece of middleware.