ASP.NET Reviews

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.

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. 

I am using ASP.NET for business solutions.

The most valuable feature of ASP.NET is the support of multiple platforms with ASP.NET Core. Additionally, Azure integrates well with ASP.NET and Visual Studio.

It would be beneficial if Microsoft provided more support for certain technologies, such as Blazor, in the form of basic components. As it stands, some reliance on third-party tools may be necessary. Having more support from Microsoft for these technologies would make it easier for users to build and maintain applications. For example, the grids, date pickers, and dropdown lists would be components to add.

I have been using ASP.NET for approximately 15 years.

We have not had any issues with the stability of ASP.NET.

I rate the stability of ASP.NET a nine out of ten.

The solution is scalable. It's not a very high-impact solution. We mostly use it for internal business, and it's good. We have approximately 200 users that use the solution.

I rate the scalability of ASP.NET an eight out of ten.

We don't rely on Microsoft's support. We use third-party companies for support.

The initial setup of ASP.NET is straightforward.

This is a free solution. However, we have some server licensing costs which are not directly a cost of using the solution.

I rate ASP.NET 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 primary use case for ASP.NET is for the web-based department. However, as local platforms are being introduced, we are trying to reduce our use of ASP.NET.

This solution has helped my organization by allowing me to build internal sites and Web-based applications.

In my opinion, this solution should improve their web toolkit.

I have been using this solution for almost 20 years.

I would rate the stability of this solution a nine, on a scale from one to 10, with one being the worst and 10 being the best.

I would rate the scalability of this solution a nine, on a scale from one to 10, with one being the worst and 10 being the best.

There are a lot of consultants on the market that provide support services, so we hardly ever went with Microsoft's tech support.

I would say that the initial setup process was quite straightforward.

I would say that we have seen a return on investment when it comes to this solution.

Overall, I would rate this solution a nine, on a scale from one to 10, with one being the worst and 10 being the best.

ASP.NET's best features are its application structure and API testing.

An area for improvement is the structure template.

I've been using ASP.NET for five years.

There are often stability issues when new updates are first released.

The initial setup was easy.

ASP.NET is open-source and free of charge.

I would rate ASP.NET eight out of ten.

With ASP.NET I create APIs

It is completely, positively, and positively assisting us. To the best of my knowledge, there is nothing to change when generating APIs.

While using ASP.net, we can create interactive websites.

We can create interactive websites. Aside from that, we can create APIs for mobile platforms and also generate APIs.

I am not familiar with ASP. That's why I'm not sure which scenarios will see an increase.

I don't use ASP very often. That's why I'm not sure what additional features would be of assistance to users. I am only using ASP to generate the APIs.

You are required to have knowledge of C#.

I have been working with ASP.NET since the beginning.

We are using the old version because this project was started a long time ago.

It is not too old; it's one or one year and a half old.

ASP.NET is a stable product.

ASP.NET is scalable. We can easily add to it.

This solution is used by approximately 100 developers in our company.

I have never contacted technical support, but some of my colleagues have.

The initial setup was easy.

It took approximately 30 to 40 minutes to install everything and have it running.

ASP.NET is an open-source solution.

You can use ASP.net without a doubt. However, before beginning ASP.net, learn the basics of C#.

I would rate ASP.NET an eight out of ten.

I am not giving it a ten out of ten because there are other languages, such as Angular and React, which are available in addition to ASP. I am not very knowledgeable about them.

However, I am unfamiliar with React and Angular, which is why I rated it an eight out of ten.