best c# Namespace for user functions??

[waltFX]

I have multiple functions that I have developed to use in my strategies..
What namespace should they be defined in so I can reference them in any strategy (and indicators) ?
Thanks!

[NinjaTrader_Jesse]

Hello waltFX,

If you put your functions inside a custom class that you create an instance of then it doesn't matter, you can use any namespace you want. That would work for both indicators or strategies.

If you are trying to use the C# partial class feature you would need to define your methods inside a partial class for the type you want the methods to apply to and in the namespace for that type. This only works for the one type you specify like Strategy as an example. Using partial classes also does not work well if you plan to export the scripts so if this is something you will distribue you should just use a normal C# class and define it in a custom namespace of your choosing.

If this is just for your personal use on that pc you can do something like the following:

namespace NinjaTrader.NinjaScript.Strategies
{
    public partial class Strategy
    {

      public double CalculateDelta(double firstPrice, double secondPrice)
      {
            return Math.Abs(firstPrice - secondPrice);
      }
   }
}​

Then each strategy could just call the method like any other NinjaScript function.

CalculateDelta(Close[0], Open[0]);

[waltFX]

Thanks, I need to be able to see some strategy properties/objects (without passing them in) so I guess the "partial" method will work...
>> I am the only user and transfer source code from my dev system to my prod system so that should work...

[bltdavid]

In my experience, using an abstract base class is
much better than partial classes.

Good reading here, here, and here.

I provide a very useful example of an abstract
base class for Strategies here.

[waltFX]

thanks, In other languages, multiple inheritance could be used but, the last time I looked, c# does not support it...and I moved to DB work (and didn't keep up)
Abstract class might be a better way to implement...
Thanks for the tip!