ASP.NET Reviews

We use ASP.NET for e-commerce, attendance modules, and school management.

It is easy to install ASP.NET on your laptop.

ASP.NET is a very slow tool, and it should be faster.

I have been using ASP.NET for three years.

ASP.NET is a stable solution.

Around 150 users are using the solution in our organization.

The solution’s technical support could be faster.

Neutral

The solution’s initial setup is easy.

ASP.NET is not an expensive solution.

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

Our primary use case is to develop food and geolocation applications. 

The language is easy to learn, understand and develop. There is good documentation available.

There should be more Python capabilities available.   

I have been using the solution for twenty years. 

I would rate stability a ten out of ten. 

The solution is scalable. 

I would rate technical support an eight out of ten. 

The initial setup is easy because I use container services. 

The language is free to use. The pricing wouldn't be a problem for the paid version.  

I have used Python to improve my applications, but I have used ASP.NET for all applications. 

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. 

The solution has good scalability.

The solution's initial setup is intermediate, and it could be improved.

I have been using ASP.NET for two years.

I rate ASP.NET an eight out of ten for stability.

I rate ASP.NET a nine out of ten for scalability.

I rate ASP.NET a seven out of ten for the ease of its initial setup.

We all deploy our applications in Git and raise one PR, and we need to deploy it in Jenkins, where we need to test the application. So, it takes one or two minutes because we are in the pipeline. A lot of users are using it, and they also have their changes. We need first to confirm if they are testing anything or not. After that, we can deploy changes and PR. Doing a whole task might take three to seven days, based on the availability of other users and employees.

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.

Our company used the solution to provide web services, pages, and registration forms for our client's job portal. 

The solution's framework supports storing all client-side and server-side code in one place. 

The solution is very user-friendly.

Scripted languages like AngularJS and Node.js are much faster than using ASP on the client side. 

We created server-side code in ASP based on client-side code but questions that hit the server took time to render as they searched the data. Node.js includes client-assisting languages that speed up the process. 

I used the solution for nine years at my prior place of employment. 

The solution is more stable than others because there are various security protocols that can be implemented to restrict users. 

The solution is easy to scale. 

Our company had more than 100 users with no issues. 

I did not need to contact support. 

The initial setup was easy. 

We pre-wrote code and identified functionality so that any deployment only took about fifteen minutes.

The solution requires a licensing fee but is worth the investment. 

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. 

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.

Whenever I don't know how to fix some critical issues, the Microsoft support team always gives us some good guidance and we follow it. When it comes to the application simulation and whether we think it should be added into the latest Microsoft released technology or not, we get everything we need. The only thing is they need to up their new technology and to revamp or migrate our current or existing applications into the latest version, and it should fix the current issues. But it's not me as a developer who can simply buy or implement the tool. Its edition should come from the management, which is not that easy. We only can propose that we get better features in the latest ASP.NET technology, and our higher reporting managers were keen to emphasize that it might take some time. We use the latest technologies that will be implemented with my current applications. We just sample it.

With ASP.NET there are pros and cons. The main pro is that it's very easy and we have Microsoft helping to stabilize the product which is coming with the all new features every year. It does improve the product. But the con is that every year they are launching a new technology, and for a company like us, we get confused about which version should be used.

Let's say we started using the next version, then the next year the version is no longer supported or it got upgraded to the new one. It's not that easy to migrate that entire software to that new version so they have a challenge here. I would hope when Microsoft releases any new products, they would release at least once in five years, and they need to give all the features for that version together. Not like now, when every edition they launch is a new product with the next version and entirely change that Framework. This is not advisable, because when we deal with the project, the size matters and the application usually also matters. Because if all projects are in one year, and you started working on the next version and we were going to launch that software the next year, that version has changed. It's very tough to migrate the entire one year project to the next version. So this is the challenge.

I have been using ASP.NET for eight+ years.

Because I'm working in the insurance domain, we normally don't simply upgrade just like that, and the version I started using was ASP.NET 3 and Framework 3.5. Nearly two years back we migrated to 4.0.

It is stable.

It is scalable because of the intra-, we can scale it but we cannot compare this with new cloud technologies because the cloud is a newcomer, a new revolution where you can simply change it in-cloud. But when it comes to my company, we have our own private intra-. If you want to increase the scale to a higher level, to raise the scale, we need to put a new server or increase the memory RAM in terms of hardware and intra-. Regarding capacity, from day to day, the company is growing and its customers are also growing, and it needs to cater to their needs, so we normally do the server checkups to see whether that number of incoming requests is able to cater within that existing hardware. If not, we will redirect the request to the intra- team, then they'll proceed with that, making the applications to be supplied so that we are able to execute the performance. 

