Microsoft .NET Framework Reviews

We use Microsoft .NET Framework to develop Windows applications. It is utilized for Windows form solutions to create Windows-based applications. Our team uses it in our software development process for data connectivity, user input form validation, user management, authentication, and authorization.

It is beneficial for running smooth operations on every application. We face minimal problems using it, allowing for stable and efficient operations.

All team management features, application management, core security, and integration capabilities are very helpful. It facilitates running Windows business applications and leveraging enterprise application development.

There is room for Microsoft .NET Framework to improve cloud platform capabilities. They have already made improvements in their new version by making it multi-platform and upgrading it for cloud platform capability.

We have been working with Microsoft .NET Framework for the last fifteen years.

Microsoft .NET Framework has a high level of stability, rated eight out of ten. The stability benefits our operations by ensuring smooth and reliable performance, minimizing the occurrence of problems during application usage.

Microsoft .NET Core is more scalable than the traditional version. By making it cloud-compatible, scalability has improved in their new version. However, as Microsoft .NET Framework is not built for the cloud, its scalability remains limited.

We manage it internally, and if any problem arises, we use online resources. We have never reached out directly to Microsoft technical support.

Positive

Before Microsoft .NET Framework, we were using the old version of Microsoft technology, Visual Studio 6. It was retired as it was outdated, prompting the switch to Microsoft .NET Framework.

The initial setup is easy to complete. On a scale of one to ten, where ten is the easiest, I would rate it a ten. No challenges or difficulties were encountered during the initial setup process.

The same team of five people handle the deployment and maintenance activities.

Microsoft .NET Framework helps in running smooth operations, which we value greatly. It is time-efficient and has saved us a significant amount of time.

The pricing is rated six out of ten. It provides value for the cost.

We did not evaluate other options before choosing Microsoft .NET Framework. Being already familiar with Microsoft products, it was easy for us to switch to their new technology.

I would recommend using the latest version of Microsoft .NET Framework, especially for cross-platform and cloud-native applications.

I'd rate the solution eight out of ten.

We use the solution for some internal applications we develop. We also use the Microsoft workflow engine.

When using Microsoft .NET Framework, you start writing the code internally. This reduces the cost on the licensing side, which helps reduce the overall expenditure of OpEx and CapEx.

The solution needs to update its security periodically because there are many security concerns. It should also provide audit reports so that it is easy for the auditors to see the security controls.

I have been using the solution for 10 to 15 years.

I rate the solution’s stability ten out of ten.

Microsoft .NET Framework is a scalable solution.

I rate the solution’s scalability an eight out of ten.

Since most of our developments are in-house, we are less dependent on technical support unless it concerns the engines.

Positive

The solution’s initial setup is easy. It takes around half a day to get the servers ready, install it, test it, reboot the server, and retest.

Microsoft .NET Framework is very cost-effective for corporate users. If you're on Microsoft, you have no choice but to use it. We have an enterprise agreement with Microsoft, and the solution comes to us as part of a bundle. Overall, we are satisfied with the solution's pricing. The solution has helped us save around 25% of our operational costs.

On a scale from one to ten, where one is bad and ten is good, I rate the solution's pricing ten out of ten.

We use the solution for development purposes. When it comes to security, we depend on two levels of security. The first level is what Microsoft .NET Framework gives and the patches that Microsoft provides. The second is our internal security algorithms and logics.

Licensing plays a big role when you have other systems. When using Microsoft .NET Framework, you start writing the code internally. This reduces the cost on the licensing side, which helps reduce the overall expenditure of OpEx and CapEx.

I would recommend Microsoft .NET Framework if you start developing your tools and products in Microsoft. This is one of the platforms that Microsoft provides. If you are into .NET and want to develop a lot of applications, you need the Microsoft .NET Framework platform. We perform the solution’s maintenance in-house.

Overall, I rate the solution ten 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.

I'm a developer with .NET Framework. Apart from powering the Xamarin platform, I also use .NET for API development for .NET Core, which I deploy on clouds like Azure or AWS. We use .NET Core for every solution, from built-in web apps to REST APIs. I can use .NET Framework to build desktop-based applications using a company called WPF. We use .NET for Unity, a popular gaming engine. It uses .NET as well as C#. In our organization, we just use .NET for Xamarin.

Given that it's cross-platform right now, where you can use it on Windows and Mac, that is the single most significant feature that has resulted in wider adoption of .NET. Earlier, you could only build solutions for Windows and Windows server ecosystems, but now you can build a .NET Core app and deploy it on Linux VMs, and so on.

