Microsoft .NET Framework Reviews

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.

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

The most valuable feature is customization.

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.

There have been some issues with the running application crashing.

The scalability is good.

Microsoft's technical support is good.

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

We used an in-house team.

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

We pay around $450 for our license.

.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.

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. 

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.

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. 

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.

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

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. 

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

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.

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.

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.

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

The product is stable.

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.

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

Positive

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

The product is free.

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.

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

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

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.

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.

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.

For testing purposes, we deploy it on our own server (on the Infrastructure server). For our production, we're deploying it on AWCC too.

Nowadays, Microsoft is trying to fix a few things and build a framework faster than other frameworks. There are a few reasons to choose .NET. However, my supervisor selected this framework for a few scenarios, and our scenario is also quite a good match with the .NET Framework. 

We are using, the .NET Core Framework right now. It's the Core platform. They are releasing a new version, and the new version is becoming faster and easier to use compared to other frameworks and other languages. 

The initial setup is easy.

They offer good CLI support.

It's easy to create and integrate things.

They're improving many features day by day. Maybe other kinds of support would be helpful. Making it even faster would be welcome. Their ORM is a little bit slow compared to other ORM. That said, comparing to the current version and previous versions, their ORM is now much faster.

They should try to improve their Blazor WebAssembly.

Previously, we used to face difficulties in designing a pattern or this kind of feature. However, right now, they're improving this so it's easier to write than it was before.

I've been using the solution for three years. 

The solution has been very stable and reliable. We haven't had issues with bugs or crashes. 

In my company, we have more than 100 employees, and more than 50 are using .NET Framework.

Compared to the previous version, the current version is more scalable in .NET Framework.

I've never used technical support. 

I'm also familiar with Java. 

The product was easy to set up. It was not an overly complex process. I'd give it an eight or nine out of ten for ease of deployment. Their CLI support is very good. 

The deployment itself is fast and takes about 20 minutes or so. I'm using a Windows server. It might vary based on dependencies. In our case, it was very straightforward since we had everything set up and ready to go. Only one technician was needed to set up the server. 

We do not have to pay to use the .NET Framework or other kinds of frameworks. 

We are end-users. 

I'm not sure why the company decided to use the solution. However, they have used it for a while. 

Choosing a framework totally depends on the scenario and project. If you want to build an interface, then the .NET Framework will be good. That said, a Java framework also will be good. I'd recommend either of those frameworks in general. 

I'd rate the solution eight out of ten. they are always trying to improve, unlike other frameworks or languages. There are also good features and a good community around it. 

I use .NET Framework for development because my client uses it. It was already in place when I started the product. They work with .NET because it's mainstream and .NET programs are widely available.

Pre-programmed functions for .NET Framework are widely available.

I would like more web integration.

I have been working with .NET Framework for the past two years.

The framework is stable, but it depends on the size of the application. If it's a larger application running on multiple machines, you may experience issues because it's on Windows, the least stable platform. 

The initial setup is easy, and it takes less than half a day.

I rate .NET Framework seven out of 10. If you are using .NET, make sure your setup meets the requirements because that was an issue that caused a lot of problems.  I would recommend Magic rather than .NET. It takes longer to develop something on .NET. The framework has extensive possibilities, so the learning curve is steep.

I'm an associate professor of computer engineering.

The solution is user-friendly and straightforward. I enjoy using it.  

It's a little difficult to scale this product for large organizations.

I've been using this solution for 10 years. 

It usually takes a few months for each new version to become stable. 

Scalability is a bit messy so we're forced to use different solutions for different clustering. 

We're satisfied with customer service. 

This is a good product and although it's not suitable for everyone, we're able to support various clients who use this. 

I rate this solution seven out of 10.