Try our new research platform with insights from 80,000+ expert users
Project Lead at AIA
Real User
Simple to maintain, design, and to create
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."
  • "The con is that every year they are launching a new technology, and for a company like us, we get confused which version should be used."

What is our primary use case?

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.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

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.

Buyer's Guide
ASP.NET
November 2024
Learn what your peers think about ASP.NET. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
814,649 professionals have used our research since 2012.

What do I think about the stability of the solution?

It is stable.

What do I think about the scalability of the solution?

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.

How are customer service and support?

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.

How was the initial setup?

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.

What's my experience with pricing, setup cost, and licensing?

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.

What other advice do I have?

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.

Which deployment model are you using for this solution?

On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Tom West - PeerSpot reviewer
Director at Digital Page Publishers, Ltd.
Real User
Top 10
Not stable, out of date, and should not be used
Pros and Cons
  • "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."

What is our primary use case?

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

How has it helped my organization?

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

What is most valuable?

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

What needs improvement?

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

For how long have I used the solution?

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

What do I think about the stability of the solution?

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

What other advice do I have?

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.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
ASP.NET
November 2024
Learn what your peers think about ASP.NET. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
814,649 professionals have used our research since 2012.
SasidharParupudi - PeerSpot reviewer
Full Stack Developer at a outsourcing company with 5,001-10,000 employees
Real User
Top 10
Integrates well, straightforward implementation, and high availability
Pros and Cons
  • "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."

What is our primary use case?

I am using ASP.NET for business solutions.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

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

What do I think about the stability of the solution?

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

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

What do I think about the scalability of the solution?

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.

How are customer service and support?

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

How was the initial setup?

The initial setup of ASP.NET is straightforward.

What's my experience with pricing, setup cost, and licensing?

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

What other advice do I have?

I rate ASP.NET an eight out of ten.

Which deployment model are you using for this solution?

Hybrid Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Associate Software Architect at a computer software company with 501-1,000 employees
Real User
Easily handle data processing and reporting and good features available in the recent releases
Pros and Cons
  • "It's a pretty stable solution."
  • "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."

What is our primary use case?

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

What is most valuable?

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

What needs improvement?

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.

For how long have I used the solution?

I have been using it for five years. 

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

I will rate the scalability a nine out of ten. 

How are customer service and support?

The support is good. 

Which solution did I use previously and why did I switch?

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

How was the initial setup?

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.

What's my experience with pricing, setup cost, and licensing?

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

What other advice do I have?

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.

Which deployment model are you using for this solution?

Hybrid Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
RodrigoGalhardo - PeerSpot reviewer
CTO at Kultua
Real User
Top 5Leaderboard
An easy to learn solution with good documentation
Pros and Cons
  • "The solution is easy to learn, understand and develop."
  • "The capability related to Python needs to be improved."

What is our primary use case?

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

What is most valuable?

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

What needs improvement?

There should be more Python capabilities available.   

For how long have I used the solution?

I have been using the solution for twenty years. 

What do I think about the stability of the solution?

I would rate stability a ten out of ten. 

What do I think about the scalability of the solution?

The solution is scalable. 

How are customer service and support?

I would rate technical support an eight out of ten. 

How was the initial setup?

The initial setup is easy because I use container services. 

What's my experience with pricing, setup cost, and licensing?

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

Which other solutions did I evaluate?

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

What other advice do I have?

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. 

Which deployment model are you using for this solution?

Private Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Manoj Pathak - PeerSpot reviewer
One Identity Developer at Wipro Limited
Real User
A stable framework for customized user credentials and authorizations
Pros and Cons
  • "The solution's framework supports storing all client-side and server-side code in one place."
  • "Scripted languages like AngularJS and Node.js are much faster than using ASP on the client side."

What is our primary use case?

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

What is most valuable?

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

The solution is very user-friendly.

What needs improvement?

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. 

For how long have I used the solution?

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

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

The solution is easy to scale. 

Our company had more than 100 users with no issues. 

How are customer service and support?

I did not need to contact support. 

How was the initial setup?

The initial setup was easy. 

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

What's my experience with pricing, setup cost, and licensing?

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

What other advice do I have?

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. 

Which deployment model are you using for this solution?

Private Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Other
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
COE Head - Emerging Technologies & Global Practice Lead - Digital Transformations at Tata Technologies
Real User
ASP.Net in Microsoft Platform is a very powerful development tool through which you can design and develop highly scalable and reliable web applications
Pros and Cons
  • "This framework is very easy to use and tweak for our business needs."
  • "Sometimes we have issues with instability and it crashes, which is something that should be made to work better."

What is our primary use case?

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.

How has it helped my organization?

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

What is most valuable?

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

What needs improvement?

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.

For how long have I used the solution?

I have 11 years of experience with ASP.NET.

What do I think about the stability of the solution?

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.

What do I think about the scalability of the solution?

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.

How are customer service and technical support?

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

Which solution did I use previously and why did I switch?

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

How was the initial setup?

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

What about the implementation team?

We have implemented using our in house team

Which other solutions did I evaluate?

Yes, the options were JAVA, PHP

What other advice do I have?

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.

Which deployment model are you using for this solution?

Private Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Disclosure: My company has a business relationship with this vendor other than being a customer: partner
PeerSpot user
Solutions Architect at a insurance company with 10,001+ employees
Real User
Top 5
Good for building internal sites and web-based applications
Pros and Cons
  • "I would say that we have seen a return on investment when it comes to this solution."
  • "In my opinion, this solution should improve their web toolkit."

What is our primary use case?

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.

How has it helped my organization?

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

What needs improvement?

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

For how long have I used the solution?

I have been using this solution for almost 20 years.

What do I think about the stability of the solution?

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.

What do I think about the scalability of the solution?

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.

How are customer service and support?

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

How was the initial setup?

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

What was our ROI?

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

What other advice do I have?

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.

Which deployment model are you using for this solution?

Hybrid Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Download our free ASP.NET Report and get advice and tips from experienced pros sharing their opinions.
Updated: November 2024
Product Categories
.NET Development Services
Buyer's Guide
Download our free ASP.NET Report and get advice and tips from experienced pros sharing their opinions.