We just raised a $30M Series A: Read our story

Microsoft .NET Framework OverviewUNIXBusinessApplication

Microsoft .NET Framework is #2 ranked solution in top Application Infrastructure tools. IT Central Station users give Microsoft .NET Framework an average rating of 8 out of 10. Microsoft .NET Framework is most commonly compared to Apache Web Server:Microsoft .NET Framework vs Apache Web Server. The top industry researching this solution are professionals from a comms service provider, accounting for 27% of all views.
What is Microsoft .NET Framework?
.NET Framework is a software framework that runs primarily on Microsoft Windows. It includes a large class library named Framework Class Library (FCL) and provides language interoperability across several programming languages. Programs written for .NET Framework execute in a software environment named Common Language Runtime (CLR), an application virtual machine that provides services such as security, memory management, and exception handling. FCL and CLR together constitute .NET Framework.

Microsoft .NET Framework is also known as MS .NET Framework.

Microsoft .NET Framework Buyer's Guide

Download the Microsoft .NET Framework Buyer's Guide including reviews and more. Updated: November 2021

Microsoft .NET Framework Customers
Curtin University, Rockwell Automation, Aruba Networks, Insurity Inc., City of Barcelona, Pennsylvania DCNR, University of Petroleum and Energy Studies, A1 Telekom Austria AG, Eastman Chemical Company
Microsoft .NET Framework Video

Pricing Advice

What users are saying about Microsoft .NET Framework pricing:
  • "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."
  • "The pricing could be cheaper."
  • "There is a Community Edition that can be used free of charge, but the licensing cost for the Enterprise version is quite high."
  • "The Microsoft .NET Framework is free of charge, without licensing cost."
  • "If you want to develop an enterprise-level application, you have to purchase the enterprise-level development license."

Microsoft .NET Framework Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
SK
Founder at a non-profit with 1-10 employees
Real User
Top 5
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
Flag as inappropriate
RE
Solutions Architect
Real User
Top 20
A easy program language that works well in Linux environments and is easy to implement

Pros and Cons

  • "Basically, .NET is simply is the easiest programming language to use, based on my experience."
  • ".NET Is still heavy or dependant on other Microsoft libraries and frameworks."

What is our primary use case?

Our development tools, our platform, every solution we've developed, most of them are Microsoft products. So we're using .NET. 

Almost all of our enterprise applications are developed within that whether it will be reading those applications, web applications, or a background service, etc. Of course, there's a different case when it comes to our mobile application. We're quite open-minded and like to explore other frameworks due to the fact that there has been a lot of frameworks getting more popular nowadays.

What is most valuable?

I have very diverse experiences in most of the major programming frameworks, whether it is DHP, Java, etc.

Basically, .NET is simply is the easiest programming language to use, based on my experience. It has flaws, however, the performance and agility are much better compared to other programming languages.

They've done a lot in the past few years. You can see this especially in the fact that they allowed .NET to be run in Linux environments.

What needs improvement?

For .NET, what I can say is that maybe it needs adaptation of a more streamlined function. What we can see is vital is a simple programming model. However, .NET Is still heavy or dependant on other Microsoft libraries and frameworks. Therefore, although they're going there, they're already open-source for that network. There are lots of improvements that can be done there within that industry.

For example, .NET support needs to offer big data similar to Mongo DB or to the other big data technologies. It's still in its infancy from I've experienced. When it comes to the big data or data science fields, I think .NET framework has a lot of things to hash out.

Another item worth improving in .NET is support to Mac. There's still a lot of grey areas when you use a Mac. There's a lot of instability when it comes to that OS. .NET programming language will be very difficult to compete with when they fully jump into the Apple territory.

For how long have I used the solution?

I've been dealing with the solution for probably more than ten years. I've been using .NET since the beginning when it was .NET 1.0. Therefore, I believe it's been more than a decade.

What do I think about the stability of the solution?

The solution is stable. Aside from issues surrounding using Macs, it's not too glitchy. It doesn't freeze. It's pretty reliable.

The biggest problem with programming language nowadays, because there are a lot of things happening, is that changes happen too fast. Due to the competition, they tend to release new features almost every week. I don't think there's an exception on that one. In return, the application framework can have bugs in it. 

What do I think about the scalability of the solution?

Nowadays when it comes to scalability performance, it's in the hand of the programmers. It's not in the framework. Even if you're using a very efficient or powerful framework, if that application was developed improperly, it just makes everything else shakey. If the framework is there to help you to do the best practices and apply everything, .NET is still really good at doing that, compared to other frameworks. Almost everything is bootstrapped or is ready for you to use, unlike other frameworks like Java. You have to develop everything to make sure that it is able to address the issues. In .NET it's pretty straightforward.

