Indicator Namespace How Does It Work

[geoMEAN]

If You = NT Staff, stop reading. You shouldn't use up your time answering this sort of question.... I understand C# is not supported here.

I've recently been trying to learn C# up to a level where I will feel comfortable coding Ninjascripts.

One exercise has been to look at the auto-generated code in ninjascript editor to learn.

Consider picture below. I'm wondering how the Ninjatrader.Indicator namespace is able to put together all the indicators used in Ninjatrader without having some sort of equilvalent of the "Partial" keyword that is sometimes used for a class where the class is defined in multiple files. In this example, my stupid "If Open=Close indicator" is the only indicator here. So just wondering from a programming perspective how C# knows to compile all the different indicators into the same Ninjatrader.Indicator namespace.

And yes I know this is nit-picky but I'm trying to understand and process all this stuff.

[NinjaTrader_Dierk]

>> If You = NT Staff, stop reading
Done

[geoMEAN]

Dierk, well at least you follow instructions!

Perhaps I'll elicit a quick response from a programmer if I refrase in shorter language:

Can the same namespace be defined across multiple .cs files?

E.g.:
//in file SMA.cs
namespace NinjaTrader.Indicator
{
public class SMA : Indicator
{
}
}
//in file EMA.cs
namespace NinjaTrader.Indicator
{
public class EMA : Indicator
{
}
}

I imagine this is what is happening each time I create a new indicator as I've heard that all strats are kept in 1 compiled strat file and all indicators kept in 1 compiled indicator file.

[NinjaTrader_Dierk]

>> Can the same namespace be defined across multiple .cs files?
That's how all NS files work.

[TakisTakis]

Originally Posted by geoMEAN

I imagine this is what is happening each time I create a new indicator as I've heard that all strats are kept in 1 compiled strat file and all indicators kept in 1 compiled indicator file.

This explains why if we mess up one strategy, no other strategy works until we fix the one that has the issue. Or why if we forget a reference in one file and take away the dll and then the strat that used it, we still have errors in other strats until the reference is GLOBALLY removed... I think...