Microsoft .NET Framework Reviews

We design solutions for different applications and we use .NET core for the solutions' web portals. We primarily use .NET core for the back end of our services.

In my opinion, the best thing about Microsoft .NET is the fully featured framework. It provides most of the things which a normal developer requires of any application out of the box. There's also a great Microsoft community and support with the frame. Another important thing is that the latest versions are platinum diagnostic, which is quite valuable.

In my opinion, this solution can be improved by providing out-of-the-box support for different types of libraries.

I have been using this solution for about 10 to 15 years now.

My impression is that this solution is stable.

My impression is that this solution is scalable.

We have contacted their technical support many times. I would rate them a 10, on a scale from one to 10, with one being the worst and 10 being the best.

My impression is that this solution is not complex to set up. Installing .NET usually takes only a few minutes. If you go for full-fledged and more components, it may take longer.

If you want to go for development, there is an open-source ID call at video studio code. If you want to go for enterprise development, then there is a video studio professional or enterprise, which is a little costly for an individual. I think individual developers can do this work free of coupons. They don't need to pay anything to Microsoft for that.

I am working as a consultant for this solution for various companies.

I would recommend this solution to other people.

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

I work on the C#, ASP.NET, SQL Server, and others. I am also developing some scripts for my RPA solutions when needed. 

Microsoft .NET Framework has introduced many new features, making the technology very vast. In particular, they have a very good Visual Studio environment to do development.

The solution is not limited in storage, is customizable and simple to use.

I would like to see a better response time from the technical support.

This is a stable solution.

Microsoft .NET is scalable.

My experience with Microsoft technical support is that they can be difficult to reach. The support depends on the contract between the client and the company. 

Positive

Microsoft .NET has both open source and licensing options. Microsoft Framework and Visual Studio are licensed however, they have introduced .NET Core which is open source. In .NET Core, you will find Angular which is open source.

I would rate Microsoft .NET Framework a nine out of 10 overall.

I have been using the tool mostly for building web applications. Azure’s cloud integrations are pretty good.

The project that I worked on was a legacy application. It was pretty easy to use once we learned about the stack and understood the MDC architecture well. The product incorporates ML features and is continuously improving its features. The learning scale is good. We need a scalable website if we want dynamic web content for more than 5000 users.

In-built refactoring and .Net profilers are the most valuable features of the solution. We can use any language. We can use the product’s compiler to generate an intermediate language. Currently, the solution is becoming platform-independent. MAUI is not a specific platform or environment.

Since the product belongs to Microsoft, users trust it. The scalability of the applications built into the solution is pretty good. It can handle much workload. Microsoft keeps improving its tool stack based on market updates. It incorporates artificial intelligence and machine learning features. The solution also provides content embedding and multi-factor authentication.

It is not a pretty compact product because of the assemblies that are being loaded. The cloud features must be improved. The deployment must also be improved.

Automatic code completion and natural language processing would be a good addition to the tool. I'm not sure whether these features are already present.

I have been using the product for the last five years. From 2018 to 2020, I have been using versions 4.5 and 4.6.2. After 2020, I moved to .NET Core 3.1.

The tool’s stability is good. I rate the stability a seven and a half out of ten.

I would rate the tool’s scalability a seven or seven and a half out of ten.

The support is good.

Positive

The initial setup was straightforward. Large-scale deployments are done on Azure’s cloud, and it's easy.

I definitely see a return on investment.

The product’s pricing is a bit high. It's not an open-source tool. Organizations prefer the enterprise edition. Though there are some restrictions, developer versions are useful for learning purposes.

The product has to compete with Spring Boot.

People wanting to use the solution must learn the basics as much as possible and explore and utilize the features. Overall, I rate the product an eight out of ten.

We use Microsoft .NET Framework for custom application development.

Microsoft .NET Framework’s most valuable features are web application development, RESTful services development, security, performance, and less memory footprint.

The product’s reliability needs improvement. There could be fewer footprints for compiled code. Additionally, its memory management could be better. The performance should be increased as well.

We have been using Microsoft .NET Framework for eight to ten years.

It is a stable platform. Although, we encounter memory consumption issues when there are a lot of concurrent requests. It should give error messages when it is about to reach the capacity limit.

The scalability depends on the architecture of the custom application.

We don’t need to contact Microsoft as many technical forums and tech programs can help and guide us with any issues.

The product’s initial setup process is not complicated. Although, you need to have technical expertise for implementation. The time taken for deployment depends on the project requirements. For a complex project, it takes one to two days. Whereas for a simple application, it takes a few hours. It requires two to three executives for deployment and five executives, including admins, engineers, and developers, for maintenance.

The product can be deployed in-house by getting guidance from the Internet.

Microsoft .NET Framework is free of cost. Microsoft also provides its open-source version. One can quickly deploy it if they have a server license. 

J2EE Framework is good but complicated to deploy and requires more skills. It is not straightforward compared to Microsoft .NET Framework.

I advise others to hire technical expertise or learn the technical aspects to understand the product. It will help them leverage all the features.

I rate it a nine out of ten.

I use this framework to create backend services or work with data lakes.

The .NET Framework is easier to use because it provides a lot of libraries. I find it very useful. The difference, for example, with the .NET Core framework from Microsoft is that it's an open-source library and runs on multiple platforms.

