I thought this thread might be useful for others (like me) who are working their way through Neoticker, but prefer to use c# and IDL as a development combination from the very beginning.
My reasons for bypassing (as far as possible) Scripts, BackTestEZ (or whatever) and jumping straight to c# are (1) That I am happier working in c#, (2) That I know I am going to want a unified environment for optimisation and performance analysis outside Neoticker itself - and I would like to retain control of that environment from the first day and (3) That - although it doesn't appear to be the most natural integration in the world the ability to use c# as the development language was one of my reasons for choosing NT.
The fact that the documentation is scant, and the examples very basic just seems to be par for the course with NT. I have no intention of using the better supported Delphi because I left Delphi and Object Pascal alone years ago for .net.
c# With Neoticker Basics
Moderator: moderators
Please add www.kreslik.com to your ad blocker white list.
Thank you for your support.
Thank you for your support.
Creating the C# DLL
Using Visual Studio (or other C# editor) create a new project of type class library. Set the project options so that it will output a dll into a named directory (this is the dll directory you referred to in Creating the wrapper above).
Add a project reference (Project / Add Reference / Browse tab) to the Neoticker interop dll (this can be found in the neoticker samples / c# directory ? is there a more stable location for the latest version?).
Add a using clause to your prinicpal class file (using Neoticker) and make a note of the namespace and principal class name (you will need these when creating a wrapper script in Neoticker).
Creating the wrapper
Using the Neoticker script editor (Program / Script Editor) create a new script. In the Setup section (Indicator / Setup) name the indicator, and enter a description. Set the Language to IDL and the class to Indicator. For the time being ignore the other settings
Under the IDL Tab, ignore the External File and ActiveX Class. Set the name (and directory, if appropriate) of the .net dll which your .net project will output, and in the .net class text box set the Namespace and classname (Namespace.ClassName) of the class which will implement IDLCallEx.
Ensure that the Early Binding option is checked.
Check that the wrapper verifies (Indicator / Verify) and installs (Indicator / Install)
Questions:-
1. Is there a standard location where any newly updated neoticker interop dll would be published?
Using Visual Studio (or other C# editor) create a new project of type class library. Set the project options so that it will output a dll into a named directory (this is the dll directory you referred to in Creating the wrapper above).
Add a project reference (Project / Add Reference / Browse tab) to the Neoticker interop dll (this can be found in the neoticker samples / c# directory ? is there a more stable location for the latest version?).
Add a using clause to your prinicpal class file (using Neoticker) and make a note of the namespace and principal class name (you will need these when creating a wrapper script in Neoticker).
Creating the wrapper
Using the Neoticker script editor (Program / Script Editor) create a new script. In the Setup section (Indicator / Setup) name the indicator, and enter a description. Set the Language to IDL and the class to Indicator. For the time being ignore the other settings
Under the IDL Tab, ignore the External File and ActiveX Class. Set the name (and directory, if appropriate) of the .net dll which your .net project will output, and in the .net class text box set the Namespace and classname (Namespace.ClassName) of the class which will implement IDLCallEx.
Ensure that the Early Binding option is checked.
Check that the wrapper verifies (Indicator / Verify) and installs (Indicator / Install)
Questions:-
1. Is there a standard location where any newly updated neoticker interop dll would be published?
Please add www.kreslik.com to your ad blocker white list.
Thank you for your support.
Thank you for your support.