Try our new research platform with insights from 80,000+ expert users
Roger-Morera - PeerSpot reviewer
Developer at a tech consulting company with 51-200 employees
Real User
Highly versatile, dynamic, and versatile
Pros and Cons
  • "The most valuable feature is customization."
  • "Microsoft could improve .NET Framework by providing more resources to help users understand the solution."

What is our primary use case?

I use this solution with data from different applications to obtain data from files, apply business roles, and obtain different behaviors of the data. I also use it to transform and apply valuations and to send information through SMS or certified email.

How has it helped my organization?

.NET Framework saves us cost and time, provides quality and accuracy, and improves our security.

What is most valuable?

The most valuable feature is customization.

What needs improvement?

Microsoft could improve .NET Framework by providing more resources to help users understand the solution. I would also like Microsoft to add an additional monitoring tool - for example, when we develop a robot using .NET, we need too many people following the area of the robot.

Buyer's Guide
Microsoft .NET Framework
February 2025
Learn what your peers think about Microsoft .NET Framework. Get advice and tips from experienced pros sharing their opinions. Updated: February 2025.
838,713 professionals have used our research since 2012.

What do I think about the stability of the solution?

There have been some issues with the running application crashing.

What do I think about the scalability of the solution?

The scalability is good.

How are customer service and support?

Microsoft's technical support is good.

How was the initial setup?

The initial setup is quite complex and requires someone with technical skills to complete it. The minimum time for setup is three weeks.

What about the implementation team?

We used an in-house team.

What was our ROI?

.NET Framework is a good tool to add value to our company.

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

We pay around $450 for our license.

What other advice do I have?

.NET Framework is very versatile and dynamic and allows us to change properties and customize the controls. If you're familiar with programming, you can go ahead with all the functionality and create new products. I would rate .NET Framework nine out of ten.

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
PeerSpot user
Software Engineer at Micron Technologies, Inc
Real User
Top 20
It simplified operations dealing with the allocation and deallocation of memory spaces
Pros and Cons
  • "Initial setup is straightforward. All the components are readily available."
  • "The addition of generics to handle common functionality across types, and the more recent upgrade of the dataset to the Entity Framework, has cut development time drastically, while increasing quality and confidence between builds."
  • "The .NET Framework simplified operations dealing with the allocation and deallocation of memory spaces and the additional processing resources."
  • "Needs stronger security with respect to cloud issues."

What is our primary use case?

The .NET Framework is the foundation for software design and development. This is the context that I use it in, and the perspective that I view the discussion about it.

How has it helped my organization?

Coming out of C++, the .NET Framework simplified operations dealing with the allocation and deallocation of memory spaces and the additional processing resources. Adding this feature to the .NET Framework has freed countless hours of leak management. 

What is most valuable?

The addition of generics to handle common functionality across types, and the more recent upgrade of the dataset to the Entity Framework, has cut development time drastically, while increasing quality and confidence between builds. Finally, the test framework allows for increased velocity. 

Most recently, the updates tot he Entity Framework, and the addition of the ability to work with mobile applications have also been huge additions

What needs improvement?

  • Stronger security with respect to cloud issues
  • Greater flexibility with data connections
  • Better control
  • Extensibility of the framework as a whole

For how long have I used the solution?

More than five years.

What do I think about the stability of the solution?

Changes in technology generally happen faster than any single entity can keep up with. But the side-by-side Runyon capability handles most stability issues behind the scenes. 

What do I think about the scalability of the solution?

Only the ones that were fixed. 

How are customer service and technical support?

I have not had to use the support.

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

No.

How was the initial setup?

It is straightforward. All the components are readily available.

What about the implementation team?

Started as part of a school program.

What was our ROI?

I can't measure ROI, because I've never used a different technology stack.  Switching from one to another has not been an issue. 

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

Do your homework. Consider the partnership program.

Which other solutions did I evaluate?

No.

What other advice do I have?

With the advent of IoT, combined with cross-platform development, the .Net framework becomes much more versatile. We should begin to see apps scaling down in size, but also (literally) covering more ground. 

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
Buyer's Guide
Microsoft .NET Framework
February 2025
Learn what your peers think about Microsoft .NET Framework. Get advice and tips from experienced pros sharing their opinions. Updated: February 2025.
838,713 professionals have used our research since 2012.
User
Top 20
Have managed complex setups with connectivity and offers good scalability
Pros and Cons
  • "As we are scaling quite nicely on Azure."
  • "There may be some topics regarding connectivity and management of certificates that require attention."

