There were four developers that are involved in the deployment and maintenance of the website. We have internal resources for support, but the actual management and maintenance are done by only four developers.

The main piece of advice I would give is to make use of asynchronous processing. It's becoming increasingly common, but it's important to understand its limitations. It's particularly useful when dealing with an application that has a lot of active users. For older code bases or companies that may not be as familiar with it, it's essential to understand and make use of asynchronous processing.

It's a great solution for larger companies, as the costs aren't as significant. However, for startups, there may be more cost-effective alternatives. It depends on the specific needs of the company. However, for an enterprise or large institution, it's a great choice because it's an actively updated framework, now cross-platform, and it's widely used and supported by a large community of developers. It's reliable, stable, and active. For all the reasons in the review, it makes this solution a go-to framework.

It's a reliable and robust framework, but it depends on the specific use case. For backend development, it's a mature and current solution, but for front-end development, there may be better options available in my opinion.

I rate ASP.NET a nine out of ten.

View full review »

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.

View full review »

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.

View full review »

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.

View full review »

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.

View full review »

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.

View full review »

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.

View full review »

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.

View full review »

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

View full review »

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. 

View full review »

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.

View full review »

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. 

View full review »

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.

View full review »

I rate ASP.NET an eight out of ten.

View full review »

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.

View full review »

I would rate ASP.NET eight out of ten.

View full review »

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.

View full review »

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.

View full review »

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

View full review »

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

View full review »

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. 

View full review »

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.  

View full review »

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.

View full review »

I would recommend this solution. 

I would rate it an eight out of ten. 

View full review »

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.

View full review »

If I needed to build a new site from scratch, and was able to use IIS7, it would be extremely likely that I would choose ASP.NET MVC. It’s a joy to work with (possibly because it’s "new"), and just makes sense. If I needed to work with an existing site, I would certainly have to consider the pro’s and con’s I mentioned above. ASP.NET MVC gives us an amazing new tool in our huge Microsoft toolbox. View full review »

ASP.NET is very easy to use if one is familiar with .NET framework. View full review »