How are customer service and technical support?

If we contacted technical support it may have been a long time ago. Nowadays, it's rare to go directly to support. For the most part, all you need to do is Google your queries and you can find the answers yourself.

How was the initial setup?

The tool itself, in terms of the initial implementation, is pretty straightforward. The tool will do everything for you, unlike other programming languages where you have to install these different dependencies, et cetera. 

What other advice do I have?

We're just a customer.

We use multiple deployment models. I'm using Azure Dev Ops for my previous projects, but for my company, we're using Jenkins to deploy our applications.

The good thing with the .NET framework is that it allows you to develop an application faster and in a professional way. The downside is that it's different due to the fact that it's abstract. It's different from every other program. You really need to know the fundamentals of software development. That's the downside. Using .NET You will be able to develop many applications without really knowing what the inner workings of that application are. Compared to Java, or C++ where you should be able to know every fundamental of every foundation, you don't need that deep knowledge with .NET. If there will be a trainee or entry-level person on the program, I suggest they study first computer programming fundamentals, maybe in Java or another more engineering-oriented programming language before they go deeper into the .NET framework. Or they should at least do their homework to learn those things.

Overall, I'd rate the solution eight out of ten. If they slowed down a bit with the new releases and made sure they were bug-free before releasing them, I might rate it higher.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Learn what your peers think about Microsoft .NET Framework. Get advice and tips from experienced pros sharing their opinions. Updated: November 2021.
552,305 professionals have used our research since 2012.
AndreasSemousu
Project Delivery Manager at Skhomo Technologies
Real User
Top 10
Cross platform development that is user-friendly and has good support

Pros and Cons

  • "When it comes to the user interface, the context is better than other tools because it is easier to use."
  • "They should have more training materials available that are specific to .NET. We spend a lot of money training our engineers."

What is our primary use case?

We are working with version 2019, but we have clients who are still on older versions. We deployed the solution in 2014 or 2015 and they still haven't upgraded.

What is most valuable?

Cross-platform development is better than all of the other frameworks. When it comes to the user interface, the context is better than other tools because it is easier to use. You can still use C# in the developer infrastructure, which makes it far better and you don't have to learn a new language.

For me, the cost is what is most important. We have an agreement with Microsoft to co-sell some of the applications. When we started developing using the Microsoft Framework, it went well because we started making more money than the cost to Microsoft. We don't have this agreement with Red Hat or JBoss.

One thing that I like is that from the usability point of view, nothing has changed all that much. We use Visual Studio and if you compare the older version of Visual Studio from 2013 to the 2019 edition, the scale is still there. You're not moving to a different environment and you are still able to find your way around very quickly. With the new features, we are still able to feel those out within a short period.

For the mobile application, I like the iOS interface. Android is a little different from what you have on iOS, but the iOS package includes the same thing.

What needs improvement?

The pricing could be cheaper.

They should have more training materials available that are specific to .NET. We spend a lot of money training our engineers. I think that it would be better if there was more training available to the partners who invest in Microsoft.

At this time, the training is all over the place and there is no specific certification.

This solution is not scalable with older versions without using patches for it to work.

For how long have I used the solution?

I have been working with this solution for more than ten years.

What do I think about the scalability of the solution?

Microsoft's strategy is not scalable, especially with the Visual Studio environment. If for example, I am testing things from on older version, it's not available in the newer version. You will have to use notes and the patches for it to work.

Currently, we have two enterprises. One of them has over 1000 employees and an IT department with 200 developers.

How are customer service and technical support?

The technical support has been excellent. If you are working with them, they are always there to connect with you all the way, which makes things so much better.

The first day takes a couple of hours and the second day is for the configuration and switching everything out to make sure that everyone has access to it. Then they test everything to make sure that it is fine and working. It's not a lot of work for us to do.

The support has been very good, maybe because we have a local office with resources.

Some of the issues with support is not with .NET, it's dealing with some of the packages that should offer support. One of the new products that Microsoft has introduced is called Dynamics 365, this is outside of .NET. We have been struggling to find someone for support, but unfortunately, it has to be through the US.

When it comes to everything else, the .NET Framework has a lot of support from the local Office.

If they struggle with .NET there is someone in the UK office that would be able to assist us.

How was the initial setup?

The initial setup is easy for our guys who spend quite a bit of time with Microsoft.

