Distributing Indicators

[moflaherty]

Can I verify the steps we need to take to distribute our own indicators? This does not seem to be working for us. We are using NT7, and I have created a clean XP environment to test.

We export the indicator from our build machine. (Files-Utilities-Export NinjaScript.) We would like to create our own installer since we want to include help files, etc. We are taking the .cs and .dll from the zip and adding them to our custom installer. Our installer is placing these files in the Documents\NinjaTrader 7\bin\Custom folder on the machine.

The problem we are having is that we need to include a reference to a Microsoft .NET library that is not available within NT. When we attempt to use the indicator in the test environment after installing the files as mentioned above, we are getting errors because of the missing reference. If we open up a new test script, right-click, and choose References, we can add the .NET library no problem. But it also seems like we need to reference our indicator this same way. Once we reference these two components, then everything is good.

So the questions are (1) is there a way to programmatically create the reference that is needed in our installer and set this up without making the users do this, and (2) why would a reference to our indicator be required? (3) Is there another way we should be doing this?

Thanks!
Michael

[NinjaTrader_Bertrand]

Michael, correct you want to a reference to all needed assemblies, the .NET one and your custom one created for distribution - there's a way to do all this 'behind the scenes' to simplify the distribution tasks (this would include presetup chart / MA templates as well if needed) -

http://www.ninjatrader.com/support/helpGuides/nt7/distribution_procedure.htm

[moflaherty]

?

Just to be clear, we want to have our installer place all the necessary files on the computer and not have the end-user walk through an importation process. Is it possible to place the DLL and CS in the folder, but also add references to the necessary .NET framework file?

Unless I am missing something, the instructions you refer me to are strickly for creating the zip for the end-user to import manually.

Thanks!
Michael

[NinjaTrader_Bertrand]

Unfortunately you could not add references automatically, an import of the zip containing the references.txt would be needed for this to happen.

[moflaherty]

?

OK, so if I need to add a reference to a Microsoft .NET DLL in the AdditionalReferences.txt file, how do I do that? Do I need to be concerned with paths?

Also, any update on the RemoteSoft protection? It sounded like NT is investigating some alternatives.

Thanks again!
Michael

[NinjaTrader_Brett]

Hello,

I will have Bertrand respond once he is back into the office today.

Thank You for your patience.

[NinjaTrader_Bertrand]

Yes Michael, you would need to enter the full path needed, this is normally under the Window > Microsoft .NET folder and then the specific framework version you need the DLL from.

Correct, we're currently working on an alternative way to obfuscate the sourcecodes - if you need code protected please contact us directly at support at ninjatrader dot com

[moflaherty]

?

I am not 100% sure yet, but I believe XP places them in the Program Files folder whereas Vista and 7 place them under .NET in the Windows folder. This might be an issue.

OK, I won't spend the money with RemoteSoft just yet. I appreciate knowing you will protect it worse case...

[moflaherty]

Red Gate

You might check out Red Gate; we use their stuff: I am sure they would make a deal: http://www.red-gate.com/products/sma...mbly/index.htm

[NinjaTrader_Bertrand]

Thanks for the input and suggstion - I believe the DLL's are still under Windows > Microsoft .NET > Framwork > your version in XP.

[moflaherty]

Windows XP .NET Files

FYI: Using the Windows XP environment under Windows 7 (which we test with), the 3.0 .NET framework DLLs are NOT under the Windows folder.