What is our primary use case?

I am building a web application and using this solution.

What is most valuable?

The platform was chosen to be used and I did not choose it, so I can't speak to what is the best feature.

What needs improvement?

There may be some topics regarding connectivity and management of certificates that require attention. We are currently facing some issues.

For how long have I used the solution?

I have been using the solution for about two years.

What do I think about the scalability of the solution?

As we are scaling quite nicely on Azure.

How are customer service and support?

I have not contacted customer service recently.

How would you rate customer service and support?

Neutral

How was the initial setup?

The initial setup is complex. Once you know and have some help, it is manageable.

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

The company is not paying anything for the license. I am not familiar with this area. For us, it's free.

Which other solutions did I evaluate?

Java and Sprint are alternatives we considered.

What other advice do I have?

Our solution should work for roughly 50,000 users every day. We are still collaborating, and it's okay. 

The overall product rating is eight out of ten.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Flag as inappropriate
PeerSpot user
reviewer2356524 - PeerSpot reviewer
CTO at a tech services company with 11-50 employees
Real User
A free comprehensive solution to build applications with low entry barrier
Pros and Cons
  • "Microsoft .NET Framework reduces the cost of entry and enables the development of applications with mature and enterprise features, thereby lowering the entry barriers."
  • "The learning curve could be improved."

What is our primary use case?

I work in the supply chain and transportation space. NET Framework is the core part of the technology stack. We had to build everything, including the Windows system.

We could spend more time building the application than building the framework. We've been using it since V1, and .NET has grown and changed multiple times in different directions. It brings more to the table each time, so we need to build less and less. If you think about containerization, you get that from the .NET framework.

What is most valuable?

Microsoft .NET Framework reduces the cost of entry and enables the development of applications with mature and enterprise features, thereby lowering the entry barriers.

What needs improvement?

The learning curve could be improved.

For how long have I used the solution?

I have been using Microsoft .NET Framework since its inception.

What do I think about the stability of the solution?

The product is stable.

What do I think about the scalability of the solution?

The solution’s scalability is good. We use the .NET Framework as a stack component in our project to develop software. Everyone from cybersecurity personnel and architects to customer service support uses this application.

How are customer service and support?

There is a community providing solutions. Many others encounter the same issue with .NET and search for solutions online through Google.

How would you rate customer service and support?

Positive

How was the initial setup?

The initial setup is very easy. We can usually get something spun up and running in a day.

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

The product is free.

What other advice do I have?

Microsoft .NET Framework is a framework for development. We use cryptography, messaging, and many other components the platform provides for our development work. We are prototyping with the latest framework, which includes a mixed model of HTML rendering. This model is a blend of client-oriented applications, where most tasks are performed in the browser, and server-side applications, where the server renders the HTML for the web pages. The latest offering simplifies administration and development for simple pages while enabling the creation of highly interactive pages resembling control screens and back-office control centers.

We've used ASP.NET to create web UI. You might have business rules and logic running on your server. You have databases and frameworks for interacting.

We use C# and VB.NET on the backend and SQL for the database. The platform is good at implementing standards for web services. With .NET, there are competing standards, depending on whether it's coming from Microsoft or Oracle. The platform is very good, providing standards-based programming models.

The ease of finding and using third-party libraries with the .NET Framework is extensive. We use some libraries, but many more are available.

A single person is enough for the solution's maintenance.

The .NET Framework requires maintenance like any other deployed software, with patches and updates being essential to maintain. It's important to stay updated and evaluate these patches as they often address security threats. One of the major security risks in the .NET environment arises from using outdated software with known exploits. For instance, a vulnerability discovered in a particular version becomes a security risk until patched. In such cases, a patch is released, and while most companies apply it promptly, some may lag, leaving them vulnerable to attacks. These unpatched systems become easy targets for attackers, exploiting well-known vulnerabilities. Therefore, the patching process is crucial for maintaining security.

