Base solution for your next web application
Open Closed

Roadmap/ Future of aspnetboilerplate #2017


User avatar
0
soulmate created

Hey Guys,

I hope this forum fits the topic ;-)

First of all I want to thank you again for providing this great framework. I choose the framework because one the one hand I feel that it is stable enough to build my application upon on this and on the other hand it well documented.

However, looking from a ressource based point of view it must be really hard for you to maintain aspnetzero for all the flavors (ASP.NET MVC 5.x, ASP.NET Core 1.x, AngularJS) and adding useful features to it. So I want to start a small discussion about the roadmap or the future of your nice framework.

From my point of view (and I think others who buy the licencse will have the same opinion) I need a stable framework with a solid ecosystem. This includes for me:

  • Logging
  • JobScheduler
  • Localization
  • Caching
  • Settings
  • Auditing
  • Authentification & Authorization

For me this framework should be based on the latest technolgoy and should be upgraded frequently so that my team can focus on building line of business applications without the hassle to maintain nuget packages or reinventing wheels. This will allow junior/ mid developers to speed up with software development.

After .NET Core is now out for some month I compared the features that come with aspnetzero and that are included in .NET core. As far as I can see .NET core has a lot of features like DI, Localization, Logging, Caching, etc included and maintained by a huge community. From your perspective it should make sense to use this features and build advanced features/ easier handling for aspnetboilerplate on top of this, right?

Would it be an idea to skip the support of ASP.NET MVC 5.x within the next year and only focus on .NET Core? From an architect perspective you then would be much faster/ better in providing updates and new features.

Maybe it would make also sense to introduce a "user voice" feature to your community in order to ask the people who use the framework which component should be added to the framework?

Best regards


2 Answer(s)
  • User Avatar
    0
    hikalkan created
    Support Team

    Hi,

    Thank you for your comments. We think similar.

    We are currently working on Angular 2 UI and hopefully finish it in this year (in ~4-5 weeks). Then we will mostly focus on AspNet Core and Angular 2 versions, not immediately but by the time. Because AspNet Zero is mainly to start to new projects, so we should provide the most fresh technology stack.

    ASP.NET Core is more powerfull then MVC 5.x and has many features built-in, as you said. We first integrated to it's Dependency Injection and Logging systems. You can already use AspNet Core's all features in AspNet Zero and ABP framework. But, by the time we will implement it's style much more. For example, it introduces resource based authorization which we will work in the future.

    We released ABP 1.0 just a few weeks ago and we are planning new features based on community feedback. We don't have a "user's voice" page but I think Github is more suitable for it. Just create an issue on Github, we label it as "feature request" and discuss it.

    Thanks, Have a nice day.

  • User Avatar
    0
    soulmate created

    That sounds great to me! Thank you once again for your great work