Hi,

I want to control when my strategies are executed and write to a logfile whenever the srategies are executed. How can this achieved?

By manually adding a block of code to each of your strategies that appends a line to a log file.

Does it work the same way if the file is on the internet? Is it that easy?

As I see things, it would be easy to just drop the file to a local folder, and then:

1. Use a custom app to monitor file system changes in that folder. Hint: Use FileSystemWatcher to detect file changes

2. And then upload your changed file. Depending on where and how exactly you'd like to place that file "on the internet" (HTTP, FTP, Dropbox, Amazon S3... just to name a few), you'd need to figure out how to do it in C# or your favorite script language (PowerShell, AutoIt etc.)

Chances are, a script/utility might already exist for automatic uploading of changed files "to the internet".

I am looking for a direct way where
a) there is no other software involved
b) the user does not notice anything.

That's unrealistic.

Hmmm...was I understand it WLD has a connection to the internet. So there should be a way to read/write directly from a script, shouldn´t it?

Sure that's right. There also exists the possibility to use WL's built-in email notifications - which work for Alerts only i.e. not suitable when no alerts were triggered.

But it's pretty easy to notice (and remove) the watchdog code added to a strategy - unless it's compiled in a library and that library is safely obfuscated. If the user isn't tech savvy, still there are other, more subtle ways of "outing" like an added delay of strategy execution due to accessing an internet resource and/or an exception message popping up telling something like "destination host unreachable".

Anyway, the web upload solution is completely up to you.

QUOTE:
that library is safely obfuscated

What do you mean by that?

Is there a ChartScript Protector tool for WL6?

OIC, so without doing this anyone could read my dlls, right?

Think big: it's even possible to decompile an unobfuscated .NET assembly and have it served as a Visual Studio solution.

Okay, so I really need to obfuscate then.

I am a bit curious: how does Fidelity and MS123 protect their code/dlls?

A good example of question that will stay unanswered.

Because if I new that it would be much easier for me to read the code?
Just trying to understand obfuscating better.

Because nobody in the industry would help make a hacker the first step by unveiling any details about their protection scheme(s).