Hi, I just downloaded the latest UI for WPF (2019.3.1023) NuGet packages. Obviously the Wpf.NetCore packages have dependencies to SharpDX (>= 2.5.0) and SharpDX.Direct3D9 (>= 2.5.0). These are packages compiled for .NET Framework and NOT compatible with .NET Core 3.x
Hey guys, do you test your packages before deployment? Can I use the controls in my project anyway, should I remove the SharpDX references?
Regards
Heiko
3 Answers, 1 is accepted

Hello Heiko,
Indeed, there are warnings because the SharpDX dlls version (used by RadWebCam and RadChartView) is not build against .NET Core. However, the controls still work. If there are any runtime errors or other behavior that is stopping the controls from running on your side, can you share what exactly happens?
Also, currently we are working on replacing the SharpDX assemblies with their .NET Core version.
Regards,
Martin Ivanov
Progress Telerik
Martin (or other Progress representative):
Is your Telerik group planning to support SharpDX yourselves? Without having anybody support SharpDX, our Government customer will not accept our use of Telerik UI for WPF because it depends on SharpDX. Otherwise, is there any scenario in which Telerik (RadWebCam and other controls) do not depend on SharpDX?
We certainly prefer to continue using Telerik.
Thank you for your response.
Best regards,
Enrique Medina
We don't plan to take ownership on the SharpDX library. We use this only in two controls - RadCartesianChart for WPF and RadWebCam for WPF. The RadCartesianChart uses SharpDX to support additional rendering mode which is faster compared to the standard WPF rendering. In other words, you can use the chart without SharpDX. However, the RadWebCam cannot work without SharpDX, so this is where we cannot suggest an alternative.
Anyway, I am not sure why your government customer is concerned with the SharpDX library, but we use this for around 10 years now in the chart and couple of years in RadWebCam and we have almost no issues related to SharpDX. There is only a single error related to the library, which reproduces in a very niche scenario (constantly adding and removing multiple chart series fast at runtime). The library is pretty stable when it comes to the rendering features we use for the chart and the webcam.
If at some point in the future SharpDX is no longer suitable or if there is a proper alternative, we will research that and see if we can incorporate this in our product.
