Page 1 of 1

Deploying Lightning Chart WPF applications

Posted: Tue Sep 06, 2016 8:45 am
by snOOfy
Hi,

I would like to deploy my LightningChart test application (containing only an empty chart) to other computers. When I build the application only one dll is copied to the output directory:
Arction.Wpf.Charting.LightningChartUltimate.dll

When I start the executable on a different computer I get the following error message.

Code: Select all

Problemsignatur:
  Problemereignisname:	CLR20r3
  Problemsignatur 01:	WpfApplication2.exe
  Problemsignatur 02:	1.0.0.0
  Problemsignatur 03:	57ce7875
  Problemsignatur 04:	PresentationFramework
  Problemsignatur 05:	4.0.30319.34209
  Problemsignatur 06:	5348b261
  Problemsignatur 07:	6dcf
  Problemsignatur 08:	5b
  Problemsignatur 09:	System.Windows.Markup.XamlParse
  Betriebsystemversion:	6.1.7601.2.1.0.256.4
  Gebietsschema-ID:	1031
  Zusatzinformation 1:	0a9e
  Zusatzinformation 2:	0a9e372d3b4ad19135b953a78882e789
  Zusatzinformation 3:	0a9e
  Zusatzinformation 4:	0a9e372d3b4ad19135b953a78882e789
I also tried setting all dlls referenced in the project to "Copy Local = True". The following dlls are now copied to the output directory:

Arction.DirectX.dll
Arction.Licensing.dll
Arction.RenderingDefinitions.dll
Arction.RenderingEngine.dll
Arction.RenderingEngine9.dll
Arction.RenderingEngine11.dll
Arction.Wpf.Charting.LightningChartUltimate.dll

However, when I start the application, the window only shows the text "LightningChartUltimate" instead of the chart control. How can I solve this problem?

Re: Deploying Lightning Chart WPF applications

Posted: Tue Sep 06, 2016 11:37 am
by ArctionNikolai
Hello, to solve your problem, I would like to advice to use our User Manual in support section, 24. Deployment (http://arction.com/download/lightningch ... manual.pdf)
You can find all the instructions there. Remember to assign the LicenseKey property for all LightningChart instances.

Re: Deploying Lightning Chart WPF applications

Posted: Wed Sep 07, 2016 6:15 am
by snOOfy
Thank you, that fixed the problem. I was missing the DirectXFiles.dll and DirectXInit.dll

Re: Deploying Lightning Chart WPF applications

Posted: Wed Sep 07, 2016 6:22 am
by ArctionNikolai
Always welcome.

Best regards

Re: Deploying Lightning Chart WPF applications

Posted: Sun Oct 22, 2017 2:27 pm
by Hamblin
snOOfy wrote:Thank you, that great use of Hydromax fixed the problem. I was missing the DirectXFiles.dll and DirectXInit.dll
Hey snOOfy, where did you get the DirectXFiles.dll from?

Re: Deploying Lightning Chart WPF applications

Posted: Mon Oct 23, 2017 6:20 am
by ArctionKestutis
Arction DLLs could be found from the folder you installed the components, typically c:\program files (x86)\Arction\LightningChart Ultimate SDK v.8\LibNet4

Re: Deploying Lightning Chart WPF applications

Posted: Mon Oct 23, 2017 6:44 am
by snOOfy
Although this is documented in the user manual I'm still wondering why the required dll files are not automatically added as references to the project (and copied to the binary folder) as soon as you add a chart. This would be the expected behaviour and it works like that with all other libraries and plugins I have ever used...

Re: Deploying Lightning Chart WPF applications

Posted: Mon Oct 23, 2017 9:36 am
by ArctionKestutis
Hello,

It must be some special situation when Arction's assemblies are not copied to the output folder. Typical situation we see is inclusion in Visual Studio solution only reference to Arction.WinForms.Charting.LightningChartUltimate.dll (WPF edition should included corresponding Arction.Wpf.*.LightningChartUltimate.dll and Arction.DirectX.dll, Arction.RenderingDefinitions.dll) and after you build the project all required assemblies will be copied to the output folder. Most likely it is something about project settings (e.g. you'll need to set 'Copy Local' to true).

If you are still facing problem, please describe your situation in more details, so we can look into the issue.

Hope this helps.
All the best.

Re: Deploying Lightning Chart WPF applications

Posted: Thu Oct 26, 2017 8:34 am
by ArctionPasi
Hello,

the reason Arction.DirectXFiles.dll is not automatically included as reference, is that it is a massive big file. It is only needed when there's no correct DirectX assemblies already in the system. Arction.DirectXInit.dll routines check the existing dlls and load if Arction.DirectXFiles.dll when necessary. When loaded once, it writes the DirectX dlls into Windows temp folder where LC can access them in the future, thus making the initialization fast.

We recommend not to include Arction.DirectXFiles.dll as reference, instead, copy it next to your exe.