+1 888 340 6572
MultiCharts Project Management
Go to the previous open issue
Go to the previous issue (open or closed)
Please log in to bookmark issues
Open Bug report MC-2373

Multicharts.NET latest: using System.Windows.Forms.DataVisualization.Charting; fails in PowerLanguage Editor but compilation succeeds in Visual Studio

Go to the next issue (open or closed)
Go to the next open issue

I was surprised to see a situation (as in the attached) where I can Build successfully the solution in VStudio but it errors out in PowerLanguage.NET Editor ... this is a bit strange, usually the two are consistent in the errors they output.

Steps to reproduce this issue

Add a:

using System.Windows.Forms.DataVisualization.Charting;

statement in your Strategy code. Vistual Studio will Build successfully and PowerLanguage.NET Editor will complain.

Comments (1)
user-offline.png  MultiCharts Support (MultiCharts)
Nov 14, 2017 - 10:16
Hello Andb,

Please make sure you have added System.Windows.Forms.DataVisualization.dll to the References list of PowerLanguage .NET Editor window. All references should be added through PowerLanguage .Net Editor only. You need to open any study in the PowerLanguage .Net editor window and right click on the source code->References. If you want to see the references in the Visual Studio – you need to restart both PowerLanguage. Net Editor and Visual Studio so that Visual Studio can pick up the references.
  •   icon_status.pngStatus changed: Under Review => Not a bug
Issue basics
  • Type of issue
    Bug report
  • Category
    Not determined
  • Targeted for
    Not determined
  • Status
    Not a bug
  • Priority
    Not determined
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (0)
There are no items
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Reproducability
    Not determined
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