dotnet core netcoreapp3.0

[virzak]

Hello,

Is there a plan to multitarget to netcoreapp3.0 as well?

[XceedBoucherS]

Hi, Yes, we plan to look at .net coreApp 3.0 as well. Thank you.

[miqm]

I created a fork of the project and compiled toolkit as .NET Core 3.0 Windows App and put it as nuget package: https://www.nuget.org/packages/MiqM.Xceed.Wpf.Toolkit.NETCore/

It's not created as multi-target, therefore it can be difficult to maintain but I'll be happy to create a pull request where we could work on improving it.

[virzak]

@miqm Thanks Mikolaj,

Would be awesome if DataGrid could be converted as well.

Unfortunately it was dropped it from the 3.5.0 release and is only available up to 3.4.0

[miqm]

@virzak I converted 3.4.0 tag to .NETCore 3.0 and pushed to nuget. However it's not tested heavily, I just went through the live demo app and from general perspective it seems to be working. Use responsibly 😉

[virzak]

@miqm Awesome, thanks!

[FroggieFrog]

@XceedBoucherS Any news on official support for .Net Core 3 in the non plus version?

[hmartinez82]

@virzak I converted 3.4.0 tag to .NETCore 3.0 and pushed to nuget. However it's not tested heavily, I just went through the live demo app and from general perspective it seems to be working. Use responsibly 😉

When do you intend to push your 3.5.0 release to Nuget? :)

[sa-he]

@XceedBoucherS what is the planned timeline for supporting netcore 3? I do not find any indication on that - not even for the plus edition?

[XceedBoucherS]

Hi, We are waiting for the official release of .NET Core 3 before making any announcements. Having the Toolkit on .NET Core 3 is important to us. Thank you for your patience.

[miqm]

@XceedBoucherS - just FYI, current preview8 of netcore 3.0 is considered by Microsoft as production ready, see https://docs.microsoft.com/en-us/dotnet/core/whats-new/dotnet-core-3-0#production-supported-preview

[Dirkster99]

@virzak @XceedBoucherS @miqm @FroggieFrog @hernancmartinez

We have just published a real open source version of the Toolkit and AvalonDock which target NetCore 3 based on Preview 8 and Net 4. Please consider these projects and NuGets if you are looking for NetCore 3 support in AvalonDock or the rest of the Toolkit:

• dotnetprojects/WpfExtendedToolkit
• Dirkster99/AvalonDock

[virzak]

@XceedBoucherS dotnetprojects/WpfExtendedToolkit is not .net core compatible. @miqm 's port is, but his project inherited some of the original bugs. Would love to collaborate on these projects, but not sure if I should submit PR to @miqm 's, to dotnetprojects/WpfExtendedToolkit or create my own fork. What are your thoughts guys?

[XceedBoucherS]

Hi virzak, Submitting your ideas, PR, bugs, comments on this site is always a good idea since this is the official WPF Toolkit OpenSource site. All your comments are read and classified in order to fix them. Your support is greatly appreciated. Thank you.

[Dirkster99]

@virzak I think @miqm and @jogibear9988 should work together on one version that supports both .Net Core and .Net. What do you guys think?

[jogibear9988]

I've a version that supports netcore ;-) And I'm happy of everyone who likes to join my github organisation and help with the projects

[virzak]

@Dirkster99 Yeah, absolutely. Sorry, I meant to tag you in previous post. Would be happy to help as well.

@jogibear9988 I'm so in!!!

@XceedBoucherS while I've thoroughly enjoyed using the wpftoolkit. I'm still at version 3.1 due to bugs and datagrid presence. What's xceed end game for the community toolkit?

Here are 3 main showstoppers for me:

• Removing controls (DataGrid)
• Open sourcing year-old, sometimes buggy, releases
• Having a frequency of 2 releases per year - that defeats the whole purpose of a PR, doesn't it?

Can you address these concerns?

[XceedBoucherS]

