ASP.NET Reviews

Our primary use case for ASP.NET is for the web-based department. However, as local platforms are being introduced, we are trying to reduce our use of ASP.NET.

This solution has helped my organization by allowing me to build internal sites and Web-based applications.

In my opinion, this solution should improve their web toolkit.

I have been using this solution for almost 20 years.

I would rate the stability of this solution a nine, on a scale from one to 10, with one being the worst and 10 being the best.

I would rate the scalability of this solution a nine, on a scale from one to 10, with one being the worst and 10 being the best.

There are a lot of consultants on the market that provide support services, so we hardly ever went with Microsoft's tech support.

I would say that the initial setup process was quite straightforward.

I would say that we have seen a return on investment when it comes to this solution.

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.

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.

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.

With ASP.NET I create APIs

It is completely, positively, and positively assisting us. To the best of my knowledge, there is nothing to change when generating APIs.

While using ASP.net, we can create interactive websites.

We can create interactive websites. Aside from that, we can create APIs for mobile platforms and also generate APIs.

I am not familiar with ASP. That's why I'm not sure which scenarios will see an increase.

I don't use ASP very often. That's why I'm not sure what additional features would be of assistance to users. I am only using ASP to generate the APIs.

You are required to have knowledge of C#.

I have been working with ASP.NET since the beginning.

We are using the old version because this project was started a long time ago.

It is not too old; it's one or one year and a half old.

ASP.NET is a stable product.

ASP.NET is scalable. We can easily add to it.

This solution is used by approximately 100 developers in our company.

I have never contacted technical support, but some of my colleagues have.

The initial setup was easy.

It took approximately 30 to 40 minutes to install everything and have it running.

ASP.NET is an open-source solution.

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.

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.

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

Following features of ASP.Net and Microsoft Technologies are valuable:

1. Cross platform support and container support is really a breakthrough

2. ASP.Net has unified MVC and web API frameworks which is really helpful to developers

3. VAPT points can be taken care with ease handling OWASP standards

4. ASP.Net integration with Azure Cloud environment is very seamless and supports other Cloud providers

5. ASP.Net provision of integration with FxCop, SonarLint and SonarQube for static code coverage ratio is very good

6. NuGet package integration is really very good

Following can be improved:

1. VS IDE should be license free so that community edition interactions can be enhanced

2. Undefined Application Architecture with lack of Separation of Concerns (SoC)

3. Lack of abstraction with least control over HTML.

4. Limited support for testing and SEO.

I have 11 years of experience with ASP.NET.

Regarding stability:

1. The releases made by Microsoft need to be stable from the perspective of release

2. The Microsoft platform has come out of ages, but still it need to be more stable so that the production environment is very stable.

Microsoft Platform is highly scalable and so is ASP.Net. However there some important factors like Separation of Concerns, SEO integration etc. which need to be integrated.

The technical support is fine. The partnership helps us get support for what we need and we have no complaints.

Yes, we moved from legacy ASP to ASP.Net because of technological advancements

Initial setup is straightforward and it is complimenting. We are able to setup the VS IDE and the project structure easily in ASP.Net projects

We have implemented using our in house team

Yes, the options were JAVA, PHP

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.

If a project is inherited from a client, we would need to utilize ASP.NET, in such cases, we strongly recommend upgrading to .NET

ASP.NET does not help organizations it is a distraction and out of date.

The solution is useful for seeing what old technology was before the new technology we use today, such as .NET.

The solution is out of date and should not be used.

I have been using ASP.NET since it came out.

The solution is out of date and shouldn't be used. It is not stable.

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.

We primarily use the solution to create workflows, forms, and applications. 

I like that, with the Asp.net platform, you can create forms, applications, and workflows in Power Platform.

The initial setup is straightforward.

It is stable. 

We find the solution to be scalable.

I like that it is open-source and free to use. 

We haven't had any issues with the product.

It could use better reporting and documentation. 

We've used the solution for at least the past 12 months.

We find the product to be stable. It's reliable. There are no bugs or glitches and it doesn't crash or freeze. 

The scalability of the product is good. It's easy to expand.

We've dealt with support and find them to be helpful and responsive. We are completely satisfied with the level of support we can receive. 

The setup is pretty straightforward and simple. It's not a complex process.

This is an open-source product. We do not have to pay to use it. 

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