ASP.NET Reviews

We mainly use ASP.NET for handling tasks like check and credit card processing in the financial services sector and in utilities billing, particularly for managing services like gas and electricity. 

The most valuable feature of ASP.NET is its visual side, which makes building Windows forms applications visually efficient. However, for web deployment, particularly with technologies like Blazor Server, the visual aspect is not as prominent, and some improvements are still needed in that area.

In addition to the visual aspect, there is a need for ASP.NET to provide a robust visual front end like there was in the past. This would prevent the need to explore low-code alternatives, which are becoming more popular.

I have been using ASP.NET for a long time, starting from 2005.

All six developers in our company have experience with ASP.NET.

I would rate their help as average, a five out of ten. Most of the time, you can find solutions by searching online because of ASP.NET's large user base and active community. However, when it comes to direct contact with Microsoft, it is not always exceptional because online resources are often sufficient.

Neutral

The main reason we chose ASP.NET is because of our historical shift to Microsoft products in the late '90s. We found more stability with Microsoft compared to other platforms like Borland. Microsoft's reliability and long-term presence in the industry were important factors for our decision, as we wanted to ensure continuity and avoid potential dead ends with smaller companies.

The initial setup is fairly simple.

The cost of ASP.NET and Microsoft development tools can vary. Microsoft offers a cost-effective option for software development houses with their direct access arrangement, where you pay around $400 a year to access all their current development tools. This can be a good value, especially if you have experience with .NET, although there may still be a learning curve for newcomers.

My advice to people who are considering using ASP.NET is that if your target audience primarily uses Windows machines, especially in financial institutions, ASP.NET and Microsoft technologies may be a lower-risk choice. However, consider productivity issues, especially as everything is moving towards browser-based solutions. Also, keep in mind cost considerations when evaluating software options. Overall, I would rate ASP.NET as an eight on a scale of one to ten. It has generally remained stable with no major syntax changes over the years. However, there have been two significant drawbacks, which are the abandonment of the VB6 methodology and the abandonment of Silverlight, both of which caused challenges and expenses when migrating applications. So, while ASP.NET is good, these two dead ends are a black mark on Microsoft's track record over the past 25 years.

We are a company which has more strength with ASP.NET developers. Microsoft technologies are very easy to understand, integrate and adopt. And we have a working background on that. Our customer decided to use this because they want to develop those applications in ASP.NET.

The solution is easy to integrate and understand. It has a very good user interface and a lot of prebuilt tools, which require a lot less coding if we compare it to other solutions.

First, the price of the solution can be cheaper as different customers have different budgets. Second, more frequent updates regarding security would be better as online application security is always a concern. Third, I think there is always room for improvement in every product. 

There should be consistent customization related to security, features, and developers, making the solution more understandable and adaptable. The market is growing day by day and there are so many competitors in the market for Microsoft, hence customization is required.

I have been using the solution for five to six years.

It is a stable solution. I rate the stability a nine out of ten. 

It is a scalable solution. I rate the scalability a nine out of ten. Our clients are all enterprises.

The technical support team is good. I rate the support a nine out of ten.

Positive

The initial setup is easy if you have all the hardware and prerequisites. It depends on the deployment size because we have multiple modules and are following the CI/CD process. 

We plan our deployment in chunks and on whichever process is ready. So it is easy and doesn't take much time. We have a deployment team of five engineers who handle the deployment. Our developers provide maintenance and support whenever needed. We have two developers for the maintenance so that if one developer faces any emergency, the other one can take responsibility.

ASP.NET's price is reasonable. I rate the pricing a five out of ten.

ASP.NET is very easy to learn for people who are new to using the solution. The Microsoft languages and ASP.NET process and application building are very straightforward. I recommend that people learn the usage of the solution. I rate the overall solution a nine out of ten.

We use ASP.NET for e-commerce, attendance modules, and school management.

It is easy to install ASP.NET on your laptop.

ASP.NET is a very slow tool, and it should be faster.

I have been using ASP.NET for three years.

ASP.NET is a stable solution.

Around 150 users are using the solution in our organization.

The solution’s technical support could be faster.

Neutral

The solution’s initial setup is easy.

ASP.NET is not an expensive solution.

Overall, I rate ASP.NET an eight out of ten.

Our primary use case is to develop food and geolocation applications. 

The language is easy to learn, understand and develop. There is good documentation available.

There should be more Python capabilities available.   

I have been using the solution for twenty years. 

I would rate stability a ten out of ten. 

The solution is scalable. 

I would rate technical support an eight out of ten. 

The initial setup is easy because I use container services. 

The language is free to use. The pricing wouldn't be a problem for the paid version.  

I have used Python to improve my applications, but I have used ASP.NET for all applications. 

I will continue to use this solution in the future because I am a developer, and I like the language.  