Overall, I rate the solution an eight out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
reviewer2168790 - PeerSpot reviewer
Technical Solutions Architect, Enterprise Architect at a tech services company with 11-50 employees
Real User
Top 20
A software development framework for building and running applications on Windows
Pros and Cons
  • "Firstly, I appreciate the decision to use Microsoft .NET Framework. I find it to be an excellent language, with a history rooted in providing an alternative to Java, albeit with initial challenges. It is gaining popularity and may be voted the most desirable programming language. What I particularly like about .NET is its language efficiency. While C# is the primary language, the platform also supports others, catering to those inclined towards functional programming. Although I started with Shell, I'm still grasping the concept of functional programming. Despite initial reservations about object-oriented programming, I acknowledge its advantages. .NET is a safer option, and despite criticisms, it has evolved over the years. One notable aspect is .NET's transition to an open platform in recent years, distancing itself from being exclusive to Microsoft engineers. I appreciate the versatility of .NET, enabling code production for a wide range of platforms, presenting a strong competition to Java. It allows targeting practically any physical platform, showcasing its flexibility. These qualities contribute to my positive view of .NET, totaling thirteen aspects that I find appealing."
  • "In the realm of Microsoft .NET Framework, particularly in the C# language, there have been significant developments that I find highly commendable. I am genuinely fascinated by the continuous evolution of the language, and staying abreast of the latest features in Azure is both challenging and enjoyable. Working with C# in Azure is particularly fantastic. I appreciate in .NET, as compared to Java, is the enforcement of types, providing a better experience in terms of technicalities. Additionally, the introduction of Roslyn in the past few years has brought about the concept of late .NET, which I find interesting and powerful. This allows for the transformation of symbolic code just before execution, eliminating the runtime decision-making process and enhancing efficiency. However, late .NET does come with a drawback – a delay in the last-minute computation when starting an executable. While some may find this less appealing in terms of instant responsiveness, especially in serverless cloud environments, the efficiency gained from executing strictly binary code is valuable. Despite potential drawbacks like the time required for activation, I view .NET favorably for its technical advancements and efficiency, especially in scenarios such as serverless cloud computing. It's essential to recognize the intricacies of how .NET processes code and the efficiency it brings, which some may overlook."

What is our primary use case?

I am currently working on the development of a new product using Microsoft .NET Framework. The project is currently in the analysis, architecture, and user acceptance phases. It is a comprehensive system similar to ERP, designed to manage internal resources for a sizable bank. The application focuses on handling IT resources for the bank, and it is being developed in-house.

How has it helped my organization?

Within each specific .NET product of ours, we currently have a robust portfolio with around a dozen products actively running for our customers. Based on the user databases, it's evident that each product is implemented using .NET. In fact, one of our products boasts slightly over one thousand users. This underscores the prevalent use of .NET across our product range.

What is most valuable?

Firstly, I appreciate the decision to use Microsoft .NET Framework. I find it to be an excellent language, with a history rooted in providing an alternative to Java, albeit with initial challenges. It is gaining popularity and may be voted the most desirable programming language. What I particularly like about .NET is its language efficiency. While C# is the primary language, the platform also supports others, catering to those inclined towards functional programming. Although I started with Shell, I'm still grasping the concept of functional programming. Despite initial reservations about object-oriented programming, I acknowledge its advantages. .NET is a safer option, and despite criticisms, it has evolved over the years.

One notable aspect is .NET's transition to an open platform in recent years, distancing itself from being exclusive to Microsoft engineers. I appreciate the versatility of .NET, enabling code production for a wide range of platforms, presenting a strong competition to Java. It allows targeting practically any physical platform, showcasing its flexibility. These qualities contribute to my positive view of .NET, totaling thirteen aspects that I find appealing.

What needs improvement?

In the realm of Microsoft .NET Framework, particularly in the C# language, there have been significant developments that I find highly commendable. I am genuinely fascinated by the continuous evolution of the language, and staying abreast of the latest features in Azure is both challenging and enjoyable. Working with C# in Azure is particularly fantastic.

I appreciate in .NET, as compared to Java, is the enforcement of types, providing a better experience in terms of technicalities. Additionally, the introduction of Roslyn in the past few years has brought about the concept of late .NET, which I find interesting and powerful. This allows for the transformation of symbolic code just before execution, eliminating the runtime decision-making process and enhancing efficiency. However, late .NET does come with a drawback – a delay in the last-minute computation when starting an executable. While some may find this less appealing in terms of instant responsiveness, especially in serverless cloud environments, the efficiency gained from executing strictly binary code is valuable.

Despite potential drawbacks like the time required for activation, I view .NET favorably for its technical advancements and efficiency, especially in scenarios such as serverless cloud computing. It's essential to recognize the intricacies of how .NET processes code and the efficiency it brings, which some may overlook.