Just today, one of the guys set up an environment for one of our clients on Azure. This was a Visual Studio environment and it took him two hours. He did not encounter any difficulties. 

What about the implementation team?

We have guys take care of the server section and we have our developers that implement from the installation for the environment.

It seems very easy for them to get everything up and running.

What other advice do I have?

Small clients don't do their development internally. We have three of these types of clients. Small to medium-sized organizations don't have an environment because they are easy to develop with easy requirements.

I would recommend this solution but it depends on the environment and what they want to do.

If you do mobile applications, to avoid the headaches of doing development on multiple platforms, I think that .NET is something that really works. We have tried everything, so when we try iOS it becomes a problem because we have to re-develop what you do for Android on iOS, even though we don't use Windows phones anymore. We can still use the same tools for your desktop applications.

If you have a different environment then you have to develop based on whatever application you are going to run your application on. 

I would rate this solution an eight out of ten.

Which deployment model are you using for this solution?

On-premises
Disclosure: My company has a business relationship with this vendor other than being a customer:
Ashish-Kamat
Senior Manager at a tech services company with 10,001+ employees
Real User
Top 5
A mature development platform with a helpful IDE and extensive documentation

Pros and Cons

  • "The .NET framework is a mature platform that is very helpful and saves time during the software development process."
  • "If Microsoft would provide a monthly subscription at a cost that a developer can afford then it would be really helpful."

What is our primary use case?

We are part of the development team.

We use this solution with TFS as our ALM tool, and we use the information server for the deployment.

How has it helped my organization?

We have been using this solution for development for a long time and it has proven to be helpful.

What is most valuable?

The .NET framework is a mature platform that is very helpful and saves time during the software development process.

The IDE is quite helpful.

There is a lot of very extensive documentation available.

What needs improvement?

The price of the Enterprise version is quite high and can be improved. If Microsoft would provide a monthly subscription at a cost that a developer can afford then it would be really helpful.

From a security standpoint, the tools are not that mature.

For how long have I used the solution?

I have been using the Microsoft .NET Framework for more than 25 years.

What do I think about the stability of the solution?

This is a very stable platform for enterprise development. It has been maturing since its inception and is very helpful for delivering products.

How are customer service and technical support?

We have dealt with the technical support team and they are very helpful. Whenever there are issues, especially when troubleshooting in a production environment, Microsoft and the support people provide a lot of technical expertise and we are very happy with it.

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

This product is really helpful when compared to other solutions such as open-source platforms. All of the tools are interlinked, rather than having individual tools for individual features. What Microsoft provides is a complete tool, with all of the features contained.

How was the initial setup?

The initial setup is easy. There is a vast amount of resources made available by Microsoft and a lot of guidance being provided to the developers. 

What about the implementation team?

I lead a development team and the team members perform the deployments. There is a lot of guidance available on the Microsoft website that is really good, so the deployments are not troublesome.

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

There is a Community Edition that can be used free of charge, but the licensing cost for the Enterprise version is quite high. Some of the tools that are available in the Community Edition need a valid license to run.

Compared to other vendors, Microsoft products definitely have a higher price tag. I would say that is my only grievance.

What other advice do I have?

Talking from an application developer's perspective, this platform is very helpful because it provides a common development line across all of the products that Microsoft provides. This includes things like Microsoft Dynamics, the Cloud Integration tool, and SharePoint. It makes it very easy to jump from one application tool to the other.

The Community Edition can be used free of charge and is helpful for both new developers, as well as those who are shifting to the Microsoft platform.

Over time, this product has matured and all of the new features have been helpful in improving the performance of application developers. Overall, we are very satisfied with using this platform for application development. It is very good. That said, there is always room for improvement.

I would rate this solution a nine out of ten.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
Syed Fahad Anwar
Principal System Developer at a government with 51-200 employees
Real User
Top 5Leaderboard
Great all in one framework with extensive stack for web applications, windows applications and mobile applications.

Pros and Cons

  • "The most valuable features for us are web frameworks like MVC, Web API, and WCS."
  • "I would like to see more pre-built features in the MVC framework because as it is now, it's very open and you have to develop your own controls in order to use it."

What is our primary use case?

Our primary use case is custom business applications, Integration services using WCF/Web API.

How has it helped my organization?

Using this framework has enabled us to create services out of things things that we used to do manually. Not only has it made our lives easier, but it has increased productivity as well.

What is most valuable?

The most valuable features for us are web frameworks like MVC, Web API, and WCF.

What needs improvement?

I would like to see more pre-built features in the MVC framework because as it is now, it's very open and you have to develop your own controls in order to use it. It would be much easier for us if there were more pre-built controls.

