ASP.NET Reviews

I am responsible for maintaining the backend API for a website built with React, which supports the front end and I use ASP.NET.

ASP.NET is a great and versatile platform for developing APIs that has helped our organization. It has a robust ecosystem with many tools and SDKs that are tailored to it. It's also easy to set up and run APIs. We also use it with Microsoft Azure, which makes it easy to develop and integrate with Microsoft Azure's Cloud Services. Additionally, Azure Functions are similar to Amazon AWS Lambda functions, it easy to switch between different tooling and environments. It's easier to integrate with Microsoft Azure compared to other platforms.

Our primary use is for development purposes, to cater to the company's business requirements and needs. We have our own team where we get exactly what they want through the business analysts. Then according to that, we design and cater to the requirements and implement it.

In terms of the features that I have found most valuable, I'd compare it to Java and competent technology. We can do the same thing within Java, as well. But the thing with Java is that you need to write end-to-end, and with Microsoft, it is much easier for the developer and the intra-system because everything is very simple. It is not complex to maintain, to design, and to create. In simple terms, we can say that we choose Microsoft technologies most often because of their simplicity.

Any developer, even me, can read, understand, support and maintain. For Java, it's open-source and each fellow has his own style. Of course, .NET has its own so-called design patterns, we can call it Framework, and this Framework is direct for most of the developers. When we know which Framework this software design uses, the developer is easily able to understand it.

I work as a solution architect and a technical architect, too. I use .NET and ASP.NET specifically for web development. Nowadays, it's not just ASP.NET. We mostly use microservices or service-oriented architecture, so the web development is in Angular or React, and we create APIs like microservices or SOA. Either way, its working depends upon the client. We mostly develop single-page applications, and the backend is Microsoft .NET Core. Now we are migrating to .NET 7.0, and I have mostly been using SQL Server in the backend. I have also been working using Azure DocumentDB for some of the NoSQL.

My client is a medium-sized enterprise.

Classic ASP.NET had features like session caching, which were immense considering other technologies in the market. However, since we moved to the .NET Core environment, we now have the freedom to deploy it into any environment like Linux or any other operating system. The framework provides in-built security and performance-related mechanisms. We just need to utilize the technical stacks available within Microsoft .NET to incorporate these basic requirements of any business server. We don't need to write much custom code.

The performance of the servers is easy to scale. If we are hosting with .NET and millions of users hit our server, it is very easy to scale out because of the platform, unlike any other technology stack. Nowadays, we use the cloud platform that Microsoft supports. It is seamless compared to Java or any other technology stack.

Tata Technologies support manufacturing organizations and our customers are global automotive and aerospace manufacturers. Using Microsoft technologies we have developed applications for PLM, business applications solving business needs. The primary use cases would be to resolve business problems in Supply Chain, Inbound and Outbound logistics, Procurement to Pay, Contract to Pay, HR domain, Dealer Management System, Customer Relationship Management.

ASP.Net and Microsoft technologies platform has helped in improving our services to our clients. We are able to generate solutions for our global OEM customers and those solutions have become our arrowheads which we have taken to market as leaders. These arrowheads have allowed us to templatize and configure our solutions for our customers thus reducing our turn around time to reach to market

We are a company which has more strength with ASP.NET developers. Microsoft technologies are very easy to understand, integrate and adopt. And we have a working background on that. Our customer decided to use this because they want to develop those applications in ASP.NET.

The solution is easy to integrate and understand. It has a very good user interface and a lot of prebuilt tools, which require a lot less coding if we compare it to other solutions.

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.

We mainly use ASP.NET for handling tasks like check and credit card processing in the financial services sector and in utilities billing, particularly for managing services like gas and electricity. 

The most valuable feature of ASP.NET is its visual side, which makes building Windows forms applications visually efficient. However, for web deployment, particularly with technologies like Blazor Server, the visual aspect is not as prominent, and some improvements are still needed in that area.

I have found the entity framework to be a valuable feature. The authentication layer is amazing as well.

ASP.NET has a vibrant community, and as a result, we haven't had the need to contact technical support.

I've been working with it for about nine years.