wpftoolkit
wpftoolkit copied to clipboard
xceedsoftware
Missing Xceed.Wpf.DataGrid.dll in nuget v3.5
The latest Release (v.3.5.0) has no Xceed.Wpf.DataGrid-Assembly in the nuget package. (https://www.nuget.org/packages/Extended.Wpf.Toolkit/) That's a breaking change for my projects.
However the source code still has the Xceed.Wpf.DataGrid-Project.
Is this intended ?
Yeah. As the release notes say: The DataGrid control is now part of the Toolkit Plus for WPF. :-1:
Thanks. One more reason to remove xceed toolkit as a dependency for my project. I really like the xceed toolkit for my projects in the past but unfortunately I will not use it anymore. My projects are normally free and open source for people to use and modify and cannot afford to pay for the full professional release.
@Hyrules what alternatives are there?
With Xaml Islands one alternative I know of is: https://github.com/windows-toolkit/WindowsCommunityToolkit/tree/master/Microsoft.Toolkit.Uwp.UI.Controls.DataGrid
@virzak At the moment I don't know if there are any worth using or mentioning (The same goes for the property grid) but MahApp has one datagrid https://mahapps.com/controls/datagrid.html . I have used their controls in the past and are working pretty well.
The code was released under the MS-PL license. It would be possible to fork the code from the 3.3 release and release a separate NuGet.
This is a shockingly irresponsible breaking change. The removal of DataGrid should be reverted and a version 3.5.1 should be released to resolve the issue. Afterwards, Xceed should continue to support DataGrid in the "free" repository until they can establish a migration path - whether that be to a new control they create or a control produced elsewhere that is roughly compatible.
@AaronWrightAdm the way to look at it is: they are a private business and can do whatever they want.
Having said that, even if they brought the data grid back in 3.5.1 you would be stuck with .Net Framework for a few more years. Even their latest DataGrid is built on the old EF6. They aren't exactly in a rush to migrate to .net core either. So from my perspective, it is best to replace their DataGrid with something truly open source.
@virzak I understand that what "should be" and what "is" are two different things, especially when it comes to businesses. That said, I outlined what they "should" do in order to demonstrate a responsible attitude toward those using their libraries.
They're free to completely ignore it. However, I believe it would set a precedent that could repel people from their community and impact their bottom line in the long run. If DataGrid is removed from 3.5.0, then perhaps PropertyGrid or AvalonDock are next. Or perhaps they'll decide to move a control from the "Plus Edition" to the "Business Suite" in the same manner.
Decisions like this break trust in a product and its company, and make people think twice about starting or continuing business with said company.
@AaronWrightAdm Certainly agree with you on the trust issue. In fact I didn't only lost trust in xceed, but in closed source solutions altogether.
Lets just hope they remove AvalonDock soon from the open source release since the open source quality is not useful anyways - I see things like this as a chance to develope it as a true open source project as it used to be when AvalonDock was maintained by the original author.
This is indeed troubling. I choose this library because of the DataGrid control. I use a few more controls, such as the dock, and property grid as well, but the DataGrid was what sold me. I've already looked at alternatives when I evaluated it, none of them are close to feature parity and function. I don't know what to do now.
Also the old versions of the toolkit were removed from NuGet.org!
I today also upgraded our nuget dependencies and by this upgraded the Extended.Wpf.Toolkit package from 3.3.0 to 3.5.0. With this upgrade suddenly various projects do not compile anymore as the DataGridControl seems not to be part of it anymore. After checking the very poorly communicated release notes and readme changes in GitHub and crawling the issues, I saw that for the DataGrid was updated to be part of the Plus Edition and is not free anymore. Fair enough, its not free anymore for the future and Xceed is in the end a business company and not a non-profit organization.
Donating this toolkit to the public for free (including the datagrid) was a nice move from Xveed but deleting even the old nuget package versions from nuget.org would be quite a rude move against the community. I really hope that this was an accident and not an active decision. I mean: The binary releases on github are still available, then why remove the NuGet packages and break potentially all builds in the market using the old versions unless the package is still in the local cache, or NuGet.org still serves it for a while.
In worst case I would recommend that the community forks out the 3.4 version and publishes the data grid based on this state independent from Xceed. At the end it was published once as open source under the MS-PL and AFAIK the OSS license of this old source code state cannot simply be revoked.
Someone else has already pushed a 'new' 3.4 version to NuGet.
Please check if it works for you and report back in the thread if you can work with it...
@Danielku15 The packages are still on NuGet, just unlisted (you cannot remove a package from NuGet AFAIK). For example, the version 3.4.0: https://www.nuget.org/packages/Extended.Wpf.Toolkit/3.4.0/.
But yeah, I agree that unlisting packages just because the DataGrid is no longer free is not a good move.
@k94ll13nn3 Good to hear that they cannot be removed. I didn't know that nuget.org only allows "unlisting". My fear was that they were deleted by Xceed and nuget.org will only serve the packages for some more time until they actually delete it.
if you guys feel like compiling the 3.5 with the datagrid check my repo. I have integrated the datagrid to my repo version of the 3.5. I could add a compiled version to my release if needed.
I did similar. I grabbed the github source from late Feb, and just pulled it into my regular source, linking against the nuget version of this library.
It's exactly the same here. We updated the NuGet packages of our applications, and it was frightening to see that the DataGrid was simply removed. That's really not very nice, because it was already slimmed down anyway, unlike the full version. But I personally don't understand that it was completely removed.
I'll give you a hint it start with Mo and end in ney... I had to rollback to 3.4.0 now because of a bug in the latest property grid. I'm getting tired of this.
+1 to removing DataGrid with minimal explanation or notification being not nice, and +1 to delisting 3.4.0 from Nuget being a jerk move.
I could only speculate about Xceed needing to find ways to boost revenue, or cut support costs or something, but this seems like a disaster for their reputation: steward a useful open source control for years, gaining wide spread good will and name recognition with the community, then one day multiply all that good will by minus one, by pulling the rug out from all the many happy people, turning them into many angry people who will spread by word of mouth that Xceed is a jerk company that will happily betray their users trust. Bravo.
(Microsoft for example will discontinue open source projects, fair enough, but then point out "but this person is forking and continuing maintenance, so check that out." In contrast, Xceed DELETES 3.4.0 from Nuget listing, which seems unprofessional and manipulative.)
Xceed, am I missing something? I mean it's your company, but if you accidentally created a lose-lose scenario, maybe there's a chance you can still fix it.
jogibear9988 has published a real open source version of the Toolkit which targets NetCore 3 based on Preview 8 and Net 4. The Toolkit still contains the the DataGrid. So, please check it out and let us know if you have trouble using it.
Extended WPF Toolkit
AvalonDock
I used the Nuget Package Manager in VS 2019 to install dotnetprojects/WpfExtendedToolkit 4.6.78, and I don't see the DataGrid in the Object Browser. Has anyone tried this? Am I missing something?
You can install v3.4.0 via Package Manager console though. DataGridControl still in there.
Install-Package Extended.Wpf.Toolkit -Version 3.4.0
Infragistics pulled the same trick with their Express DataGrid but they pulled the free version probably a decade ago.
But in their defence, if I was producing a commercial tool used in the UI of Visual Studio I probably wouldn't be giving it away for free either.
If anyone is interested, the latest open source version of the DataGrid has been forked here. The nuget package is here.
It is .Net Core 3 compatible.
If anyone is interested, the latest open source version of the DataGrid has been forked here. The nuget package is here.
It is .Net Core 3 compatible.
Hi, I am just starting to use WPF and C#. I am interested to test the datagrid by exceed (non commerical). How do I use the links you have mentioned virzak? Do I download it and build the solution to produce the .dll?