There should be more security features included.

The performance should be improved.

The technical support is in need of improvement to make solving issues more efficient.

For how long have I used the solution?

I have been using the Microsoft .NET Framework for more than 16 years.

What do I think about the stability of the solution?

This is a very stable solution and we haven't had any issues.

What do I think about the scalability of the solution?

This is a scalable framework but it depends on how you deploy the solution. Because it is a framework and not a product, it will give you options on how to develop your solution. If you develop it in a way that is scalable, then it will be scalable. But if you don't develop it properly then it will not be scalable.

In my previous company, we had approximately ten thousand users.

In my current company, we only use this solution internally. We have fewer than ten people, and they are business users. We do not currently have plans to increase usage but it may happen in the future.

How are customer service and technical support?

On a scale from one to ten, I would rate Microsoft technical support a seven.

Whenever we are trying to solve issues by dealing with Microsoft, they ask so many irrelevant questions that it delays things.

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

We are also using WebLogic Suite with SharePoint on the server-side.

How was the initial setup?

The initial setup was straightforward and the deployment took not more than two to three days.

What about the implementation team?

We implemented this solution using our in-house team.

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

The Microsoft .NET Framework is free of charge, without licensing cost. The only cost is purchasing the hardware that it runs on.

Which other solutions did I evaluate?

Java SDK. Java SDK is also good but require little bit more effort.

What other advice do I have?

My advice for anybody who wants to use the Microsoft .NET Framework is to have the proper foundation before implementing the solution. This means that they should lay the architecture first, properly, and then develop the solution based on the architecture. Without this, the solution will not be scalable and will suffer from problems in the long run.

This is a good solution but there is always room for improvement.

I would rate this solution a nine out of ten.

Which deployment model are you using for this solution?

On-premises

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

Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
YasirMehmood
Software Engineer at a mining and metals company with 10,001+ employees
Real User
Top 10
Easy modular development with good technical support, but the features could be enhanced

Pros and Cons

  • "As we are a software company, we find that accessing resources using this technology is easier compared to the others."
  • "In the next release, I am looking for more advanced technologies such as socket communication and enhanced features like realtime chat with the clients."

What is our primary use case?

We are a software company, and we build software. This is one of the solutions that we use in our development environment.

I have a profound handle on Microsoft. Net Framework.

What is most valuable?

As we are a software company, we find that accessing resources using this technology is easier compared to the others.

What needs improvement?

The main obstacle in this technology is that it is currently paid. If you want to develop an enterprise-level application, you have to purchase the enterprise-level development license. I think that this is a hurdle. If it is made free then more people will learn and the industry will have more proficient people with better performance.

In the next release, I am looking for more advanced technologies such as socket communication and enhanced features like realtime chat with the clients. This is what I have been looking at adopting into my existing application.

For how long have I used the solution?

I have approximately six years of experience with Microsoft .NET Framework.

What do I think about the stability of the solution?

This solution is stable if the logic is handled sufficiently. It all depends on what kind of coding you are doing while you are developing the application.

What do I think about the scalability of the solution?

This solution is scalable. The modular development plus expansion is quite easy.

We have 2000 users who are actively using this solution.

How are customer service and technical support?

When we contact technical support, we open a ticket with the vendor, who then assigns us to a person. We meet to discuss the technical challenges we are facing and they come up with a solution.

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

Previously, we were using the IBM integration bus.

We were using Microsoft, Mobility Android, and iOS applications.

Most of my experience is with Microsoft solutions.

How was the initial setup?

The initial setup was quite easy. The installation itself is easy. The prerequisites are already available on the internet.

It is a two-step deployment, the first being the development environment. The installation of that took between one hour and an hour and a half. For the processing, the deployment was a little bit different. I needed the information server hosting the Microsoft application.

While it's on a public cloud, some are on-premises that are accessed by the application.

We have a team of ten to maintain this solution. There are several internal connections to the system. For example, an interface with the other system which included SAP, Oracle, and IAD. The team looks for support queries that include any issues found or for any troubleshooting that needs assistance.

What other advice do I have?

There are proper resources. Stability and scalability are quite good. We handle 3000 to 4000 users at any time and they are users from all over the world, including North America, Australia, and the Middle East. This is a good option for the level of the audience.

We are using version 4.5 but we are gathering a few more projects that are running on version 4.7 and 4.8.

I would rate this solution a seven out of ten.

Which deployment model are you using for this solution?

Public Cloud

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

