Since I made a backup a few days ago and reinstalled multicharts, after restoring the backup I noticed that the Nuget packages were no longer taken into account. I assumed that all references would also be saved in the backup file if I had previously added them using the powerlanguage editor. But this doesn't seem to be the case, because I had to reinstall the NuGet packages in the solution and re-add the references.
You should be able to save the Nuget packages/DLLs and the reference in the backup files.
assembly references are not saved in backup
-
Polly MultiCharts
- Posts: 281
- Joined: Jul 20 2022
- Has thanked: 2 times
- Been thanked: 68 times
Hello HellGhostEvocatorX,
When you export signals that reference Nuget packages, the associated DLLs are also exported and after the Restore procedure restored into the folder C:\ProgramData\TS Support\MultiCharts.NET64\StudyServer\Techniques\ even if they have been removed in Visual Studio.
If you delete Nuget packages from the project using Visual Studio, you will need to manually re-add them. The Restore function in MultiCharts does not restore the packages and extensions in Visual Studio. It simply copies the DLL, which can be referenced by right-clicking on the code editor in the PowerLanguage .NET Editor → References.
When you export signals that reference Nuget packages, the associated DLLs are also exported and after the Restore procedure restored into the folder C:\ProgramData\TS Support\MultiCharts.NET64\StudyServer\Techniques\ even if they have been removed in Visual Studio.
If you delete Nuget packages from the project using Visual Studio, you will need to manually re-add them. The Restore function in MultiCharts does not restore the packages and extensions in Visual Studio. It simply copies the DLL, which can be referenced by right-clicking on the code editor in the PowerLanguage .NET Editor → References.
-
HellGhostEvocatorX
- Posts: 144
- Joined: Feb 10 2022
- Has thanked: 68 times
- Been thanked: 23 times
thanks for the reply. In any case, I had to reinstall a few Nuget packages, but I won't be able to understand what happened in the end, at least for a while 
So if the DLLs are copied along with it, that's a good thing.
But this brings me to another point: Isn't there a way to generally see which Nuget packages have already been referenced in Powerlanguage?
Currently I only see this when I go to the corresponding signal file, i.e. I would have to look through all signal files where a reference may have already been set. It would be nice if you didn't attach this to one or more "single" signal files but rather "globally".
I am aware that referencing applies globally.
It's just more about retrievability. In Visual Studio I can see the packages, but not whether they are referenced...
So if the DLLs are copied along with it, that's a good thing.
But this brings me to another point: Isn't there a way to generally see which Nuget packages have already been referenced in Powerlanguage?
Currently I only see this when I go to the corresponding signal file, i.e. I would have to look through all signal files where a reference may have already been set. It would be nice if you didn't attach this to one or more "single" signal files but rather "globally".
I am aware that referencing applies globally.
It's just more about retrievability. In Visual Studio I can see the packages, but not whether they are referenced...
-
Polly MultiCharts
- Posts: 281
- Joined: Jul 20 2022
- Has thanked: 2 times
- Been thanked: 68 times
HellGhostEvocatorX,
Which NuGet packages have already been referenced in PowerLanguage can be seen in Visual Studio by right-clicking on the project → Manage NuGet Packages.
Global references can be seen in the PL editor by right-clicking in the editor → References → Add Global References.
Local references to DLLs are saved only after exporting the signal from the archive. If the signal has not been imported, local references are not added.
Which NuGet packages have already been referenced in PowerLanguage can be seen in Visual Studio by right-clicking on the project → Manage NuGet Packages.
Global references can be seen in the PL editor by right-clicking in the editor → References → Add Global References.
Local references to DLLs are saved only after exporting the signal from the archive. If the signal has not been imported, local references are not added.