+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-1170

Visual Studio Intellisense docs not published.

action_vote_minus_faded.png
3
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

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)
#0
user-offline.png  orad (orad)
Nov 14, 2012 - 18: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.

#0
user-offline.png  orad (orad)
Dec 27, 2014 - 02:45

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

History
Issue basics
  • Type of issue
    Feature request
  • Category
    Usability
  • 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
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