One thing that could be improved is the tooling and IDE for .NET in non-Windows environments like Mac. This is a common gripe across the developer community. Visual Studio for Mac is nowhere near as feature-rich and productive as Visual Studio for Windows. Visual Studio for Mac is a shadow of what Visual Studio for Windows offers. For developers who switch from Windows to Mac and those who are using Visual Studio or both, they find that the Visual Studio provided by Microsoft for Mac is very primitive compared to what's offered for Windows.

I've worked with .NET Framework since 2002 on and off.

I rate .NET Framework’s stability a nine out of ten.

I rate the initial setup a nine out of ten. The initial setup is very easy. When you install Visual Studio, it will install the latest .NET runtime for you. You don't have to do anything extra to get .NET installed.

If you build cloud solutions, your .NET Framework will be installed as part of your solution. Suppose you are deploying something on the cloud, microservices, for example. In that case, you'll most likely deploy Microsoft services as part of the container, and the container will ensure that all the prerequisite underlying software, like .NET Framework, is installed. In my organization, we already use .NET Framework for mobile development on Xamarin, and that requires us to install the .NET Framework on the system we're developing on. .NET Framework gets automatically installed when you install the Visual Studio IDE that comes bundled with all the dependencies like the .NET Framework.

How fast .NET Framework deploys depends on your Internet connectivity, but it can take less than two minutes. The solution does not require maintenance. One person is enough for deployment.

I rate the solution's pricing a two out of ten because .NET is an open-source framework. You don't have to pay for a license. .NET alone wouldn't do the job for you. .NET is the underlying framework, so you must install IDEs or something to build apps on top of .NET. Visual Studio, for example. Only the Visual Studio Community edition is free. The other variants of Visual Studio will cost you money, and they have increased their prices. Everything is free if you use the Community edition, but if you have to deploy the solution to the cloud, like Azure or AWS, they will charge you money. Likewise, if you are building something on Unity for game development, you can always distribute your games through the Apple, Windows, or Google Play stores, and they will charge you.

In my organization, .NET Framework is only used for mobile development in Xamarin. It's not used for server-side or cloud development because we use Java and Node.js. Once we move from Xamarin to another technology, our organization will probably not use .NET.

Suppose you want to work within the Microsoft ecosystem, which many organizations do because many organizations have had a partnership with Microsoft for a long period. In that case, .NET is the de facto development framework organizations use. .NET is very mature, well supported, and adopted by major Fortune 100 or Fortune 200 companies. Big companies use .NET, but maybe not for their entire spectrum of services and solutions. But most big companies use Microsoft .NET for some other part of their solution. It's been there for the last 20 years, and Microsoft releases new versions yearly. The current one is cross-platform, very robust, and stable. I rate .NET Framework a nine out of ten on all these criteria.

In my company, the solution is used for web development.

I use the tool as a commercial user so that applications can be made available for our company's customers or users.

The integration capability of the product with AI is an area with certain shortcomings, where improvements are required.

I have been using Microsoft .NET Framework since 2004, so I have twenty years of experience with the solution. My company has a partnership with Microsoft.

It is a stable solution. Ten years ago, the product was not very stable.

Scalability-wise, I rate the solution an eight out of ten.

With the tool, my company works with clients who run small and medium-sized businesses.

The solution's technical support is very good. Users can directly contact Microsoft for support. I rate the technical support a ten out of ten.

Positive

I have not used any other products from other vendors. I may have directly used some other products, but I only use products from Microsoft for the production phase.

Microsoft .NET Framework is a very good solution for the production phase.

The product's initial setup phase was easy.

The time required for the installation process depends on the time the user takes to download the installation stuff. Generally, the installation process takes just a few minutes to complete.

In my company, we use the tool for sales projects, CRM purposes, B2B projects, and creating applications.

The tool's feature that has been very beneficial for the development process stems from the fact that it is very easy to develop applications and to find a knowledge base of Microsoft.

The integration of Microsoft .NET Framework with other Microsoft tools has impacted our company's workflow since we have integrated it with Office 365.

Microsoft .NET Framework is a good product with a bright future.

The maintenance of the product is very easy.

I rate the product's capability a ten out of ten in terms of the learning curve for developers who are new to the tool.

I rate the overall tool a ten out of ten.

