Azure DevOps is a very strong tool, committing to any available tools like Git or Vera. It competes with anybody in the market. Microsoft gives you the technology, but you must utilize it to write the code in a maintenance-free mode. The way you write the code and the decoupling principles you apply, for example, the SOLID principles. You should ensure the solution is maintenance-free or scalable. Security-wise, you should not look into the system to check for vulnerabilities whenever you are deploying. Those things come as part of our design and development. I would ask prospective users to start from the basics. Just travel 20 years back when ASP.NET started and what was the situation, then come back to the latest version so that they will understand the evolution. That is required because you may not know enough if you directly jump into the current version or technical stack. There are many legacy applications still running in the market. It doesn't matter that it's only on ASP.NET, but multiple technologies. It is very required to know what the market was earlier and how it has been evolving. And probably because they might be working on some migration project or maintaining the existing one while changing area by area on your system, a big system. That knowledge will be very, very helpful or handy when you are working on the latest stack. I rate ASP.NET a nine out of ten.
Cloud App Dev & Services Pre-Sales Lead for US & APAC at Systems Limited
Real User
Top 5
2023-02-13T20:14:00Z
Feb 13, 2023
My advice would be to go for ASP.NET in production. The solution has been out there for over two decades, and they know what they're doing. It's also modular and robust. I would absolutely recommend ASP.NET and rate it at eight on a scale from one to ten.
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.
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.
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.
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.
Unemployed at a manufacturing company with 501-1,000 employees
Real User
2020-09-27T04:09:52Z
Sep 27, 2020
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.
Cost-wise, choose Microsoft technology. Regarding availability, check the supply of developers in the current market, because most of the developers, entrepreneurs, who start a new job, are going to learn this technology because it's simple and easy to learn. There is nothing difficult to learn and to work on. So I can say yes, ASP.NET is easy and is low cost when compared to other technologies. And in the current market, we have plenty of developers available and people like to learn it because it's so easy. On a scale of one to ten, I would rate ASP.Net an eight.
I started my career with ASP.NET and I like most of the things about it. I started working with Microsoft technologies rather than Java technologies, and I am still with Microsoft. In India, they are moving to cross-platform deployment using the .NET work and I haven’t seen any drawbacks, apart from not being supported by Apple or macOS. I think that most customers prefer Windows applications, so they will prefer ASP.NET. I would rate this solution a nine out of ten.
COE Head - Emerging Technologies & Global Practice Lead - Digital Transformations at Tata Technologies
Real User
2020-02-10T07:39:02Z
Feb 10, 2020
In general, I would recommend ASP.NET. However, it depends upon the use cases. If there is an application for the web then it is very good. I would rate this solution an eight out of ten.
Overall, I rate ASP.NET an eight out of ten.
Azure DevOps is a very strong tool, committing to any available tools like Git or Vera. It competes with anybody in the market. Microsoft gives you the technology, but you must utilize it to write the code in a maintenance-free mode. The way you write the code and the decoupling principles you apply, for example, the SOLID principles. You should ensure the solution is maintenance-free or scalable. Security-wise, you should not look into the system to check for vulnerabilities whenever you are deploying. Those things come as part of our design and development. I would ask prospective users to start from the basics. Just travel 20 years back when ASP.NET started and what was the situation, then come back to the latest version so that they will understand the evolution. That is required because you may not know enough if you directly jump into the current version or technical stack. There are many legacy applications still running in the market. It doesn't matter that it's only on ASP.NET, but multiple technologies. It is very required to know what the market was earlier and how it has been evolving. And probably because they might be working on some migration project or maintaining the existing one while changing area by area on your system, a big system. That knowledge will be very, very helpful or handy when you are working on the latest stack. I rate ASP.NET a nine out of ten.
This is a legacy solution and I would strongly recommend people upgrade to .NET. This is outdated technology. I rate ASP.NET a one out of ten.
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.
My advice would be to go for ASP.NET in production. The solution has been out there for over two decades, and they know what they're doing. It's also modular and robust. I would absolutely recommend ASP.NET and rate it at eight on a scale from one to ten.
I rate ASP.NET an eight out of ten.
I'd rate the solution ten out of ten. We've been very happy with its capabilities.
I would rate ASP.NET eight out of ten.
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.
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.
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 rate ASP.NET seven out of 10. I recommend the solution .net because it's easy for IT to provide program support.
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.
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.
I would recommend this solution. I would rate it an eight out of ten.
Cost-wise, choose Microsoft technology. Regarding availability, check the supply of developers in the current market, because most of the developers, entrepreneurs, who start a new job, are going to learn this technology because it's simple and easy to learn. There is nothing difficult to learn and to work on. So I can say yes, ASP.NET is easy and is low cost when compared to other technologies. And in the current market, we have plenty of developers available and people like to learn it because it's so easy. On a scale of one to ten, I would rate ASP.Net an eight.
I started my career with ASP.NET and I like most of the things about it. I started working with Microsoft technologies rather than Java technologies, and I am still with Microsoft. In India, they are moving to cross-platform deployment using the .NET work and I haven’t seen any drawbacks, apart from not being supported by Apple or macOS. I think that most customers prefer Windows applications, so they will prefer ASP.NET. I would rate this solution a nine out of ten.
In general, I would recommend ASP.NET. However, it depends upon the use cases. If there is an application for the web then it is very good. I would rate this solution an eight out of ten.