There is room for improvement in the setup process and the support. 

In this technology, I have four years of experience. In my current organization, I create an API solution using the Microsoft .NET Framework for my microservices. I use .NET Framework 4.7 and 3.0. Both versions can serve as the core.

It's stable.

I create API solutions and web apps. Microsoft .NET Framework can be scaled. I have a solution that is designed for implementing transactions.

The initial setup is a bit complex. I would rate my experience with the initial setup a seven out of ten, with ten being the most complex.

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

I use the product only for automation.

Our usage was limited. Microsoft .NET Framework is a good investment.

The solution is technical. A new user cannot use it. The solution is difficult to learn if someone is learning it for the first time. It is difficult for non-technical people.

The tool was stable.

Around 20 to 25 developers used the tool in our organization.

The solution was deployed by the vendor.

Only developers can use the tool. We have used Microsoft .NET Framework for web-based applications. If someone is planning to use the tool for the first time, they must learn the basics of .NET. They must go through some manual or training. The solution is easy to use if the user is a developer or some technical person. It’s a good application. Overall, I rate the product a six to seven out of ten.

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. 

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.

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. 

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

The stability is fine. 

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.

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

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.

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. 

I use the solution in my company to build internal systems that are used for developing applications to run our business, and we also use it to call web services.

The most valuable component of the product stems from the fact that it works properly. I know it might sound funny, but you don't have to go and get other third-party solutions when using Microsoft .NET Framework. With Microsoft .NET Framework, you also don't have to do a whole lot of extra configurations to make it run. The tool offers a lot of support, and there is a lot of knowledge material available, along with a lot of community groups. If you have an issue with the tool, you can find someone to help you pretty easily.

I think the main thing that my company wants is Microsoft .NET Framework to provide us with more integrations with Azure, like in the area of DevOps in Azure, which can improve its management and work in the cloud. The tool is good, but it can be made a bit better.

The product's price is an area of concern, making it an area where improvements are required. The product should be available at a low cost.

I have been using Microsoft .NET Framework for about fifteen years. The older version of the tool is automatically updated.

I have not faced any issues with the stability of the product.

Considering what cloud services can support, the scalability offered by the product is unlimited. I feel that it is a scalable solution.

My company has around 12 to 15 developers who use the product.

In terms of the size of Microsoft .NET Frameworks' environment, I feel that as a cloud-based product, it serves as a system to the customers, so it can serve the needs of hundreds of customers, meaning there are no real size limitations. The on-premises version of the tool that our company has been running had 350 people running through the applications on-site, and it was running every day with thousands of daily transactions.

I believe that the developers in my company have raised issues with the product's support team. I believe that it was never a challenge for my company to find the right person who provides the right solutions. My company has dealt with difficulties in a few technical areas attached to the solution, especially in the area of integration, but I don't remember any major issues with the solution.

Microsoft support is okay. If you are aware of the community practice when it comes to the tool, you can pay for Microsoft .NET Framework's extended support, as it can be helpful. The support is really good. I rate the technical support a seven out of ten.

Neutral

As long as somebody in your company understands how the tool works, handling its setup phase is not complex. If you are learning to use the tool for the first time, the setup phase can be difficult. You need a good understanding to start with if you want to do the setup phase easily.

During the product's deployment phase, our company just needs to push the product through the pipeline, which is a very easy process. Putting the code out there is pretty easy since Microsoft processes work quite well in a simple manner.

My company has not looked at the tool from an ROI perspective since it is a product we need to use. Along with the stack of Microsoft products, Microsoft .NET Framework is a tool that works for our company.

In our company's development projects, the code is built using Microsoft .NET Framework, which is valuable and beneficial.

In our company, we have a system internally that runs several contracts that we do, and it provides a workflow application that people in our organization basically manage to make sure that the workflow for the contracts we hire is completed, so it has a lot of business rules in it, meaning it has a very strong business rules engine. The other main process our company uses is in building the cloud solution that is focused on how you deliver durability to end-customers because it is a tool that can be used in a very extensible manner, leading us to use it a lot.

The interoperability of Microsoft .NET Framework with other languages and platforms affects our company's projects since it allows us to build whatever we want. There are no limitations in the tool, and as long as someone in our company has an API we can work with, we can build a connector tool, so it is quite open to what it can achieve. In general, with some of the low code areas, you may start to run into challenges while doing some integrations and maintaining them, but with Microsoft .NET Framework, it is very simple since once something is built, it works fine, especially when doing updates and changes, it is an easy process which is not a difficult thing to manage at all.

The product's security features are fine, but I feel you need to follow a security-by-design approach for all software environments. Microsoft .NET Framework usually enables what you do, but it does not make it happen for you since it only serves as a toolkit.

The performance and the scalability of the applications developed in Microsoft .NET Framework are fine but my has got certain things on Microsoft .NET Core is on Microsoft Azure. It can take as many customers or as many users as Azure can handle, making it a very extensible tool.

The product is not difficult to maintain.

The integration of security and network of the tool has benefited our organization since we can easily integrate SIEM, SOAR, or NMS tools.

I recommend the product to others who plan to use it. I believe that you need to invest in getting to know how to use and run the tool.

 I rate the tool a nine out of ten.