+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 Feature request MC-1170

Visual Studio Intellisense docs not published.

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

When editing C# code in PLStudies2010.sln in Visual Studio, Intellisense does not show API documentation for any of multicharts assembly references (included PL*.dll files). This is because XML Docs are not included with the reference assemblies in:
%ProgramData%\TS Support\MultiCharts .NET64\StudyServer\Techniques\CS
These XML Docs should be the same XML files used to generate the MC's .NET API documentation.

Steps to reproduce this issue
  • Open PLStudies2010.sln in visual studio
  • Try auto complete feature for any object under the MultiCharts namespace.
    ==== EXPECTED ====
    Should see documentation for each object or member
    ==== ACTUAL ====
    There's no intellisense documentation for MC objects
Comments (2)
user-offline.png  orad (orad)
15 de nov de 2012 - 03:03

Maybe you can make XML docs available for download in a zip file? Having access to the docs in Visual Studio is much more convenient than browing/searching the .CHM file.

user-offline.png  orad (orad)
27 de dic de 2014 - 11:45

This issue has been fixed. You may close the issue.

Issue basics
  • Type of issue
    Feature request
  • Category
  • Targeted for
    MultiCharts 9.0 (RELEASED)
  • Status
    Partially Implemented
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (2)
People involved
  • Posted by
    user-offline.png  orad (orad)
  • Owned by
    Not owned by anyone
  • Assigned to
    Not assigned to anyone
  • Subscribers
    2 subscriber(s)
    Click here to show the list of subscribers
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
  • Severity
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