Thanks for your response. Sorry, I'm not sure if I was clear with my question, or maybe I don't completely understand. I only have 2.1 installed on my machine, but I still have the 1.6 dlls being referenced. So I have two DLLs, both named Abt.Controls.SciChart.Wpf.dll, one of them is 1.6, the other is 2.1. Each of my 2 projects references a different version. My projects however, are part of the same codebase, so compile to the same output directory. Due to the DLLs having the same name, but different version, I can only ever have one version of the Abt.Controls.SciChart.Wpf.dll in my output directory. I tried renaming the DLLs by suffixing the version number (e.g. Abt.Controls.SciChart.Wpf.1.6.dll and Abt.Controls.SciChart.Wpf.2.1.dll), but this does not work, as the projects still end up trying to locate the Abt.Controls.SciChart.Wpf.dll at runtime. I have other third party DLLs that include a version number in their DLLs, so I can therefore reference different versions without having to completely upgrade to a new version in one big bang. I was wondering if there was a way I could do this with SciChart. Cheers
Aha, I see. Good idea. Well currently the Dlls are named the same, but installed to separate directories. I would suggest that if you want to do an upgrade while keeping your old source intact, you should create a copy of your working directory (e.g. if using SVN or Git, checkout to a new directory, or create a branch) and perform the upgrade (referencing new DLL from new installation folder) in the new working dir. Then, once you are happy, commit to your repository and if necessary merge. That's how I would do it, although I'll add to our feature board the idea of having version numbers in DLLs. We do release pretty often (every few weeks) so a new version number might annoy some people, but might help others. Thanks for the suggestion! - Andrew- It definitely would be helpful in my scenario. I actually have a number of projects referencing 1.6, and only wanted to upgrade a few to 2.1 and use multiple versions simultaneously. I know it would be preferable to upgrade everything to 2.1, but my main issue was with the refactoring done between 1.x and 2.x. This means that I need to upgrade every single project to use 2.1 and fix all the errors created due to the refactoring. This scenario would be preferable, but I have time restrictions unfortunately. Thanks for your help!
- Update: as it happens we're writing a performance test-suite, to test the performance of SciChart across multiple scenarios and versions. We've run into exactly the problem you're describing - different versions result in a FileNotFound exeption. The reason is that the DLL AssemblyName (internal to the DLL) is the same across versions, and visual studio can't pick them up as separate, despite different version numbers. So, to resolve the problem we're going to have to release Dlls with version number in the filename and assembly name. That will help us and hopefully help you too. Thanks for reporting! Best regards, Andrew
- Ah great news. Yes, that is exactly my issue and will help in future upgrades. Cheers
Is this really fixed? I am having similar trouble. An existing project is using version 5.1 for 3D chart and I need to use the latest 6.5 version for the 2D chart. And build just fails.- Good morning, times have changed since this question was asked and now I’d recommend using nuget to reference the packages for different scichart versions. Be advised the v6 licensing mechanism is completely different from v5, you’ll need to use the cross platform licensing wizard to start trials and activate licenses for v6. This can be downloaded and installed without the main installer https://www.scichart.com/cross-platform-licensing-wizard/
1
Queens Award for Innovation
Proud winners of the Queens Award for Innovation, 2019. Awarded on account of our innovative graphics engine which underpins the SciChart library and enables our world-beating charting performance
National Business Awards
Highly Commended for Lloyds National Business Awards, 2019. Awarded on account of our innovative graphics engine and impressive customer base
Reviews
SciChart has received hundreds of verified, 3rd party reviews
Try SciChart Today
Start a trial and discover why we are the choice
of demanding developers worldwide