|
Kassel / Germany
Experience: None
Platform: MC
Broker: IB
Trading: CL/NG/ES
Posts: 72 since Aug 2011
Thanks Given: 128
Thanks Received: 62
|
This is what I'm using a DLL (written in C#) with an Interop-DLL which propagates the calls from MC, done in VS2017.
On top helper dlls for MySQL and a SharedData-Dll for a better global variables implementation and a common messaging provider for communication with any needed app. But yes, documentation is very rare and partly very old. Hard to get information about extensions of MC or the way extension are done by using a DLL.
Not sure where the problem is as there are quite a few things to consider... so I write down a few things which can be of help maybe.
- all your pieces of code in your first post here seem to be correct
- In my DLL I'm referring to PLTypes.dll and PLKit.dll. The latter one is important. In an older docu they're talking about another dll but thas is obsolete, you need PLKit.
- In C++ I refer to it: #import "C:\Program Files\TS Support\MultiCharts64\PLKit.dll" no_namespace
- All of my DLLs I copy to: C:\Program Files\TS Support\MultiCharts64
- In the past there was a different directory for MC and the installations of newer versions not always delete them. So it's possible to drop the dll into the wrong directory.
- Very useful I've found the many different logfiles: C:\Users\User\AppData\Local\TS Support\MultiCharts64\11.0.16148.400\Logs\MultiCharts64 When calling the dll problems will be logged from StudyRunner --> StudyRunner_Error.txt --> in case the signature imported into MC is not found the following was logged: <<ASSERT>> Description: Unknown exception during resolve File: ResolveObject.cpp
- If things are working you can easily start MC from VS and stopping at a breakpoint inside your dll.
- when dealing with your own external dll within MC you should be very cautious regarding any exception thrown. Don't let things like this through to MC, otherwise MC gets instable and can possible quit out of nowhere.
|