Microsoft Azure
Disclosure: I am a real user, and this review is based on my own experience and opinions.
GN
Associate Director at a computer software company with 10,001+ employees
Real User
Top 20
Great customization and consistently delivers in enterprise-size companies

Pros and Cons

  • "Proven solution with valuable customization."
  • "Lacking in auto-scaling."

What is our primary use case?

Our primary use case is generally for clients that are enterprise-sized businesses like insurance companies or bit telecom companies in the US. They are generally the customers that use this solution and my company provides services to them. Our work is related to putting the solution together and implementing the whole thing end to end. A lot of companies are moving towards the cloud, so either it's AWS or Azure or Google. Google is not as popular as AWS, followed by Microsoft Azure. And of course there are a lot of products on Microsoft which are also popular like their database and of course the Windows server and things like that.

We're a partner of Microsoft and I'm the associate director of our company.

What is most valuable?

The most valuable features are the customization and the support moving towards a .Net framework.

What needs improvement?

Nothing in particular comes to mind in terms of improvement. It's a proven solution and it really depends on the resources that a company has for maintenance once a solution is in place. That said, it would be good if auto-scaling could be included. I also believe implementation could be simplified.

Microsoft has got a lot of products and improvements would be in the context of a particular product. I've seen there are areas that are much harder to capture - so things like auto scaling and implementation could be improved. 

For how long have I used the solution?

I've been using this solution for three or four years. 

What do I think about the stability of the solution?

It's a stable solution. 

What do I think about the scalability of the solution?

It's a scalable solution. 

How are customer service and technical support?

The technical support is good and they also have some community forums where people can get quick responses to some of the queries that they have. So the community is good.

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

I"ve used Java previously and find it a more portable solution. 

How was the initial setup?

Initial setup is somewhat complex and requires some training. I would say that Microsoft can  improve on that somewhat in terms of enabling someone to understand the process and set it up themselves.

What other advice do I have?

I would definitely recommend that anyone considering implementing the solution do a proof of concept. That gives you an idea as to whether you're on the right path. A company also needs to take into account the requirements of their organization in terms of scalability and ease of maintenance and also whether they have the skill set to maintain the IT resources required. A lot goes into it but proof of concept would be good before going ahead.

I would rate this product an eight out of 10. 

Which deployment model are you using for this solution?

Hybrid Cloud

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

Amazon Web Services (AWS)
Disclosure: My company has a business relationship with this vendor other than being a customer: partner
David Shlingbaum
IT Development Manager, Architect, Developer at a tech company with 11-50 employees
Real User
Top 10
Rich libraries and very good development tools are key to this great solution

Pros and Cons

  • "Ease of use, the richness of the libraries and basically very good development tools."
  • "The .NET open source community could be larger."

What is our primary use case?

Basically all my development work is done with .NET Framework. It's web services, data processing, get web APIs, and also web development. I work as an IT development manager and am also an architect. 

What is most valuable?

The ease of use, the richness of the libraries and basically the good tools are all valuable features. Most important are the very good development tools that Microsoft has, it's a good environment.

What needs improvement?

Things could always be a little easier and smoother. You'll sometimes find bugs but because I'm using an older version these bugs have already been fixed in later versions. The .NET open source community is very small and it would be nice if it were larger. I know Microsoft is now contributing a lot, but in other languages there's not too many frameworks that are not Microsoft. It would be good to have a richer environment for that.

The solution could include an open source framework as an additional feature, I can't think of anything else. 

For how long have I used the solution?

I've been using the solution for a total of about 15 years, although I had a break from it for a while.

What do I think about the stability of the solution?

The stability is fine. 

What do I think about the scalability of the solution?

I think scalability is more a matter of architecture. One of the things possibly missing is, as already mentioned, open source framework. You can use Kubernetes or something called Orleans but there's not too much richness in that area, but there are solutions. Scalability is a matter of architecture, it's not a matter of programming language.

How are customer service and technical support?

I have an option for technical support but haven't used it. I generally find my solutions on the internet. 

How was the initial setup?

The new versions are really, really easy and smooth and they get their updates. I'm migrating now from an older to a newer version and the setup is very easy. The old version had some glitches. I think the setup of the tool is fairly easy.

What other advice do I have?

My advice is that C# is a very rich language with lots of advanced facilities, which makes it easier to develop by not being too complex. There are a lot of libraries in out-of-the- box .NET Frameworks, which gives you tools to do almost anything you need and there are extension libraries for most of the rest. It's not the same as Python which is a bit slower but has a lot of libraries because everybody writes libraries for Python. But most of the time I find what I need.

I would rate this product a 10 out of 10. 

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.