DLL Reference error

[i001962]

I'm trying to code an indicator that calls a third party web service.
(realize my pgm skills are rusty so I hope I explain this correctly)

I have turned the web service (WSDL) into a C# pgm and compiled it into a DLL. The DLL build uses these references /r:System.dll /r:System.Web.dll /r:System.Web.Services.dll
/r:System.Xml.dll

When I add this to my indicator as a reference the class is recognized and compiles fine but during runtime the indicator pukes (very nicely of course by simply not doing anything).

Any suggestion? I tried compiling the DLL in C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 and am running NinjaT 6.5.1000.14 (the DLL works fine when referenced by external programs.

I realize NT support may not cover this type of request but thought there may be some hints as to how to debug this or lessons learned from others extendign the NT platform.

Thank you,
Kevin

[i001962]

Mystery solved

Sorry to have poluted the forum with my ignorance.

[NinjaTrader_Bertrand]

No worries, great you got it working.

[tealover007]

How did you solve it?

Sorry to have poluted the forum with my ignorance.

I am very curious about the solution as I have the same problem.

I've compiled it into .NET 2.0, I "referenced" it, I've placed dll file everywhere I could think of, indicator that uses(calls methods) of this DLL compiles in Ninja, but then didn't run at all.

That's what I am getting in trace file:

Could not load file or assembly 'IndicatorsForNinja, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.

[NinjaTrader_JoshP]

tealover007,

Did you add a reference to this in the NinjaScript Editor via a right click -> References and not just from code?

[tealover007]

tealover007,

Did you add a reference to this in the NinjaScript Editor via a right click -> References and not just from code?

yes, I did. Next day it started working magically. Still not sure what was the issue.

[NinjaTrader_Bertrand]

It would also need a fresh restart of NT then to load the assemblies...