Version 6.5.1000.10 and Custom Indicators

[drob9876]

Custom indicators that I'm using from the shared NinjaTrader Indicator forum compile without a problem with NT Version 6.5.1000.9. When I just ran the 6.5.1000.10 setup I'm getting compile errors with the following error message:

Indicator\@ADL.cs The type 'System.Web.Services.Protocols.SoapHttpClientProto col' is defined in an assembly that is not referenced. You must add a reference to assembly 'System.Web.Services, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. CS0012 - click for info 18 11

I running NT on Windows XP Pro.

Thank you for any suggestions or comments,

DRob

[NinjaTrader_RJ]

Hello,

Thank you for your post.

I suggest to remove this 3rd party application and reinstall using the vendors uninstallation/installation instructions.

The default method in NinjaTrader is File --> Utilities --> Remove NinjaScript Assembly, however the vendor may require another method.

[drob9876]

Thanks, RJStein

Trying to remove the assembly fails with a Remove Failed error. You have custom NinjaScript files on your PC that have programming errors. These errors must be resolved before removing...

I'm just going back to Version 6.5.1000.9 until a solution can be found. It is like a a circle type error; I can't find the references to the programming error in the indicator(s) and I can't remove the NinjaScript assembly.

Something has to be different with 6.5.1000.10 and even 6.5.1000.11 with the compiling of indicators.

Any suggestions would be appreciated,

DRob

[NinjaTrader_RJ]

Interesting... can you confirm that you do not have any issues going back to .9?

[drob9876]

RJStein,

I'm working on it now. I'll post the results asap.

Thanks

DRob

[drob9876]

RJStein,

I uninstalled NT and installed version 6.5.1000.11 and started from scratch. Imported the identical custom indicators that I was using and they compiled without a problem. I did not have a copy of ".9" to reinstall.

Don't know what happened to cause the compile errors before on ".10", but a fresh install of 10 might have worked as well.

Thanks for your help,

DRob