Hi,
I am trying to understand what the roadmap is for aspnetzero, abp.io and Blazor and React for SPA.
Netzero (and I assume abp.io) are really hard (so expensive) to upgrade, and we dont want to commit man years of work to something that will be redundant.
I have searched and read a lot of posts in this forum and on Git that promised that Blazor would be started over a year ago, but in abp.io first, eg after v1.0 was released.
However abp.io has a lot less functionality than netzero, but I see that React native is now included for mobile. Posts in here say that Blazor and React are NOT planned.
From what I see in the groups there are lots of people wanting Blazor. Us included.
So as a customer it's all very confusing if we should use abp.io and live with some shortage of functionality until it is caught up, or just use anetzero; or if abp.io will get Blazor first then we should lean that way, but what if anetzero is going to get Blazor or maybe React first..?
Having good information about the roadmap for abp.io and aspnetzero will help us make better roadmap decisions for our product set too.
Can I ask for some clear statement about the roadmap?
When do you plan for abp.io to have equivalent functionality as aspnetzero?
Will you be adding React, and/or Blazor SSD and WASM template to aspnetzero? and also to abp.io? and if so when will that be for each?
Many Thanks! Andrew
3 Answer(s)
-
0
Hi @andrewt,
For your final questions;
- ABP.IO team is adding new features in every version but some of the features exist in AspNet Zero and some others don't. It is hard for us to make an assumption becasue we are adding new fetures to AspNet Zero as well. So, I suggest you to look at the current features and make your decision according to current feature sets.
- For now both React and Blazor is not on AspNet Zero's Roadmap. It is on roadmap for ABP.IO. Blazor for ABP.IO is high priority but I assume it will take a few months at least. Since we are getting many requests for Blazor, We will re-evaluate Blazor for AspNet Zero and make an announcement if we decide to add it to AspNet Zero.
Thanks,
-
0
Thanks @ismcagdas for the update.
We think that our new applications based on commercial ABP.io will be easier to upgrade as new versions/fixes are released. Do you agree with that? That has been a major issue with aspnetzero.
If we focus on Abp.io can you add the Blazor items you'll support to the milestones so we have a better understanding of how you have prioritised it, and timeline?
https://github.com/abpframework/abp/milestones
There are so many of us that want Blazor support, particularly now that Preview 3 is out and RTM is scheduled mid May 2020.
Thanks!
Andrew
-
0
Hi,
For upgrading your solution, yes it is easier to get upgrades in ABP.IO if you use modules as NuGet and NPM packages. But, it will be similar if you use source code of modules in your project. For AspNet Zero, it is a bit harder but no so much. We have explained it here https://docs.aspnetzero.com/en/common/latest/Version-Updating.
You can follow Blazor issue for ABP.IO here.
