Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dotnet core netcoreapp3.0 #1428

Open
virzak opened this issue Jan 17, 2019 · 22 comments

Comments

@virzak
Copy link

@virzak virzak commented Jan 17, 2019

Hello,

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

@XceedBoucherS

This comment has been minimized.

Copy link
Collaborator

@XceedBoucherS XceedBoucherS commented Feb 5, 2019

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

@miqm

This comment has been minimized.

Copy link

@miqm miqm commented Mar 4, 2019

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

This comment has been minimized.

Copy link
Author

@virzak virzak commented Mar 4, 2019

@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

This comment has been minimized.

Copy link

@miqm miqm commented Mar 4, 2019

@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

This comment has been minimized.

Copy link
Author

@virzak virzak commented Mar 6, 2019

@miqm Awesome, thanks!

@FroggieFrog

This comment has been minimized.

Copy link

@FroggieFrog FroggieFrog commented May 29, 2019

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

@hernancmartinez

This comment has been minimized.

Copy link

@hernancmartinez hernancmartinez commented Jun 19, 2019

@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

This comment has been minimized.

Copy link

@sa-he sa-he commented Jun 27, 2019

@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

This comment has been minimized.

Copy link
Collaborator

@XceedBoucherS XceedBoucherS commented Aug 27, 2019

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

This comment has been minimized.

Copy link

@miqm miqm commented Aug 28, 2019

@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

This comment has been minimized.

Copy link

@Dirkster99 Dirkster99 commented Aug 31, 2019

@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:

@virzak

This comment has been minimized.

Copy link
Author

@virzak virzak commented Sep 25, 2019

@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

This comment has been minimized.

Copy link
Collaborator

@XceedBoucherS XceedBoucherS commented Sep 26, 2019

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

This comment has been minimized.

Copy link

@Dirkster99 Dirkster99 commented Sep 26, 2019

@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

This comment has been minimized.

Copy link

@jogibear9988 jogibear9988 commented Sep 26, 2019

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

This comment has been minimized.

Copy link
Author

@virzak virzak commented Sep 26, 2019

@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

This comment has been minimized.

Copy link
Collaborator

@XceedBoucherS XceedBoucherS commented Sep 26, 2019

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

This comment has been minimized.

Copy link

@BOBJohnson BOBJohnson commented Oct 16, 2019

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.

@hernancmartinez

This comment has been minimized.

Copy link

@hernancmartinez hernancmartinez commented Oct 16, 2019

@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

This comment has been minimized.

Copy link

@jogibear9988 jogibear9988 commented Oct 16, 2019

wich fork? mine? mine should use final core 3

@jogibear9988

This comment has been minimized.

Copy link

@jogibear9988 jogibear9988 commented Oct 16, 2019

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

@XceedBoucherS

This comment has been minimized.

Copy link
Collaborator

@XceedBoucherS XceedBoucherS commented Oct 17, 2019

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
9 participants
You can’t perform that action at this time.