+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
bug_report_small.png
Open Bug report MC-1969

Fix problem with reloading assemblies

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 modifying a referenced assembly, recompiling does not reload the assembly until you close MC.NET and open PLEditor.NET again. This is a major pain when working with external assemblies in PL.NET
To fix this MultiCharts should use a feature called Collectible Assemblies that comes in .NET Framework 4. It's something that has to be implemented at StudyServer level.

https://msdn.microsoft.com/en-us/library/dd554932(v=vs.100)

"Collectible assemblies are dynamic assemblies that can be unloaded without unloading the application domain in which they were created. All managed and unmanaged memory used by a collectible assembly and the types it contains can be reclaimed. Information such as the assembly name is removed from internal tables."
See related discussion: http://www.multicharts.com/discussion/viewtopic.php?t=48018

Steps to reproduce this issue

In Visual Studio create a Class Library project (Class A) and compile into a DLL
Add the DLL as reference assembly to a Study in PL.NET Editor and create an instance of Class A in the study.
Add study to a chart and keep MultiCharts process open
Modify project In VS to update the referenced assembly. You'll get an error that the assembly cannot be copied to output since it is locked by StudyServer.
To work around it you have to close all MultiCharts processes, recompile and open MultiCharts again. This is very time consuming and limiting for developers.

Comments (2)
#0
user-offline.png  Alex MultiCharts (Alex MultiCharts)
Nov 20, 2015 - 09:39
#0
user-offline.png  orad (orad)
Nov 20, 2015 - 19:08

I updated the repro steps. This issue exists regardless of the code editor you use and you can reproduce it with all versions of Visual Studio. Previously this was due to a limitation in the .NET AppDomain but now it's a bug because now .NET has a better way to handle unloading assemblies as said in the descriptions.

History
Issue basics
  • Type of issue
    Bug report
  • Category
    Usability
  • 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 (2)
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Reproducability
    Not determined
  • Severity
    Critical
Attachments (1)
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates