My first professional web application I built, I used asp.net framework to develop it. My experience was somehow out of this world. It was my first time building a web application using ASP.NET, I had to learn from the beginning how the framework works, and once I figured out how it works, I fell in love with it; 2 applications after the first one was developed using it.

I like the fact that it is free I like the fact that it very secure You can build web applications with ease For Microsoft developers, it makes it easy to develop web applications running on Microsoft platform

I don't like the fact that it is not a very easy technology to use It is not easy to learn like PHP

The system allows sellers of building insurance to instantly calculate the annual premium based on value, age, etc. of the building.The ready-to-use client => controller => service => DB flow with all the surrounding authentication etc. supported the focus on application and web design. Many of the security and process flow features are already implemented.

The product can be downloaded, installed, configured and is is ready to log in in under 1h. The steps to do this are clearly described in the manual. All you need is an operating system (Windows server in our case) and a DB plus development environment.The functionality saves the tremendous effort for developing an empty framework of DB access, user management, browser page design etc. Many features are available and there are regular update with more.The integration of the client design system is always soon after the latest releases which allows to update the own application with latest features.The stability / robustness is outstanding. Yet to experience the first failure after 5 years of the application running an an environment with several hundreds of users creating millions of DB records.Extending the developed app or writing plugins is straight-forward. This is due to the well-organized architecture of the overall system.

ASP.NET is not for beginners. What is a beginner and what a pro? This is individual judgement. I found it difficult to take advantage of all the features and sometimes to find out where to implement or change what.This is partly due to my own level (mid experienced but not high), partly due to the sheer complexity and many aspects but also due to the fact that the code has hardly any comments. Sometimes it might make sense to have find some more key features documented in the code.

Support is pretty good - usually get a response with 3 working days We have a fairly common architecture (AWS / ELB / ECS / Docker) so most issues we come across are not with ASP.NET Zero as such and have been experienced and resolved already

Modular design Separation of functions / services Tech stack integrates easily into our AWS infrastructure environment

Client use of Metronic theme - would love to see alternatives such as Material

Really quick and easy to get a SaaS ready application up and going.

Ability to create isolated multi-tenant databases and really good support for creating application editions with any combination of features for our SaaS solution.

Doesn’t align with our frontend tech-stack which uses React rather than Angular.

I cannot stress enough how much I like this product and would absolutely use this platform in the future. I have even recommended to our development partner that they should look to implement ASP.NET Zero for more of their clients because of how good a platform it is.

We estimated that the existing out of the box features saved us well over 6 months of development time because they were already well implemented. Multi-Tenancy, the concept of Features, and role-based security were all key to our success.

We found working with the Metronic themes the most problematic, but that is relative since nothing was really terribly difficult. Upgrading to new versions were just more time consuming because of the Metronic themes.