SciChart® the market leader in Fast WPF Charts, WPF 3D Charts, and now iOS Charting & Android Chart Components
Should we remove the Version Number from the SciChart DLL?
On Friday we sent out a mailshot with a 1-question survey for our user base:
Q: Should we remove the Version Number from the SciChart DLL Filename?
The results are not as clear-cut as you might think! Here are the results as of Sunday 15th June.
We are preparing to release v3.1 of SciChart, so we need to know fairly soon what you think.
- Should the DLL (for this, and all subsequent releases) be named Abt.Controls.SciChart.Wpf.dll? If so vote Yes!
- Should the DLL for this release be named Abt.Controls.SciChart.Wpf.3.1.dll? If so vote No!
If you’re still not clear what we’re talking about, see below!
What are the pros/cons?
- Well, keeping a version number in filename leads to easy identification of File Version, no possibility of referencing an incorrect version / file clash and ability to have different parts of an application referencing different version(s) of SciChart.
- Removing a version number leads to easier upgrades (drop in replacement, no need to re-reference in your Visual Studio projects) and possibility of starting a NuGet feed with automatic updates in the future.
We want to remove it. If you want us to keep it, we need a good reason, so use the comments!
If you haven’t voted yet, let us know soon. The survey is here: https://www.surveymonkey.com/
Best regards,
[SciChart HQ]
Licensing SciChart iOS or Android
2 Comments
Someone said in the survey
>> “It’s not very important, though. I can always copy and rename the DLL if I want to.”
Aha but you can’t! It’s a strong named DLL. This is why its such a contentious issue. Either we release with version number in, or we don’t
Also whoever said
>> i have no problems with version number and my private NuGet private source for scichart package
Please contact me 🙂
It sounds like the answer is to have maybe to have both a signed and unsigned package, then those who want the versions can rename the dlls, or possibly build with one with versions and one without.
It’s a pain for us. We have between 5-7 different projects that reference the SciChart dll. Every upgrade we have to go remove and re-add the reference( a pain in VS), or go search through csproj files and replace it.
It’s definitely an interruption to development to have to upgrade SciChart right now.