I think developers are going to keep the solution relevant forever. I would rate the solution an eight out of ten. 

Our company used the solution to provide web services, pages, and registration forms for our client's job portal. 

The solution's framework supports storing all client-side and server-side code in one place. 

The solution is very user-friendly.

Scripted languages like AngularJS and Node.js are much faster than using ASP on the client side. 

We created server-side code in ASP based on client-side code but questions that hit the server took time to render as they searched the data. Node.js includes client-assisting languages that speed up the process. 

I used the solution for nine years at my prior place of employment. 

The solution is more stable than others because there are various security protocols that can be implemented to restrict users. 

The solution is easy to scale. 

Our company had more than 100 users with no issues. 

I did not need to contact support. 

The initial setup was easy. 

We pre-wrote code and identified functionality so that any deployment only took about fifteen minutes.

The solution requires a licensing fee but is worth the investment. 

The solution provides a good framework for creating commands and portals for user log-ins. It can perform many functions such as special credentials or authorizations that are specific to each user. 

I rate the solution an eight out of ten. 

Throughout the last five or six years, I've been jumping on and off on projects, sometimes working on Xamarin, and other times working on ASP.NET.

Currently, I'm working on a project that uses ASP.NET (with .NET Core) quite extensively. This project is intended to help a business internally maintain an inventory of their commodities, assets, and so on. It's essentially an inventory-based evolution developed on ASP.NET.

In total, we have around 30 users working with ASP.NET in my company.

The developer support for ASP.NET is a big positive. It's actually very good, and since there are so many people who use ASP.NET, it's easy to get responses to questions about ASP.NET in the broader community.

Sometimes it can be really difficult to debug using ASP.NET. When there's an issue, trying to find out the cause is not always easy, so debugging is the top area for improvement, in my opinion.

I've been using ASP.NET for almost six years.

It's definitely stable.

I would say ASP.NET is scalable, and we have about 30 users on it at the moment.

The technical support is very good. Since the community is so large, it's easy to get responses for your questions.

I don't recall any technology that can be a complete comparison for ASP.NET.

The setup is easy and it takes only about one hour for deployment.

I think ASP.NET, in deployment, is something that's quite costly when you're on a cloud provider such as Azure, and you have to pay the server cost. On average, it can cost approximately $1,000 per month to host a good site with a few databases. So you can easily burn $1,000 per month for utilizing the different resources that are required to publish your application onto the web.

But in terms of the technology, it is free.

My advice to others is that they should be very focused around the usage of the servers, because people really don't worry much about the time, the kind of connections that are being made, etc., and when they go to the cloud, it gets very expensive. So I think it's really important that you think about pricing from day one, when you start developing the solution.

I would rate ASP.NET a nine out of ten.

Our use cases depend on the specific requirements. For example, to get data from Jira to process and build reports using Power BI.

I like a feature in the recent release. So, I like the features around logging and pipelines provided by the recent .NET Framework.

I'd like to be able to run any application from a specific point instead of compiling all the code. For example, if I want to test function A, I should be able to test it even if my other functions aren't working. Like in SQL, you provide parameters to the function, and it executes. I'd like to see something similar in ASP.NET.

I have been using it for five years. 

It's a pretty stable solution. I would rate the stability an eight out of ten.

I will rate the scalability a nine out of ten. 

The support is good. 

I have experience with desktop technical solutions, web applications, and Windows applications using VPN.

I would rate my experience with the initial setup a seven out of ten, where one is difficult and ten is easy.

It is deployed both on cloud and on premises. The deployment time depends. If you're deploying to the cloud, it's typically faster. If you're doing it on-premises, it will take some more time.

The pricing is somewhere in the middle. Not too expensive, but not the cheapest either.

It's a pretty stable and scalable tool, and it has very good support. If you find an issue, you can just Google it and find a solution easily online because there's a large community using it. It's pretty easy to learn, and you can usually find help if you encounter any issues.

Overall, I would rate the solution an eight out of ten.

The solution has good scalability.

The solution's initial setup is intermediate, and it could be improved.

I have been using ASP.NET for two years.

I rate ASP.NET an eight out of ten for stability.

I rate ASP.NET a nine out of ten for scalability.

I rate ASP.NET a seven out of ten for the ease of its initial setup.

We all deploy our applications in Git and raise one PR, and we need to deploy it in Jenkins, where we need to test the application. So, it takes one or two minutes because we are in the pipeline. A lot of users are using it, and they also have their changes. We need first to confirm if they are testing anything or not. After that, we can deploy changes and PR. Doing a whole task might take three to seven days, based on the availability of other users and employees.

I have done some UI changes and modifications because the response was not coming from the back end of data for some internal applications. I have also done some filtration from the front end.

Overall, I rate ASP.NET eight and a half out of ten.