Open Closed

What are the upgrade plans for ABP.IO, .Net Core 3.0, and ASP ZERO? #6277


1
strix20 created

It is imperative that teams (like us) that are paying for perpetual licenses have adequate time to plan and prepare for the coming framework changes.


6 Answer(s)
  • 0
    ismcagdas created

    Hi @strix20

    Have you seen https://abp.io/blog/abp/Abp-vNext-Announcement before ? Probably it will answer most of your questions.

    For AspNet Zero, we will actively continue development and we will of courese support .NET Core 3.0 when it is released.

  • 0
    strix20 created

    I have, but I have not seen anything about what ASP Zero project plans to do with ABP.io.

    Presumably there will be a complete rewrite of the paid product, as well? What does that mean for those of us who have spent thousands on licenses for the current version?

    Or do you not plan to migrate Zero to abp.io, and continue to use the legacy boilerplate framework in perpetuity?

  • 0
    ismcagdas created

    Hi @strix20

    It is not %100 clear on our side but probably AspNet Zero will continue to use current AspNet Boilerplate. We will create something similar to AspNet Zero with abp.io as well. We are think of proving it for free or with a very small fee for existing customers.

    We will also continue to work on AspNet Boilerplate Framework.

  • 0
    richardghubert created

    Thanks, the .NET Core 3 support is important for diverse reasons, of course. Better docker-support being one of the "killer" reasons. We use AspNetZero with .NET-Core MVC JQuery (+ Syncfusion front) and also deploy into Docker. Can't wait for this:

    https://devblogs.microsoft.com/dotnet/using-net-and-docker-together-dockercon-2019-update/

  • 0
    bbakermmc created

    @richardghubert what do you think of syncfusion, have any screen shots of some grids/forms you have done? We use devextreme, and have used kendo in the past, but syncfusion was one we never looked at, it didnt seem to to as robust and adaptive as devextreme. But wondering what you think of it.

  • 0
    richardghubert created

    @bbakermmc All the frameworks you mention are good, so it comes down to some smaller differences. We used and looked at them as well as others and chose the trade-off-set provided by Syncfusion to be the best for our use cases. Some specific controls and graphic features were more important to us than others, e.g. theme management. We also had soft factors to consider like user support, breadth of platform, future support for Blazor.net.

    On the practical side, we first replaced the entire AspNetZero navigation and master layout UX with it and had no major problems doing that. Works fine. The rest ist just "standard" use of the Syncfusion components.