For how long have I used the solution?

I have been using Microsoft .NET Framework for many years, since 1992 or 1993. 

What do I think about the stability of the solution?

It is stable.

What do I think about the scalability of the solution?

I'm frequently questioned about the scalability of .NET products by the company owner. In response, I inquire about the specific aspect of scalability they are interested in. If the concern is about handling sudden surges in traffic, I affirm that .NET is indeed scalable, especially with the implementation of group health checks. This ensures automatic scaling without manual intervention, providing convenience.

Contrary to common misconceptions, I emphasize that the performance of .NET is typically not hindered by processing power but by factors such as disk I/O and database operations. Scaling the database differs significantly from scaling processing power, as it involves handling transactions, open transactions, and conflicting operations. If isolation is not well-implemented, issues may arise. For instance, a database like SQL Server, while appearing appealing a decade ago for its tools and affordability, presented challenges in terms of scaling compared to Oracle. Understanding these nuances is crucial for making informed decisions about scalability.

How are customer service and support?

Regarding customer support from Microsoft, I can say that when we documented issues and submitted tickets, Microsoft was responsive and open, even without direct contact. Working with Microsoft has generally been positive, and their strategic direction is something we have followed closely. Microsoft's commitment to evolving their product has been beneficial for us, even though the unpredictability of their decisions can sometimes pose challenges. In a small company like ours, adapting to changes becomes more complex, especially considering the project size.

As a company, we are also involved in software development for the European Commission, where the strong requirement is to use software from the .NET world. The challenge arises when dealing with Java in parallel, as its community processes add an element of unpredictability. Managing a team that can swiftly adapt to changing technologies is an advantage, but it requires time and effort. The unpredictability of Java's direction contrasts with the more foreseeable evolution of .NET.

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

We have had experiences with Oracle as well as .NET, specifically with the Silverlight framework, though that was some years ago. Silverlight, while not inherently bad, tends to be criticized, and I often advise people to understand its origin as the Presentation Foundation Everywhere (PFE), indicating its intention to provide a unified UI across various platforms. However, due to various challenges, it was eventually phased out, and Silverlight became obsolete. We once had a product active on SolarWinds 3.5, transitioned to SolarWinds Sorin, but unfortunately did not survive beyond Silverlight 5.

How was the initial setup?

Yes, it is easy. .NET has expanded its scope significantly. It's worth noting that while many may mention .NET, not everyone truly comprehends its intricacies. Nowadays, people often focus on microseconds, assuming they grasp the technical aspects, which can be misleading.

Although Continuous Integration and Continuous Deployment (CICD) may seem attractive for automated deployment, the allure of the cloud has somewhat overshadowed the significance of meticulous deployment, as it's often perceived as someone else's responsibility. This shift in perception, coupled with tools like CircleCI, requires a closer examination of their efficiency compared to more conventional platforms like Azure. Understanding the true speed and efficacy of these tools is imperative for making informed decisions.

What about the implementation team?

The shift in the deployment and maintenance is evident, as manual installations are no longer the norm. Intelligence is now directed towards automation, emphasizing the importance of testing. Once this process is completed, confidence in the system's functionality increases, alleviating concerns about manual loading and ensuring an automated and efficient workflow.

Everyone in our organization follows the mindset of having our proprietary tools. The majority of our internal tooling is developed in-house, making us predominantly a .NET-centric environment. While it's true that we also provide Java solutions, most of our confidence lies in .NET due to its reliability. Reflecting on past experiences, there were initial concerns about how autonomously and optimally .NET could run, especially in terms of memory management. However, over time, particularly with the introduction of .NET Core, those concerns have dissipated, and I am now completely confident in the reliability of .NET.

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

In the interim, there's no need to purchase videos for viewing. Microsoft has made significant moves in the .NET space, starting with their response in Visual Studio Code and now providing Visual Studio entirely for free. This is a notable shift from the past when we used to pay substantial amounts for technical subscriptions. Previously, a group of ten developers could cost several thousand dollars annually for licensing. However, the current trend is to offer these tools for free to maintain their dominance in the developer market. The market dynamics have changed, and now developers can freely download Visual Studio, making it a preferred choice over other paid options. 

What other advice do I have?

