TrustRadius Insights for ASP.NET are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Pros
Great Documentation: Users have expressed sincere appreciation for the software's exceptional documentation. They find it comprehensive and user-friendly, catering to both novices and experienced users. The availability of quick access to high-quality information has been highlighted as a significant asset by many reviewers.
Efficient Performance: Reviewers have noted with satisfaction that the software surpasses their performance expectations. Its ability to operate faster than anticipated while consuming minimal memory has resulted in tangible cost savings for users who switched from Python.
Customizable Functionality: Users highly value the customizable library and extensive functionality offered by the software. This flexibility proves especially beneficial in effortlessly establishing connections with databases and generating detailed reports, contributing significantly to its appeal among users.
I use ASP.NET with the SAP Business One SDK to develop financial web reports from the HANA database. The integration of ASP.NET with the SAP B1 SDK is excellent. It is possible to run complex queries and store the results in a record set variable to present them on the HTML page. Also, I use ASP.net to test and development of BOTS using Microsoft Power Automate.
Pros
Database integration for queries and inserts.
Excellent for script language for HTML.
Razor pages in Visual Studio 2022/.NET is the positive next step of web development.
Cons
Cases of study to show the excellent performance of ASP.NET combined with Razor.
Better integration with Amazon RDS database.
Easier method to parse the JSON results from webservice's.
Likelihood to Recommend
ASP.NET is well suited to work with the Microsoft SQL Server flavors database. It has an excellent interface library with the database to get the results and store them in a variable. From here, you can display the results using script language to the HTML web page. Probably ASP.NET is not appropriate to do Android development for offline applications. These applications can keep working without a connection to the internet.
Our core application was developed using ASP.NET.We use it as a database user interface and to follow our workflows and processes.
Pros
Easily build user interfaces for web applications.
User management through user sessions.
Integrates easily to third party .NET components.
Cons
It could be more visually appealing.
For certain things you shouldn't depend on third party applications.
Likelihood to Recommend
ASP.NET works well to build robust web-based systems. It integrates security very well and a lot of components that allow you to build your web pages using a graphic designer. However, the essential elements of ASP.NET are too basic, and sometimes development is accelerated by buying third-party components. ASP.NET also integrates very well with any database. It offers user sessions that easy to implement and are secure.
VU
Verified User
Engineer in Engineering (Non-profit Organization Management company, 1-10 employees)
ASP.NET has come a long way since 2010 when I started my career in web development. It was a cumbersome and slow technology that was only used by "Microsoft shops" that has transformed into an easy-to-use and open source (!) technology that is also one of the fastest web app hosts in the world. The .NET Core team has really made ASP.NET shine.
We use it to build anything from small internally-used applications to large web applications that scale to thousands and thousands of users.
Pros
Build web applications with ease.
Get up and running in minutes.
Cons
Make it easier to vote on features that we want to see implemented.
Likelihood to Recommend
If you're building a REST API or a Websocket application, ASP.NET is a must-use.
The only reason we would prefer using e.g. NodeJS over ASP.NET is when we need to use a package that doesn't have a good alternative in the .NET ecosystem, which is rare. On such example is pdfkit, which we use to render PDF receipts.
[ASP.NET] is one of the best languages for developing web based applications and websites. [ASP.NET] when integrated with CSS, Javascript and Jquery can give a very good UI. [ASP.NET] is used for building web applications which can interact with databases. It is a server side programming language.
Pros
Community versions of Visual Studio for ASP.NET and MSSQL Server Express as database are free. However, the fees of the advanced database systems required for comprehensive projects are quite high (MSSQL Server Standard, Enterprise etc.).
NET is a framework (framework) where .NET language is used to develop web applications. It uses C # language and requires advanced coding knowledge to learn.
For hosting of Code generated by ASP. Net can be hosted on IIS only.
Cons
Net is just like plug and play, we have to focus on a logic of code rest part can be handled by ASP. Net framework.
It's a best for only web development.
One downside with ASP.NET is its reliance on the .NET framework.
Likelihood to Recommend
ASP.NET is one of the main languages that we use across all of our Web Projects. We use Asp.net in may ways in our department. We use [ASP.NET] for developing most of our web projects using [ASP.NET] MVC for most of our custom applications, and we also integrated our project, which develop using [ASP.NET] with numerous systems. What I disliked is the updates on the framework. And the compatibility on different programming tools. Asp.net uses more Web server resources than others and it is expensive for small companies.
We use ASP.NET to drive most of our services. It provides the back end for our web-based software service, powers our client API gateways, and offers isolated portals for our clients' customer, employees, and business partners to interact with them.
It allows us to build our business logic on a thin, configurable framework and implement different architectures within that to suit the specific need of the project.
Pros
Quick to set up and configure
Easy to configure in code
Expandable and customizable
Cons
Fragmented version history makes it hard to know where to start
Likelihood to Recommend
I would recommend ASP.NET for any web-based application that requires business logic or database functionality. I would also recommend it for API services or internal services.
I would not recommend it for front-end-heavy applications or websites that are primarily static pages.
It was used by our front-end development team. We served web pages for the company's free tier solution, which needed SEO, so it had to be server rendered. The business logic layer was already build on top of .NET so it made sense to stick to the same tech stack.
Personally I started my career with ASP.NET before MVC arrived. The old ASP.NET tried to abstract the web environment which ended up complicating things and misleading young developers. ASP.NET and Microsoft in general have since greatly mended their ways and although it's not my go-to stack, ASP.NET MVC is a completely legitimate one.
Pros
C# is a great language and .NET has a lot of powerful functionality like LINQ.
Easy to integrate with SQL server and other Microsoft solutions (Entity Framework is great).
Microsoft tools - get the latest updates and support. They usually have great offerings for early stage startups.
Cons
Single page applications are much easier on a plain Javascript Stack-like client side frameworks or NodeJS.
Heavily dependent on visual-studio and the Microsoft Stack.
Still lacking in the ease of getting started and quickly deploying things.
Hard to find good developers that don't have a bias for ASP.NET.
Likelihood to Recommend
ASP.net is well suited when all your services are a part of the Microsoft ecosystem. If you wish to be dynamic with your tech stack and easily switch cloud providers and programming paradigms, ASP.net might get in your way a little.
Personally I am more inclined to use client side solutions for web apps, or NodeJS if server side logic/rendering is needed. However ASP.net uses C# which is a great language, and the framework has everything you need for success.
We write multiple software products across our teams. The majority of these products are written in some version of ASP.NET. It is used daily for development, debugging, and all other R&D activities. This is across multiple versions of .NET and both legacy applications and new greenfield applications. In general, all back-end code is .NET.
Pros
.NET runs well in a variety of Windows environments.
It integrates seamlessly with other Microsoft product (SQL Server, Azure, etc).
Cons
The documentation for much of the MSDN could be improved. That said, they have done a much better job with .NET Core.
Likelihood to Recommend
.NET is suitable across a variety of scenarios as it is a programming language. I have used it to write scalable servers, web APIs, desktop clients, command line applications, and a variety of other applications. As long as you are going to be running on an environment that can have the runtime, you can use it.