ASP.NET Reviews

We primarily use the solution to create workflows, forms, and applications. 

I like that, with the Asp.net platform, you can create forms, applications, and workflows in Power Platform.

The initial setup is straightforward.

It is stable. 

We find the solution to be scalable.

I like that it is open-source and free to use. 

We haven't had any issues with the product.

It could use better reporting and documentation. 

We've used the solution for at least the past 12 months.

We find the product to be stable. It's reliable. There are no bugs or glitches and it doesn't crash or freeze. 

The scalability of the product is good. It's easy to expand.

We've dealt with support and find them to be helpful and responsive. We are completely satisfied with the level of support we can receive. 

The setup is pretty straightforward and simple. It's not a complex process.

This is an open-source product. We do not have to pay to use it. 

I'd rate the solution ten out of ten. We've been very happy with its capabilities. 

I have been using ASP.NET and Microsoft technologies for more than five years. I have never been this much addicted to a language like I am right now with C#. We have been using ASP.NET framework from mobile development to web development. It just works like a perfect solution to each possible project I've come across in life up till now.

There was a gap between developing mobile application some years ago but since Xamarin is in the family of Microsoft, which is a pretty cool cross-platform technology, there is nothing you can't do with Xamarin in the mobile world. It was useful for our organization to reach out for the mobile projects as well.

Most of the important things that would be good in the next release could be support in tooling and design of cross-platform app development.

Below are the coolest features of ASP.NET which I found valuable:

• Cross-platform and container support
• High performance
• Asynchronous programming via async/await
• Unified MVC and Web API frameworks
• Multiple environment and development mode
• Dependency Injection
• WebSockets and SignalR
• Cross-site request forgery protection
• Self-hosted web applications
• Action filters
• Globalization and localization
• Profiler

Although ASP.NET is a full package for any sort of development, whether be it in web or mobile, each part has been covered well enough but there is always room for improvement. I am pretty sure that Microsoft is working in the same direction to ease the pain of developers. I won't point out anything but I am going to enjoy the fact that it's pretty cool to solve something on our own rather than just complaining about something which we haven't tried. However, who said it's going to be easy, but nobody said it's impossible. The most important thing to improve in the next release would be support in tooling and high-level designer toolbox for cross-platform mobile app development.

I used ASP.NET for my personal information in the company, including things like payslips, vacation requests, information about my profile, and career development.

There is room for improvement with the interface. It is not very fast at times. For example, when you click on something, it can lag a bit. That sort of waiting can be very boring when you are just trying to carry out an easy transaction. 

I used this solution for about five years. 

ASP.NET is stable. I did not have to do any maintenance on it.

I cannot really comment on this because my company bought a specific number of user licenses and did not increase that amount in five years. 

I did not really have to get in touch with their tech support because we had our own IT department that was in charge of any issues we would run into. We would only escalate issues to the vendor in case of level-three incidents. Most of the time, we took care of any issues in-house. 

The initial setup was easy. 

Always take into consideration other vendors. I am sure that there are better solutions out there for different customers. ASP.NET is not the best solution for all companies looking to implement a solution like it. Also, it is best to adapt the company to the solution instead of trying to adapt the solution to the company, which is totally different. 

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.

Our company has a staff of five technicians and we use the solution for web application development projects on customer's local systems. 

The solution is very easy to maintain because UI management is simple and many libraries are available. 

The solution is more secure than other products. 

The solution needs to support its framework on all devices used for mobile application development. 

For example, development on an Android device requires use of Xamarin and that adds a level of difficulty. 

I have been using the solution for five years. 

The solution is stable. 

The solution is scalable. 

The setup and installation is easy. The deployment only takes two to five minutes. 

The solution is open source and free. 

Friends and colleagues have all learned and use the solution so it is very common. Java and PHP are less common than .NET technology. 

I recommend use of the solution because it is easy to understand and manage.

I rate the solution an 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.

We use ASP.NET to develop web applications and web API. I'm working at a government financial institution in Mexico that helps citizens buy a house.

The technology to integrate with cloud information could be improved.

I have been using ASP.NET for more than 15 years.

The solution is stable.

ASP.NET is scalable. 

There are many programmers and consultants who provide support for ASP.NET.

Setting up ASP.NET is hard.

I rate ASP.NET seven out of 10. I recommend the solution .net because it's easy for IT to provide program support.

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.