I think some other issue is causing this, since I never had issues importing data in the trail versions for MultiCharts or MultiCharts .NET. Have you checked it with the steps listed in the importing datawiki article?
What MC does NOT support or does not support very well...
1/ Time and sale or T&S. This is biggy for me and I am keep getting the same very, very, very annoying answer... like they will never want to implement this feature and they hope it will fade away, I don't get it...
2/ Switching time or instrument on a chart is a pain compare to NT. /especially time is great on NT/
3/ If you want to do anything with "InsideAsk" or InsideBid" forget that in replay since MC is not recording "status line" data.
4/ DOM is far from as good as NT's DOM... it is workable though especially if you are a discretionary trader and if you don't mind to place your orders and stops and targets manually.
5/ Adding instruments does requires some learning curve compare to NT.
Some good words regards to MC however:
1/ I have both MC and NT. I find MC charting more "polished" compare to NT.
2/ IB connector is written smarter by MC than NT guys. Faster no annoying IB messages...
3/ 64 bit is rock solid - well so is NT 7 64 bit - however I've found the workspace management more convenient using MC and also many, many chart windows can be open and do stuff in the same time on a few workspaces using an i5 Dell laptop with 6GB memory which is not a really high end workstation.
4/ Support is great!!! they connect remotely even if almost no need for it and if you have a coding question they will look at as well.
Summary, I am using mostly NT for trading however just to keep my MC platform well oiled I also run some of my things on MC.
I've reported this issue on August 24th to MultiCharts Support. An hour later I received an email saying that my issue had been forwarded to the engineers. Later that day, I received another email saying that the issue might take some more time (which I already said would be okay, since it's not a critical issue).
On August 27th I received an update email from the same representative (to keep me updated), and on August 30th I received another email saying the issue had been identified and added to the fix list (within 5 business days).
MultiCharts .NET 8.1 Beta 1 was released September 25th, and the change log reads:
As you can imagine, I'm very happy with how quickly this issue was identified and solved. I also liked it that I also had to send them one email and they took it from there - they were knowledgeable and I didn't have to "prove" to them there might be an issue here. They just looked into it.
I also know, from past experience working with MultiCharts Support, that I've could asked for a hotfix after the issue was identified. I didn't do that since this issue was not that critical and there's no point in wasting their time on something that's not critical to me.
I thought I should share my experience here because most of the time these things aren't observable from the outside, like for example, the lack of a T&S is.
Disclaimer: I wasn't asked to report my experience here by MultiCharts and don't have any financial incentive to do so. I just thought they should also get some recognition for their great service.
The following 4 users say Thank You to Jura for this post:
I see you are a Ninja user as well as a MultiChart.Net user. As I understand it both use C# as their language of choice. How difficult would you say it will be to port an indicator (or system) between the two?