It has been around for about three months, and I've had a chance to delve into the capabilities. As for the .NET Framework, it's advisable not to use it anymore. While there might be some exceptional cases, I don't consider myself an expert on .NET Framework. The trend is shifting away from Framework towards .NET Core and now .NET 5. I would anticipate platforms to adapt and run seamlessly on the newer versions. Transitioning from Framework to newer versions might not be straightforward, particularly in terms of setup and configuration. Working with .NET Core involves a different approach, especially when dealing with configurations and influencing the product's behavior externally.

Switching everything from Framework to .NET Core in a short span may not be feasible, and even if you plan to do so, existing products and customer preferences may necessitate keeping the older products alive. Users may inquire about their familiar products, and it's essential to maintain support for them. Despite these challenges, I find .NET Core, particularly version 8.5, to be highly commendable. It excels in various aspects and is a robust platform, rating it 8.5 out of 10.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
reviewer1604244 - PeerSpot reviewer
Founder at a non-profit with 1-10 employees
Real User
Lacks adequate cross-platform performance and interoperability with AS400, but is the only viable solution for non-cross-platform tasks and works smoothly with Microsoft Technologies
Pros and Cons
  • "Microsoft Platform is the only viable solution when I wish to do something that is not supposed to be cross-platform."
  • "It is of great concern to us that the solution is not very powerful on cross platform, at it impedes the ability to build and scale with it."

What is most valuable?

I've been using the solution on the Microsoft Platform because it's very tied up with the Windows Server operating system, as it is with the Microsoft technologies. I would basically use the solution anytime that I wished to do something very efficient on Microsoft, building a software for example, which can be done on Microsoft Platform efficiently. I see the solution as the proper alternative to such programs as Java and Python. I prefer Microsoft.NET framework as it's actually tied with the Microsoft operating system and network.

So, the main advantage of the solution for me is that it's really tight. It starts with the component of the server side and proceeds to accessing the database. Work with it is really smooth with Microsoft technologies. There is no worry, no bother. Microsoft technologies is really straightforward.

Microsoft Platform is the only viable solution when I wish to do something that is not supposed to be cross-platform. This was the case later on with the .NET Core. Although we tried to obtain this on the Linux platform, we found things to be somewhat limited, as the .NET Core didn't mix very well with the Linux kernel. This is why we did not adopt it so much on Linux and prepared to do it with Python and Java, as the .NET Core was less powerful than the .NET Framework on Windows. As such, .NET Framework is better to use on Microsoft, on Windows Server. To me, Windows Server is actually the best when one wishes to do something for Windows Server but does not desire that it be cross-platform. It offers much integration. 

What needs improvement?

While Windows Server is always the best, the interoperability and, of course, cross-platform features could stand improvement. Ideally, the .NET Core should be made more efficient than it is at present. There is a need to be at the level of Java, for example, to truly overcome the weaknesses involved.

Price fraction on the Linux Platform and macOs Platform should also be taken into account. Then it will really be effective on those other platforms. 

It is of great concern to us that the solution is not very powerful on cross platform, at it impedes the ability to build and scale with it. There are many who would like to have their servers on Linux, since hosting Windows Server, even on VPS or in any hosting company, is very expensive. It will also be expensive in the long run. Keeping it secure will be expensive. It is cheaper and easier to get it secured, to get the best performances, with Linux. Most applications that our customer companies are using they wish to have on a server and then to access it from any type of tool, computer, or smartphone, which is what we would like for ourselves at the moment. Many are interested in the type of deployment whereby the application will be set on a server with web services.

For the .NET to really be at the level of some of the tools we are using now, it is better that Microsoft should start on the .NET Core so as to make it as powerful as possible on the main Linux distributions.

This would increase my rating of the solution.

If Microsoft could put the .NET Core at the level of the other platform I would even rate it as a nine out ten.

For the moment I can only give the product a rating of five out of ten since only some of the customers will be satisfied, those that have the financial resources for hosting a platform on Windows Server. They would need to finance a team that would work to keep everything running with security and to be capable of scaling up anytime they want. A dedicated strong team for this purpose costs money. 

While there are those companies that have the money and can afford this expenditure, others that don't will opt for the cheaper solution of using Linux, which has the potential for providing the same results. 

Moreover, I would like to have interoperability with AS400. We have not done many things with the .NET and prefer using certain other tools towards this end. When we want to work on AS400 we need to use some other tools for that on Windows. If Microsoft could resolve this issue it could attract a wider array of customers. We have very powerful software running on AS400, so the its interoperability capabilities are important to resolve.