I know it's 100 plus people using the solution but I don't the exact count.

As I said, ASP.NET already got a better version in the current market. 1% actually use that same version, which was released in 2011. Now, Microsoft announced that they are going to recall that support. I mean recall ASP.NET completely until 3.5. Luckily, we migrated to 4.0. I realize that even the 4.0 Framework was also slow and going to be recalled, as well. There are already discussions with my team and my management and because of this, we got a request from IT. We have our own IT R&D team and we got some guidelines where we have to come up with a new design with the current versions of ASP.NET to be migrated.

Regarding the initial setup, this question is a completely different story. It's not a simple setup question. Since I started learning ASP.NET, there are now many more versions. So many versions have been released and this Framework is so common that now people that used to call it ASP.NET now see it as a subset of Framework. So the Framework we saw then is different from what we see now. So I cannot easily answer because the story has changed since then. We have gotten many APIs released in between so that ASP.NET has become part of Framework and people more often use the Framework that is going to design an application.

For example, NBC is a model where we control the Framework. It's an architecture standard that has become very common since 2016. Recently, Microsoft also launched a new technology product called Core, the latest version of that is 2.0. Unfortunately, we were unable to use any of these latest technologies because of the banking insurance policies. We cannot simply implement the latest technologies just like that. We need to get the banking approvals and the country's regulations and guidelines. Microsoft is trying to improve its technology products, and somehow they made that product as open source. You can even re-direct your task to Framework in your own customized manner, which is more suitable for your company's needs.

Regarding the pricing, I don't know much because as a developer, I don't deal with the procurement, buying software. But I can say it does come with some good packages called corporate licenses. So when we buy a corporate license, I think multiple developers have access, can publish code and can develop from his own development machine. For instance, we can get Visual Studio where we use that as an IT tool, to develop the code and to buy the codes so we don't need to buy other products. I know that our company bought us a corporate license where we need to pay as a service for a year. We also have Microsoft support where we found some difficulty using so many of the application technologies. We can easily get support from that particular Microsoft team.

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 am using ASP.NET for business solutions.

The most valuable feature of ASP.NET is the support of multiple platforms with ASP.NET Core. Additionally, Azure integrates well with ASP.NET and Visual Studio.

It would be beneficial if Microsoft provided more support for certain technologies, such as Blazor, in the form of basic components. As it stands, some reliance on third-party tools may be necessary. Having more support from Microsoft for these technologies would make it easier for users to build and maintain applications. For example, the grids, date pickers, and dropdown lists would be components to add.

I have been using ASP.NET for approximately 15 years.

We have not had any issues with the stability of ASP.NET.

I rate the stability of ASP.NET a nine out of ten.

The solution is scalable. It's not a very high-impact solution. We mostly use it for internal business, and it's good. We have approximately 200 users that use the solution.

I rate the scalability of ASP.NET an eight out of ten.

We don't rely on Microsoft's support. We use third-party companies for support.

The initial setup of ASP.NET is straightforward.

This is a free solution. However, we have some server licensing costs which are not directly a cost of using the solution.

I rate ASP.NET an eight out of ten.

Our use cases depend on the specific requirements. For example, to get data from Jira to process and build reports using Power BI.

I like a feature in the recent release. So, I like the features around logging and pipelines provided by the recent .NET Framework.

I'd like to be able to run any application from a specific point instead of compiling all the code. For example, if I want to test function A, I should be able to test it even if my other functions aren't working. Like in SQL, you provide parameters to the function, and it executes. I'd like to see something similar in ASP.NET.

I have been using it for five years. 

It's a pretty stable solution. I would rate the stability an eight out of ten.

I will rate the scalability a nine out of ten. 

The support is good. 

I have experience with desktop technical solutions, web applications, and Windows applications using VPN.

I would rate my experience with the initial setup a seven out of ten, where one is difficult and ten is easy.

It is deployed both on cloud and on premises. The deployment time depends. If you're deploying to the cloud, it's typically faster. If you're doing it on-premises, it will take some more time.

The pricing is somewhere in the middle. Not too expensive, but not the cheapest either.

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.

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.