
but if i export a custom indicator as a complied DLL and then add the AdditionalReferences text file and an external DLL into the root of the zip, NT7 doesn't like that so much.
i also tried manually copying the external DLL into the bin/Custom directory (without manually adding the References), and then including the AdditionalReferences text file in the root of the zip with my compiled indicator, and NT7 didn't like that either.
with that said ... i wanted to clarify two things:
1. is it correct to assume that NT7's import will not support more than one DLL in the zip file?
2. is it also correct to assume that AdditionalReferences text file does not work when importing compiled DLL indicators?
guessing that the answers to #1 and #2 are both "correct, that is not supported", i'm curious to know if anyone within the community has been able to use the built-in NT7 import utility to:
a. import a compiled indicator (DLL)
b. that references an external DLL library (eg. getting NT7 to add the "references" during import)
c. and copying that external library into the bin/Custom folder
d. without using a custom installer
cheers,
-e

Comment