For how long have I used the solution?

I have been working with Microsoft.NET Framework for 20 years and I have been doing so since its inception. After having switched to open source I then reverted back to the solution. I have been using it since it came out with its early versions. 

What do I think about the stability of the solution?

Microsoft has tested the solution and our experience with it has shown us that, while it is not as fast as some of our other software-devoted platforms, it is very stable. It's integrated with the platform and very stable on Microsoft Platform. There are certain applications we build on it which work very well and we do not experience downtime.

What do I think about the scalability of the solution?

The ability to build and scale with the solution is hampered by the absence of its cross-platform capabilities.

How was the initial setup?

There is a need to choose the version being worked on and to obtain its appropriate components, at which point the installation will proceed as it usually does for Microsoft products. This is the point where the person must click repeatedly. The PowerShell commands can then be used. The person is presented with all the other Microsoft questions upon installation. When we work with the Linux system, we primarily prepare for use of PowerShell. 

What other advice do I have?

I rate Microsoft.NET Framework as a five out of ten. 

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
AbdulHameed - PeerSpot reviewer
Assistant Vice President at ZTBL
Real User
Top 5
A reliable lightweight solution for application development
Pros and Cons
    • "The solution has difficulty integrating with other products. There are no such difficulties if you have the same platform, hardware, and operating system."

    What needs improvement?

    The solution has difficulty integrating with other products. There are no such difficulties if you have the same platform, hardware, and operating system.

    What do I think about the scalability of the solution?

    We have almost 15 developers using the solution. It has reliability.

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

    Microsoft .NET Framework is lightweight. I work on Microsoft and Oracle platforms. Microsoft platform is easy to start working on, whereas Oracle is very difficult. Troubleshooting is complicated, whereas it's very easy with Oracle.

    The maintenance of the Microsoft platform is very tough. You can start your development after three months of your start, but in the Oracle platform, it is not so easy. You will learn it; then you will start. There is no such difficulty when you start it. It is very easy.

    How was the initial setup?

    The initial setup is complex and takes time.

    When the development team deploys a new application, they prepare a new server. It is a very complicated task. It has dependencies.

    What other advice do I have?

    More than one person is required to maintain the solution.

    Microsoft .NET Framework is a mature application. More than 50% of applications are on .NET Framework.

    Overall, I rate the solution a ten out of ten.

    Disclosure: I am a real user, and this review is based on my own experience and opinions.
    PeerSpot user
    Maria Elizabeth Lopez - PeerSpot reviewer
    Software Engineer at a consultancy with 51-200 employees
    Real User
    Top 5
    An enterprise-grade platform that provides free online documentation
    Pros and Cons
    • "The most valuable thing about Microsoft .NET Framework is that it is an enterprise-grade language and platform."
    • "Microsoft .NET Framework has a steep learning curve, which could be improved."

    What is our primary use case?

    We use Microsoft .NET Framework for testing and development for RPE.

    What is most valuable?

    The most valuable thing about Microsoft .NET Framework is that it is an enterprise-grade language and platform.

    What needs improvement?

    Microsoft .NET Framework has a steep learning curve, which could be improved.

    For how long have I used the solution?

    I have been using Microsoft .NET Framework for five years.

    What do I think about the stability of the solution?

    Microsoft .NET Framework is a stable solution.

    I rate Microsoft .NET Framework a nine out of ten for stability.

    What do I think about the scalability of the solution?

    Microsoft .NET Framework is a scalable solution. In my previous job, around 20 to 50 users used Microsoft .NET Framework.

    I rate Microsoft .NET Framework a nine out of ten for scalability.

    How was the initial setup?

    The solution’s initial setup is easy.

    What about the implementation team?

    The solution takes only a few minutes or hours to deploy.

    Just one person is required for the solution's deployment.

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

    Microsoft .NET Framework is a free, open source solution.

    What other advice do I have?

    We don't maintain the solution because it's a framework that does not need to be maintained.

    I recommend users use the solution's online documentation because it's open and free.

    Overall, I rate Microsoft .NET Framework a nine out of ten.

    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
    Buyer's Guide
    Download our free Microsoft .NET Framework Report and get advice and tips from experienced pros sharing their opinions.
    Updated: February 2025
    Product Categories
    Application Infrastructure
    Buyer's Guide
    Download our free Microsoft .NET Framework Report and get advice and tips from experienced pros sharing their opinions.