Hi all, Release dates happen when we think it's a good time and that the Plus users won't be penalized compared to the community users, since they pay to use the Toolkit and all its Plus features and fast support.

In 2019 only 1 version has been released, that is true, 7 and a half months ago, because of workload, but stay tuned, things will changed !!

We have re-think the concept of the Community version. From now one, many new community versions will be released and you won't have to wait for months/years before working in v3.9 ! Eventually the Community version and the Plus version will be at the same point !

We appreciate your feedback and we'll continue to improve the WPF Toolkit to make it the best Toolkit on the market !

Thank you.

[BOBJohnson]

I pulled the latest version of this fork today. I'm getting the following compiler warning:

Warning NU1603 MiqM.Xceed.Wpf.Toolkit.NETCore 3.4.0.1 depends on Microsoft.WindowsDesktop.App (>= 3.0.0-preview-27325-3) but Microsoft.WindowsDesktop.App 3.0.0-preview-27325-3 was not found. An approximate best match of Microsoft.WindowsDesktop.App 3.0.0-preview3-27504-2 was resolved.

[hmartinez82]

@BOBJohnson I think this is a issue with the version resolution logic that doesn't work when using -the preview-xxxx-y format. What really needs to be done is to update the version to .Net Core 3 final version.

[jogibear9988]

wich fork? mine? mine should use final core 3

[jogibear9988]

if there is still a error create a issue at my repo

[XceedBoucherS]

Hi, Happy to announce that v3.9 will include support of the Xceed Toolkit for .net core 3. Thank you.

[thomaslevesque]

Happy to announce that v3.9 will include support of the Xceed Toolkit for .net core 3.

Awesome! Any idea when it will be released?

[XceedBoucherS]

Hi, After deliberation, the Toolkit will jump from v3.8 to v4.0(with support for .net Core 3). This v4.0 version is scheduled for beginning of February 2020 for the Plus users.

The community users will get the v3.8 version at about the same time. v4.0 will be the next in line for them ! Thank you.

[jogibear9988]

I thought community and plus should be on the same line? If someone needs netcore support earlier, my forked Version at https://github.com/dotnetprojects/WpfExtendedToolkit already has support.

[XceedBoucherS]

Hi Yes, Community releases are not released faster in order to be at the same line as the Plus version. v3.6 was released in Sept 2019 v3.7 was released in Nov 2019 v3.8 is comming soon v4.0 will follow. This release contains the Official "Toolkit .Net Core 3 support".

Thank you.

[miqm]

I pulled the latest version of this fork today. I'm getting the following compiler warning:

Warning NU1603 MiqM.Xceed.Wpf.Toolkit.NETCore 3.4.0.1 depends on Microsoft.WindowsDesktop.App (>= 3.0.0-preview-27325-3) but Microsoft.WindowsDesktop.App 3.0.0-preview-27325-3 was not found. An approximate best match of Microsoft.WindowsDesktop.App 3.0.0-preview3-27504-2 was resolved.

This has been fixed and released to nuget.org as 3.4.0.4. I also published forked v3.5.1 built as netcoreapp3.0.

[rquackenbush]

I'm working with version 4.0.1 of this package and it only supports net4. Has the idea of supporting .net core been dropped?

[XceedBoucherS]

Hi, if you want the Toolkit for .NET Core, you need to buy the Plus version. This feature is only part of the Plus version of the Toolkit. You can try it for free for 45 days here : https://xceed.com/en/our-products/product/toolkit-plus-for-wpf Thank you

[thomaslevesque]

Hi, if you want the Toolkit for .NET Core, you need to buy the Plus version. This feature is only part of the Plus version of the Toolkit. You can try it for free for 45 days here : https://xceed.com/en/our-products/product/toolkit-plus-for-wpf Thank you

A few months ago you implied that .NET Core support would eventually be in the Community version as well. Has this changed? Without .NET Core support, the Community version is as good as dead...