methods, namespaces etc to exclude from obfuscation?

[iantriestrading]

Are there any standard NT methods, namespaces or properties I need to exclude from obfuscation to that my indicator can be imported without errors? What about for a strategy?

[NinjaTrader_ChelseaB]

Hello iantriestrading,

There isn't way to exclude specific code from obfuscation with Agile.NET. When exporting the obfuscation will be applied to the entire export as the assembly is built.

That said, no, you don't need to exclude anything from obfuscation to allow a script to import.

You will need to ensure you are using the latest release 8.1.3.1 and have Agile.NET 6.1.9.2 installed.

Then ensure all dependencies are included with the export, including any references to 3rd party assemblies.

If you are exporting multiple classes, we recommend isolating these to separate assemblies to prevent duplicate class errors.
Below is a link to a video.

https://drive.google.com/file/d/1D9qMVu1Ahb58Z82IVT0R7caTu0icg9nC/view?usp=drive_link

[iantriestrading]

Thanks Cheslea.
I'm actually using .net Reactor because peolpe on the forum (and on Trustpilot) said that Agile.net support is nonexistent and they paid and never received license, etc.

I actually reached out to Agile.net support previously with a couple questions and they never replied to me either. I also found developers saying Agile.net is so easy to crack/deobfuscate, so I figured I should not use it.

If you can provide any information that counters this I would appreciate it because it would be so much easier for me to just check the Agile.net checkbox in Export Assembly window, vs using .net Reactor separately with hundreds of configuration options.

BTW, regarding the video you made to help us with common dependent classes: I have used this video in the past to help me create a reference DLL for shared classes utilized by a few of my custom indicators. So just wanted to say thanks for that.

[NinjaTrader_ChelseaB]

Hello iantriestrading,

Unfortunately, we cannot provide any assistance with using 3rd party obfuscators.

The SecureTeam has a smaller support team and can sometimes have a delay in their replies, but from what I've gathered from other users they do tend to get back you.
Be sure to check spam and junk mail folders after a few days in case the response is blocked.

From my understanding (again from speaking with users) is an older release of Agile.NET may have been cracked, but the SecureTeam just recently released a new version 6.1.9.2, which I have not had any reports about being cracked.

[iantriestrading]

Hello iantriestrading,

Unfortunately, we cannot provide any assistance with using 3rd party obfuscators.

The SecureTeam has a smaller support team and can sometimes have a delay in their replies, but from what I've gathered from other users they do tend to get back you.
Be sure to check spam and junk mail folders after a few days in case the response is blocked.

From my understanding (again from speaking with users) is an older release of Agile.NET may have been cracked, but the SecureTeam just recently released a new version 6.1.9.2, which I have not had any reports about being cracked.

Cool thanks Chelsea. I just purchased Agile.net protection and am waiting for them to send/activate my license.