Hello. I am completely new to WealthLab. I purchased a one-year license to test it out; I have been using AmiBroker for many years.
I want to create a C# WinForms application in Visual Studio that accesses WealthLab directly. Ideally, everything would run within my own WinForms application without using the WealthLab user interface.
I have tried various approaches but haven't quite managed to get it working.
What options are available to achieve this? Is it even possible? Or am I limited to using custom DLLs within the WealthLab interface? WealthLab is installed and licensed on my development machine.
I want to create a C# WinForms application in Visual Studio that accesses WealthLab directly. Ideally, everything would run within my own WinForms application without using the WealthLab user interface.
I have tried various approaches but haven't quite managed to get it working.
What options are available to achieve this? Is it even possible? Or am I limited to using custom DLLs within the WealthLab interface? WealthLab is installed and licensed on my development machine.
Rename
I suggest telling us the basic functionality you want to achieve with your WinForms application. For your purposes, there may be a simpler approach that utilizes Wealth Lab user interface.
That is relatively easy to describe. I want full access to all the functionalities of the WealthLab .NET API via a C# WinForm application. Everything should run within my own WinForm interface—without launching WealthLab itself or operating within the WealthLab GUI.
In other words... developing trading systems, optimization, backtesting, importing external data into a native WealthLab database from various sources (such as real-time data from SQL Server combined with Norgate "Current and Past" EOD data), and much more. I’ve reviewed the API documentation, and as far as I can tell, it covers all the necessary capabilities.
I’ve been doing exactly this with AmiBroker for many years and have been actively trading using that setup for a long time. I realize that WealthLab will be slower than AmiBroker when it comes to optimization. Nevertheless, executing everything consistently in C# within a WinForm application would suit my trading setup better. Furthermore, WealthLab’s functionality seems superior to AmiBroker’s in certain areas.
I initially assumed it would work this way, but I couldn't find a solution during my initial tests.
In other words... developing trading systems, optimization, backtesting, importing external data into a native WealthLab database from various sources (such as real-time data from SQL Server combined with Norgate "Current and Past" EOD data), and much more. I’ve reviewed the API documentation, and as far as I can tell, it covers all the necessary capabilities.
I’ve been doing exactly this with AmiBroker for many years and have been actively trading using that setup for a long time. I realize that WealthLab will be slower than AmiBroker when it comes to optimization. Nevertheless, executing everything consistently in C# within a WinForm application would suit my trading setup better. Furthermore, WealthLab’s functionality seems superior to AmiBroker’s in certain areas.
I initially assumed it would work this way, but I couldn't find a solution during my initial tests.
I would consider using WPF instead of WinForms, albeit you may have significant reasons for using WinForms, perhaps your own libraries.
You mentioned you tried various approaches, but haven't quite managed to get it working. What are some of the issues you are encountering?
You mentioned you tried various approaches, but haven't quite managed to get it working. What are some of the issues you are encountering?
You could leverage the REST API. It was built with AI in mind it it might deliver just what you need. It doesn’t yet expose everything. but you can run backtests and get complete results. Look up REST in the WL help.
@paul1986
Sure... using WPF would be perfectly feasible. My planned developments—such as real-time data retrieval, advanced automation, and much more—could easily be implemented. That said, even with WPF and C#, it likely wouldn't be possible to create a fully standalone solution (running on the same machine where WL is installed and licensed).
@Glitch
A REST API would work; I’ve tested it extensively. However... I find that approach extremely labor-intensive. Plus, I’m concerned that using HTTPS might result in significant speed penalties, as it introduces an extra layer of processing.
I think the official approach—using a C# DLL developed in Visual Studio—would likely be the fastest method. I might be able to launch WL from my own C# program and then execute that DLL within it.
On a personal note: I’m a complete newcomer to WL. The fact that I’m getting such helpful, relevant answers here speaks volumes about WL. Many thanks for that.
Sure... using WPF would be perfectly feasible. My planned developments—such as real-time data retrieval, advanced automation, and much more—could easily be implemented. That said, even with WPF and C#, it likely wouldn't be possible to create a fully standalone solution (running on the same machine where WL is installed and licensed).
@Glitch
A REST API would work; I’ve tested it extensively. However... I find that approach extremely labor-intensive. Plus, I’m concerned that using HTTPS might result in significant speed penalties, as it introduces an extra layer of processing.
I think the official approach—using a C# DLL developed in Visual Studio—would likely be the fastest method. I might be able to launch WL from my own C# program and then execute that DLL within it.
On a personal note: I’m a complete newcomer to WL. The fact that I’m getting such helpful, relevant answers here speaks volumes about WL. Many thanks for that.
Your Response
Post
Edit Post
Login is required