Help with compiled assembly

[RedDuke]

Hello,

https://forum.ninjatrader.com/forum/ninjatrader-7/general-development/1214905-default-constructor

I am getting exactly the same error. This is my own assembly. I made sure there is no underscore in the name. I have NinjaTrader 8.1.... this was never an issue in NinjaTrader 8.0.....

I prefer to keep code compiled as assembly in VMs. Out of curiosity I manually copied the files to VM, all compiled without an issue and I was able to use indicators/strategies. But when the same files are put into protected assembly this issues manifest. The import goes in without an issue, but when I try to access indicators same exact error is shown.

Thanks,
redduke

[NinjaTrader_Jesse]

Hello RedDuke,

It looks like the previous user solved this by making sure the vendor information in the VendorLicense check was valid. For your situation you would want to follow the same steps that were posted to reply # 2 and check what part of your code is having an error. If its a VendorLicense line of code you would need to make sure you have used the correct values.

[RedDuke]

Hi Jesse,

This is my own code. I use protected assembly as security feature to deploy my own source code. There is no vendor involved. I just export code from my development laptop and import into Ninja running on VM. This is the first time I attempted this in Ninja 8.1.7. How can I see where the error is? The code compiles are run normally when scripts are just copied directly.
Thanks,
redduke

[NinjaTrader_Jesse]

Hello RedDuke,

As it seems this is unrelated to the thread you posted in i went ahead and moved this into a new thread.

The easiest way to check what problem is happening would be to comment out your custom code and export only the structure of the script. For example if this was an indicator you would comment everything out besides OnStateChange and OnBarUpdate, just the custom code you added. Then export the script and test that it works to import and use it. If you dont get an error you can do the same tests again but uncomment some of the code. Once you do this and get the error the last uncommented code would relate to the problem.