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.

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.

I use ASP.NET for VBScript. It is used to schedule, deploy, and monitor different processes within UiPath.

Using this product increases our productivity. It also helps to improve the relationship between stakeholders and customers because the delivery time is very attainable.

All of the features are important, based on the project. It really depends on what it is that you're doing.

The most valuable features are ease of use, scalability, and flexibility.

It has a good library that you can find options for what it is that you want to implement or schedule.

The areas in need of improvement will vary based on the environment and what it is that you are working on.

Performance is an area that can always be improved. For example, when you are doing invoice processing, you want to make sure that they can run at a faster rate. In terms of claims processing for an insurance company, you want to make sure that they have an increased rate of productivity.

I would like to see a summary or list of key concepts that are available. It should include a list of challenges that people are having, and some of the solutions that can help to solve them.

I have been using ASP.NET for two and a half years.

There are always issues with bugs, but it depends on how you handle them. They can be in different places. For example, if you don't see bugs in the analysis phase then we should isolate the phase where the bug is occurring. You let it run through, almost to the UTI.

The scalability is quite good.

The product is normally used by developers. Analysts do use it, but we have a code of honor based on how the project is prioritized. We have to make sure that we communicate with the stakeholders to make sure that whatever they have specified is working. In some ways, it's up to the standards of the person.

I have never requested support for ASP.NET.

Prior to this, I worked with other scripting languages. Having this experience goes a long way toward really understanding the project, regardless of industry.

I would say that the initial setup is complex. You have to consider different users or different systems being connected to the user interface, which is where you face some of the issues. Perhaps it was not fully thought out and it didn't have the right input components installed. That is something that you have to make sure of.

The return on investment is very high when using this technology.

I would say that integration is the key factor. When you have a better implementation methodology then it will make it easy to integrate with the platform.

My advice for anybody who is implementing this solution is to start with an easy example. It will take a little bit of time for you to understand it. Try to find resources and study. Definitely, I would not discourage anybody from using it.

I would rate this solution an eight out of ten.