We are creating a certain solution. There is a client, the desktop Windows application, that is used within the organization. And behind it, there are certain Windows services, and there are kinds of Windows services that run on a scheduled basis. And there's a logic behind which kind of receives data in the form of files or APIs from different endpoints. So, basically, we are working with multiple external entities, and those entities, in some cases, communicate with us via API. And in some cases, they send us files, which are huge files, via a file gate. 

So, .NET, in that sense, we are using after receiving those files, we process them as normal. Then, there is communication with multiple endpoints to actually update certain backend gate systems within the organization. It's a good, big implementation for business purposes of the .NET framework. And the team that I'm a part of is responsible for creating those new requirements that we get from business. We create the solutions for that within this application as part of that application. Also, we are maintaining that application in the production environment, which is being used for running the business.

When we talk about .NET development, we use Visual Studio IDE to create these things. In recent years, there have been a lot of improvements in Visual Studio 2022. It would be a daunting task to list all of the features that have benefited us, as it would require a lot of time and effort. However, there are definitely many improvements year after year in .NET development. 

One of the improvements is the ability to make changes to the code while debugging applications within the environment, and the changes will be reflected in real-time. There are also many other improvements, such as the integration of Git and Azure DevOps.

The integration with DevOps tools, such as Azure DevOps, Jira, and GitLab, would be a valuable addition. This would allow us to manage Azure DevOps work items and artifacts, as well as pull requests, within our Visual Studio environment. These features would make it easier to develop, deploy, and test applications.

I have been using this solution for 18 years. I'm currently working on an application that uses .NET Framework 4.7.1. This is an older version of .NET Framework, and Microsoft has since released .NET Framework 4.8.1, which is the latest version. We are also using .NET 7 in the same solution, which is the latest version of .NET. The APIs that we have implemented using .NET 7 are hosted in a Service App cluster on Azure.

It is definitely stable. If I compare it with previous versions, it is constantly improving.

It's completely scalable. We can use it in any way. If we are working on a PaaS platform, then whatever offerings of the PaaS platform tell us to scale. So, if we are working on an application using the .NET Framework, then whatever the best product that we would talk to is offering for scaling up the application in the .NET Framework is completely compatible.

I would rate the scalability a ten out of ten. We have around a thousand end users using this solution. We use it every day in our organization.

The initial setup is very easy. I would rate my experience with the initial setup a ten out of ten, where one is difficult and ten is easy to set up. 

.NET framework is a very small package that can be installed in a few minutes on development environment or on production environment.

Just one person is enough for the deployment and maintenance of the solution. Any new updates are automatically pushed in if you configure it; that way, they are automatically pushed into your environment, and you will be notified that new updates are available, and you can easily install it.

Within my organization, we use tools from Microsoft. So we get a subscription from them. And for running that application in a production environment, we have their different tools' licenses from Microsoft, and we also have Azure subscriptions, like a couple of Azure subscriptions, one for the non-prod environment and one for prod environments.  

I have worked with Azure tools like Azure IaaS services, virtual machines, and SQL Server, and Azure PaaS services, like Azure SQL.

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

Microsoft .NET Framework is a development platform.

The web development and Microsoft Windows service development capabilities are among the most valuable features offered by the Microsoft .NET Framework. This language platform is highly user-friendly, with plenty of online examples and information available, as well as a robust development environment.

The integration could improve in Microsoft .NET Framework.

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

The solution is stable.

I rate the stability of Microsoft .NET Framework a ten out of ten.

The solution is scalable if it is set up correctly.

We have one person who uses this solution.

I rate the scalability of Microsoft .NET Framework an eight out of ten.

I have not used the support.

I have used a Java development environment. 

The initial setup of Microsoft .NET Framework is straightforward. The process can take 10 to 30 minutes depending on the components installed.

The solution can be implemented by one person. We did the deployment.

The solution is worth the money. We have received a return on investment. Approximately 30 percent annually.

The support is an extra cost when purchasing the license. The price of the solution is overall reasonable and paid annually or every three years. Additionally, they have a monthly license. The cost is approximately $1,000 per user.

There are other licenses that can be purchased and add-ons, such as enterprise licenses and third-party add-ons.

I rate the price of Microsoft .NET Framework a six out of ten.

The solution does not require maintenance.

I would advise others to use the newest version of the solution. It is a good solution overall.

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

I am building a web application and using this solution.

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

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

I have been using the solution for about two years.

As we are scaling quite nicely on Azure.

I have not contacted customer service recently.

Neutral

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

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

Java and Sprint are alternatives we considered.

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.