WL, Hi, I need an encryption procedure available in Wealth Lab Pro that masks files on the computer by only allowing the computer to import a certain file marked as such and that the file is made unreadable by the encryption.

Please add a procedure that allows you to save and export files as import only which is the equivalent of read only and does not show the editor when you open the strategy and that's all you have to do.

Your output is an encrypted unreadable XML file marked as IMPORT ONLY, and when you import it, it can only be done once, and deletes the file from the computer.

This is available since day one. Compiled Strategy libraries do not show their code in the Editor. To further protect your intellectual property from prying eyes of those capable to reverse engineer .NET code, an obfuscator tool is required. Search for ".net obfuscator" and you shall find many packages, commercial and free.

More information:

Sharing a compiled version of a script?
Confidentiality/Encryption of Trading Methodology

Eugene, this doesn't help. It will still show the code if you open it in Wealth Lab Pro is the point.

Beau, you missed the point of what I just said. Hiding code of XML Strategies is pointless and will not be considered. At the risk of repeating, what you need is a "compiled Strategy library". The Editor isn't even shown when you open a Strategy from it.

To see how it works by example, install this extension, restart WLP, then at the bottom of the list in "Open Strategy" dialog you'll see a collection of outdated scripts grouped under "ActiveTrader Strategy Pack" folder. Try to open any of them and feel the difference:

ActiveTrader Strategy Pack

This tutorial contains a wakthrough on building Strategy libraries (requires an IDE like Visual Studio):

Programming | How can I debug my trading strategies in Wealth-Lab? (steps #1-10)

However, the protection it gives isn't sufficient from reverse engineering. Strategy code can still be decompiled by programmers and power users with dedicated tools. So re-read my post #2 for hint on obfuscation. This step is required if you wish to enhance your code protection.