MultiCharts Easter Sale has jumped in! Up to 50% off Explore offers
+1 888 340 6572
MultiCharts Project Management
previous_open_issue.png
Go to the previous open issue
previous_issue.png
Go to the previous issue (open or closed)
star_faded.png
Please log in to bookmark issues
feature_request_small.png
Open Feature request MC-1634

Why not merging Multicharts and Multicharts.NET?

action_vote_minus_faded.png
16
Votes
action_vote_plus_faded.png
next_issue.png
Go to the next issue (open or closed)
next_open_issue.png
Go to the next open issue
Description

Hi,
Regular Multicharts offers extensive library of indicators and strategies through several forums which is not the case of MC.NET. On the other side, MC.NET allow programmers to create even more advanced indicators, strategies and to do things that would not be possible with regular MC.
Some would say that each one has its advantages but for me, they both have their limitations.
I think that you would really get an edge over competition if you would merge both MC into one. I don't think most people would buy 2 licences but I think more traders would choose Multicharts over other platforms if they get more for their money.

Steps to reproduce this issue

Nothing to reproduce

Comments (6)
#0
user-offline.png  GB (Id2)
Apr 03, 2014 - 16:06

Excellent Idea,
I guess Multicharts has internal data so that they can calculate whether this makes sense in econmic/financial perspective.
Would be nice to know from MC whether this is an option for them.

#0
user-offline.png  JoshM (Jura)
Apr 11, 2014 - 08:24

If users get more for their money, MC will get less money for their work.
The current versions for MC are fine; non-programmers can go with PowerLanguage, and more experienced programmers can go with MC .NET. This serving of target audiences work much better than providing a bloating one-size-fits-all approach.

#0
user-offline.png  JoshM (Jura)
Apr 11, 2014 - 08:24

If users get more for their money, MC will get less money for their work.
The current versions for MC are fine; non-programmers can go with PowerLanguage, and more experienced programmers can go with MC .NET. This serving of target audiences work much better than providing a bloating one-size-fits-all approach.

#0
user-offline.png  YanickB (YanickB)
Apr 11, 2014 - 15:18

I disagree with JoshM. I don't think Multicharts would make less money in offering both programming language for 1 license. In fact, I think they would make more...
The equation is simple: Considering that 99% of both products is the same, most traders won't buy 2 licences(1 MC + 1MC.NET). No possible gain there. But NEW traders looking for the best platform will immediately see the advantage over competition.
Maybe there would be an 'in-between' solution: paying a little more to have both.
I don't know which license you have, but for my part, with MC.NET, I'm realizing that quite often I would save time not having to re-program something already made in easy language and not available in .NET. On the other side, I still appreciate MC.NET for things I could'nt do with regular MC. 

#0
user-offline.png  MAtricks (MAtricks)
May 29, 2014 - 17:49

Creating functions in C# that can run in Power language would be an amazing thing :) I agree that these should be one platform. Maybe we pay the extra license cost to have the ability to use an additional programming language instead of an entire different platform??

#0
user-offline.png  GB (Id2)
Oct 10, 2015 - 05:20

The best of both world if mix together. More people will buy at least 2 licenses like myself if this happen. One for development and 1 for production eventhough i know there is feature you can develop if you disconnect to internet but still have limitation but most traders willing to invest more due to best platform and more vendor will come to create indicators for MC. I really support this feature to have C# able to support limitation of easylanguage and VICE VERSA.

History
Issue basics
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (2)
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
  • Severity
    Normal
Attachments (0)
There is nothing attached to this issue
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates