-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
Generate v20.1.4 files #26
Comments
@ericmschmidt I haven't been using DevExpress controls in a while, and I had the impression that for v20 they were going to add support for .NET Core 3 and also release NuGet packages for all their controls. Isn't that the case? |
It does look like they started supporting .NET Core 3.0 starting in v19.1 and started supporting .NET Core 3.1 (LTS) starting in v19.2.5, however it does still look like they support .NET Framework 4.5.2 as well. As for the NuGet packages yes they do have a NuGet feed but it appears they've grouped DLLs into packages, and don't have the 1-1 relationship that your scripts generate. I'm sure there are some scenarios where this makes sense but there are definitely some where it doesn't. But if you've moved away from the controls I'm guessing you don't really want to support generating the scripts moving forward either, is that accurate? |
Thanks for confirming @ericmschmidt. If there's value in having the 1:1 package relationship still, I'm happy to re-generate the nuget specs. I'll book some time next week to re-generate the nuget specs at least for the most recent couple versions of v19.* and v20.* and book some time in July to open-source a dotnet tool to generate the NuGet specs |
Yes that would still be handy for us our team at this point. Thank you for your continued support on this. |
@augustoproiete any update on this? |
Would you to generate the scripts to build the v20.1.4 packages? Or have you published the code you use to create these and I can modify and generate them?
The text was updated successfully, but these errors were encountered: