Any update on this?
Has there been any decision on this? We are looking at options to migrate a product on aspnetzero to blazor/Maui, and dont really want to go to ABP.io.
We are looking to build an app using Xamarin so field users can update work from their tablet, ie a subset of the data and options held in aspnetzero backend.
They will be in locations where they may not have data connection sometimes, but need to still be able to update forms and job data.
Then when they come into coverage, they will have those updates sent back to the server, and also pull down new data/jobs.
This is a very normal situation and although there is not much support for this scenario in the aspnetzero template, what is the best approach components/tools for this?
Is the provided Xamarin demo app a good starting point, or is it just better to start fresh?
We are looking at client reporting options and would appreciate peoples experience. We would prefer to use Telerik as we already have licences and it's one less tool to learn, but it appears there are issues integrating it with aspnetzero.
https://support.aspnetzero.com/QA/Questions/8424#answer-7b90f3ec-aa75-faec-0a26-39f38a201b2d
What have others used and found to work reliably with aspnetzero?
Hi, we are (still...) upgrading a product from 6 to 8.x.
The new metronic theme is totally incompatible with the old one and so we will now have to re-do our styling etc.
What is the best practice for the "theme/UI" customizations we make in v8.x so it is easier to upgrade in future? eg when .net5 comes out.
Andrew
Hi,
Awesome to see so much activity to improve aspnetzero with release of v8.8!
However I'd really like to vote for an easier upgrade route.
So far this year there have been 8! releases. that includes hundreds of bug fixes, enhancements and new features. That's great!, but....
We are currently upgrading from v6 and it has taken about 25 man days so far including planning and development. i expect it will be another 10-20 including testing just to get to square one.
We used the two repositories process you suggested and have senior devs on this.
During this time we have had to lock out any bug fixes/enhancements which is a risk or means we have to again merge any fixes made during the upgrade.
We have a number of customizations because the functionality at the time wasn't available.
Like most customers we are building products which we have to constantly improve. We also cant ignore the underlying changes/improvements MS are making to Core.
At this rate of updates there will be close to 20 netzero release this year. Some will be to include LTS of .net core so we need to keep up.
Even if we only upgrade every 3rd release and get better at it and it takes 10 days migrate and test, that is over 60 man days just doing upgrades... Not to mention lost dev time, or cost to merge changes while upgrades take place.
Then multiply it if you have more than one product...
If we leave it longer I fear we will have even more time to upgrade each time. It is an un necessary distraction.
For one of our products in v5.5 I am thinking we should just rewrite it rather than attempt to upgrade. Should we use aspnetzero if we factor in this ongoing upgrade cost?
I think it would be a big advantage to the product to have a set of tools to significantly speed up the upgrade process.
Dont stop doing great work improving aspnetzero and abp.io but now the products are maturing it would be great to have a better approach to upgrades and cost of ownership.
Thanks.
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
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
Hi, Has there been any progress (by anyone) on a Blazor template for either ABP.IO or Aspnetzero? We have an SPA we need to start and don't really want to use Angular and then re do it later.
@gjubber - Could you update your experience and any steps or gotcha's we are looking at doing the same thing and I'd like some ide of how had/easy this was?