Hi,
Will the Angular 1.x version of Asp.Net Zero get the new features 4.1, i.e. Tenant Subscription System, Payment Integration and new dashboards?
I need these new features but I don't want to rewrite my app.
Regards, George
12 Answer(s)
-
0
Hi,
Unfortunately no. Only ASP.NET Zero Core will get these features.
-
0
That's a great shame as I've invested a huge amount of time developing my application and don't have time to rewrite it now. I've just paid your fee ASP.Net Zero renewal as well. Will you continue to support the Angular 1.x non-core versions? Is there any chance you'll add the new features to them at some later date? What do you suggest people in my situation do?
-
0
Why not?
-
0
Hi gconey,
First of all thank you very much for purchasing AspNet Zero and renewing your license. We can continue to develop ABP framework as open source and free by the help of you: AspNet Zero customers.
We will continue to;
- Proving premium forum support for all versions of AspNet Zero (including Angularjs 1x and ASP.NET MVC 5.x versions).
- Fix bugs/problems with the existing solution, add critical security features and keep the solution up to date with dependencies.
- Releasing new versions of ASP.NET Boilerplate framework that supports ASP.NET MVC based projects. That means you will get new features, enhancements and bugfixes of the framework.
But we will not continue to add major features to angularjs 1.x and AspNet MVC 5.x solution. I think this should be reasonable because;
- Angularjs and ASP.NET MVC have new versions. This is not just a new version, but a complete re-write. Microsoft and Goodle will also not implement new features for those old versions. So, we have also re-written our solution based on these frameworks. We also added new features to these old frameworks for a long time. Now, we can not implement every feature 4 times. Our statistics shows that most projects are created with new frameworks by our customers.
- ASP.NET Zero's main goal is to provide a base solution to create new applications. Upgrading was never our priority because we sell the source codeand you freely modify it and that makes automatic upgrade impossible. I had explained this in this post in detailed: #1073 But Abp packages are still upgradable which is more important I think.
Currently (until v4.0) functionalities of 4 versions are identical. Once we release v4.1 AspNet Core / Angular versions will have more features and this will continue like that. We are adding a note to feature list on AspNetZero.com to indicate all differences of different versions.
What I suggest for existing projects? Actually, it's nothing different than Google and Microsoft says: Build your new projects with new frameworks, but you can safely continue to develop your existing projects. I would not re-write my project if it works. But if your project is new and you haven't implemented much features and you think you will have much more development on this project, you can consider to migrate (). It's not a complete re-write. AspNet Zero is a layered solution. That means your Core, Application and EF layers will almost directly migrate to new frameworks. But for User Interface, it will be a rewrite, especially for angularjs, because Angular (currently v4) has no similarity to previous version.
As I check it @gconey asked it before and I had replied it: #2359@d2dbb25b-07b6-491d-b4c6-1fe9c5795dd3 :)
Have a nice day.
-
0
I'll follow up on this thread. It is disappointing that the Subscription Features in 4.1 are only being implemented in Net Core/Angular and that no future enhancements will be made for MVC 5. While Net Core is "cutting edge" it is also, just that - out on the edge. With Entity Framework Core still catching up <ins>even Microsoft</ins> isn't telling developers Microsoft to "abandon MVC 5 and only do Core." MVC 5 applications will be around for another ten years at least and it will be <ins>years</ins> before the huge amount of existing MVC 5 apps are ported over to Net Core, if ever. Most shops building enterprise apps are moving to Core slowly and sticking with the reliability of MVC 5 so I think it is a big mistake for Volosoft and for all your customers to ignore future feature updates to MVC 5.
Out of curiosity, how many users have downloaded copies of MVC 5 versus the Core version?
-
0
<cite>OutdoorEd: </cite> I'll follow up on this thread. It is disappointing that the Subscription Features in 4.1 are only being implemented in Net Core/Angular and that no future enhancements will be made for MVC 5. While Net Core is "cutting edge" it is also, just that - out on the edge. With Entity Framework Core still catching up <ins>even Microsoft</ins> isn't telling developers Microsoft to "abandon MVC 5 and only do Core." MVC 5 applications will be around for another ten years at least and it will be <ins>years</ins> before the huge amount of existing MVC 5 apps are ported over to Net Core, if ever. Most shops building enterprise apps are moving to Core slowly and sticking with the reliability of MVC 5 so I think it is a big mistake for Volosoft and for all your customers to ignore future feature updates to MVC 5.
Out of curiosity, how many users have downloaded copies of MVC 5 versus the Core version?
I fully agree with your post!
-
0
Hi,
Thank you for your comments. I will try to explain the reason of our decision.
First of all, sharing project download statistics since you wanted:
This is for last 2 months (beginning from 1st May 2017):
- ASP.NET Core + Angular = 39.5%
- ASP.NET Core + jQuery = 26.5%
- ASP.NET MVC 5.x + jQuery = 19%
- ASP.NET MVC 5.x + Angularjs 1.x = 15%
As you have seen, 66% (2/3) of our customers are using ASP.NET Core / Angular 2 versions.
ASP.NET Zero's main goal is to start to new web applications. We don't provide a good solution for;
- Migrating legacy applications (not built with ABP framework or AspNet Zero).
- Upgrading application built with previous versions of AspNet Zero (see #1073).
Like Microsoft, we also still does not tell to drop ASP.NET MVC 5.x applications. We understand that some of our customers will still start with MVC 5.x + EF 6.x (because of technical and non-technical reasons). So, why we don't add new features for MVC 5.x:
- If we countinue to implement every new feature 4 times (1. core+angular, 2. core+jquery, 3. mvc5+angularjs, 4. mvc5+jquery) it will be very slow to create new features and enhancements.
- AspNet Zero (MVC5) has already good features and enough infrastructure to start to a new application before v4.1. Do not misunderstand that: We continue to support and enhance infrastructure (ABP framework) for MVC 5.x applications. So, you can safely continue to develop your existing applications (just like Microsoft does not add new features to mvc5 but still supports it as first class citizen).
One another thing is that: Our ASP.NET Core version supports full .net framework too (beside .net core). So, your existing/legacy code can still be integrated to ASP.NET Core.
We will continue to evaluate feedbacks from our customers and watch the usage of core and mvc frameworks. If we have more resource, we consider to add features to mvc5x version in the future. But we believe AspNet Zero's actual value is not features, but infrastructure. We are developing it for 2 years. We could ad 5x more features in that time (that would show our demo richer and make our sales more :)), but we think to aligning to the latest technology and providing a well architected solid infrastructure has much more value for real world applications.
-
0
Thanks for your response. I understand that decisions have to be made about software and what version to support.
I do question your choice of <ins>only</ins> using the last two months of downloads and then making a broad claim that "2/3 of our customers are using Net Core/Angular." That data is slanted since it represents such a short time period. All you can say is that "2/3 of the customerssince May." I downloaded the 4.1 MVC 5 version and then learning that the new features were not in MVC 5, I downloaded the Net Core 4.1 version to do a test install to see the features so I am one of your 26.5%. But I am not going to completely redo my current application to move to Net Core.
I expect if you go back to the product release date you'll find a very different overall use pattern for your customers.
-
0
Hi,
Just sharing more statistics:
Beginning from 2017-01-06 (the time we released angular2):
Aspnet Core (with angular or jquery): 64%. Aspnet Mvc 5. (with angularjs or jquery): 36%.
I know that not all downloads are production projects. Some of they may be just for test or update purposes, but that provides an idea for us.
-
0
Hi,
I suggest a compromise. Now that we know you're branching the feature set. How about a one time only update of these new features back to the MVC5 versions? I'm not a far from releasing my first MVC5 app to production and would dearly like the subscription feature. I also have new projects coming and want to use ASP.NET zero for these but one requires ADFS so I'm forced to stay with MVC5 for now.
Also, i love this project. You're saving me a lot of development time.
Regards, Conor
-
0
Hi @hikalkan,
statistic data you are having/showing can be very misleading. Probablly everyone has downloaded Aspnet Core version, even I did (several times). And that was only few months ago, in April I think. But then I realized that the solution was not even close to be ready for a serious commercial project (lack of documentation, a lot of bugs, …).
Because of that I decided to go with AspNet Angularjs and now, few months later, you are telling me that you are not planning to implement any new features into this solution. I’m very disappointed I must say …
At least you should implement features which are normally supported in ABP, like disabling languages and such ….
Kind regards
-
0
Hi,
Thank you for your additional comments.
At least you should implement features which are normally supported in ABP, like disabling languages and such
That's reasonable, while there are not much stuff like that.
We wouldn't want to introduce such a feature branching, however this comes from external sources: Microsoft and Google have done such a branching and this is very natural. Even such huge companies does not have resource (or don't want to spend time) to align all features of their frameworks. It's same for us: We can not add same feature 4 times with our more limited resources.
