Closed sebkraemer closed 3 months ago
Apparently, issue #100 already talks about modernizing HelixToolkit.Wpf.Input
.
You need to use Helixtoolkit.core.wpf for dot net 6 above.
Thank you for the quick reply and sorry for the late feedback. That worked. I was somehow confused by the "core" in the name.
Version: 2.25.0
Package: HelixToolkit.Wpf
Issue: I'm seeking guidance/feedback and community support for migrating HelixToolkit.Wpf to .NET 8.0. The compiler issues the following:
Reproduce Steps:
I am evaluating the use of Helix-Toolkit and the HelixToolkit.Wpf or possibly SharpDX.Wpf components for an upcoming project. It shall be based on WPF, and I want to start the project based on .net8. I noticed that the existing nuget package is only built for .net framework 4.6.
The initial tests and migration steps for HelixToolkit.Wpf were successful, however I got the aforementioned compiler warning. The successful part is limited to the wpf component only, not I also encountered significant challenges when trying to update other dependent projects within the same solution, esp. tests and examples projects. The samples use the
propertytools.wpf
component which is .net framework based and apparently not really maintained any more. Wpf.Input complains withCannot add reference 'TDx.TDxInput.dll' to project 'HelixToolkit.Wpf.Input' because their target frameworks are incompatible.
I'm now wondering if going forward with helixtoolkit solution is an option. I would appreciate any insights, shared experiences, or advice on handling this situation, especially:
Thank you for any guidance you can provide!