Indicator's result file size (algo) - why so big?

ctid256802
22 Nov 2016, 12:48

Anyone? Spotware?

trading.kay27
27 Jan 2017, 08:56

RE:

ctid256802 said:

Hello

I've got the following question/problem. I'm developing indicators which reference my web communication library - i.e. MyConnect.dll, which on it's turn references couple of other libraries - i.e. A.dll, B.dll, C.dll etc.

So it looks like this

Indicator -> MyConnect.dll -> [A.dll, B.dll, C.dll]

When I'm adding only MyConnect.dll to indicator's references everything compiles just fine. BUT! When trying to create an instance I'm getting the errors like "A.dll cannot be found" etc. So eventually I'm having all DLL-s are added to the indicator's references. So now it's working but the size of algo-file is big - 600K! Why is it so and how it can be decreased?

 

Sorry if its too late for this but I'll answer it anyway. The size of algo file is big is because, when all files are compiled in algo file(which is a complete package), compiler put all referenced dlls into one single package - algo file.

ctid256802
07 Feb 2017, 17:44

RE: RE:

hook_1000 said:

 

Sorry if its too late for this but I'll answer it anyway. The size of algo file is big is because, when all files are compiled in algo file(which is a complete package), compiler put all referenced dlls into one single package - algo file.

Hi hook,

Thank you for your answer - theidea is clear: all referenced DLLs go to each algo file. But wouldn't it be better to keep them separately? The problem is that I have bunch of indicators referencing same DLLs (actually I have 100+ of indicators) and as you can understand the whole size get really big. I would really appreciate to have an option - whether to have these references be buld inside algo file or be distrivuted separately.