The application in the link is a wrapper for the TWS API. Yes, less lines of code are required to make the TWS connection etc, but if you're already writing the code for the MS DLL, then is there much of a saving?

Having already written several interfaces for MS to TWS, it is no small feat to get a CHARTING application like MS to act (even remotely) like a TRADING application, getting it to do things it was never designed to do. The issues here are not making the connections, but taking actions when things go awry; and they WILL go awry. A long while ago there was a product called TradeBullet which could be used with MS, but the internal and external error handling, and the way that MS handles signals and data means the product was "unstable" and unsuitable for automated trading from MS; TradeBullet was a professionally developed product over a few years and they still couldn't deal with all the issues a CHARTING application has when trying to be a TRADING application. Several forum members at the time, tried and failed at their own implementations. My own implementations come with a list of exceptions and warnings longer than your arm!

Then there are the issues like: trading signals are being generated from one data feed but traded on another completely different set of price data (and often there IS a difference between the two). There are very few traders who are 100% prepared for automated trading, through MS or any other platform.


$0.02c


wabbit [:D]