Microsoft .NET Framework Reviews

We utilize Microsoft .NET Framework for domain and web applications. We have also developed console applications and Windows services using this framework. In the past, we employed WPS upon its launch for various purposes, including web services. Currently, our focus has shifted primarily towards web applications. We are leveraging the latest versions, such as .NET 6 and .NET 8, to develop our web services.

We have different layers of security, one on the application side and another on the network side. Over time, security has continuously improved and has remained a sensitive issue. Microsoft Framework has solutions the security department recommends, enabling us to incorporate them into our solutions.

Microsoft .NET Framework continually innovates, particularly in Visual Studio, which focuses on improving languages, debugging, and .NET functionality. 

They could enhance support for Python within Visual Studio, as integrating Microsoft products with other frameworks can present a steep learning curve.

Visual Studio for C# and .NET development has a smooth experience.

I have been using Microsoft .NET Framework for 10-12 years.

The .NET Framework is stable, with a few exceptions. With the release of .NET Framework 4.6.2, where significant changes were made regarding TLS and SSL certificates, resulting in the duplication of TLS 1.0. Legacy products reliant on TLS 1.0 may encounter compatibility issues when migrating to this newer version of the framework.

Microsoft is moving from the legacy .NET Framework towards a more portable and modernized version known as .NET Core. This shift involves migrating from the older versions associated with the .NET Framework to the capabilities offered by .NET Core. This transition addresses various challenges and complexities encountered with the previous framework.

Gy

The initial setup is very easy. You just install one component and the installer package. Then, you are good to go.

It's essential to explore your options before making a decision. Microsoft offers the traditional .NET Framework. There are superior alternatives within the company's offerings. It remains a viable choice if your project demands a legacy framework like the .NET Framework. However, if you can choose, I highly recommend opting for the latest iterations, such as .NET Core versions like .NET 6 or 7. These versions offer enhanced support and features, making them preferable choices. I advise you to consider the specific requirements of your project.

Before .NET, we used C++ and C and many other languages that did not use CLR. They were not memory-managed like the .NET Framework. Shifting to managed solutions which have CLR brings productivity to the development team. We don't need to consider garbage collection and memory in .NET because the framework will handle it. This increases our productivity. If somebody is using C# or VB.NET, you need one installer from Microsoft to take care of everything. Two different languages will translate to the same intermediate code. The only competitor to .NET in the market is Java.

.NET Framework consumes much memory. The .NET Core framework requires less memory and offers firm support.

It is very easy to learn compared to other languages.

Five years ago, I would have rated it eight or nine. But now, since we already have superior products, I rate it six or seven due to the need for more portability and many legacy component dependencies.

I rate the latest version of .NET an eight to nine 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.

Whenever I need a back-end system, I create all the applications or all the products. For example, flights, hotels, and car engines have been created. .NET and Chase use my system, and I have developed flights, hotels, and car engines completely; the entire back-end system in .NET for them.

The APIs are completely effective. I can create .NET APIs very easily through .NET. For example, if I need to design any system, I can use C# and .NET.

Their system is very vast. I have spent 12 years here, and I can definitely say there is still a lot of scope for improvement. They have done a lot, however, .NET still has room to improve.

I think I have used the solution for almost 12 years.

The stability is very good right now. With the newer version, the solution is performing very well.

Scalability is good. The system has managed the scalability very well. The compatibility with Azure cloud system is very good from the scalability side, and I am deploying a lot of applications on Azure. I didn't see any scalability issues there.

Customer service is very helpful.

Positive

Whenever someone needs a very good back-end system or a strong system, they should go with C# .NET technologies. 

Overall, I would give it a rating of nine for .NET. This is definitely the way to go.

I use the solution to create websites and web services. Different departments in the whole organization use the solution. Networking, production lines, and payment departments use it.

The Windows Communication Foundation is the biggest advantage we get from the .NET Framework.

We use P storage on-premises, the middleware from Microsoft, and sadly, Microsoft is no longer improving that product. That's why we are transitioning to SAP and the cloud platform integration from SAP. It's been evolving for a few years, and they've been going to Azure for reports, which is a bit of a shame, and instead of migrating to Azure, we are migrating to a different solution.

I've been working with the solution for around ten years.

The solution is stable. It is more stable than SAP.

The solution is very scalable. It is a backend solution, so there are no direct users. Our organization is enterprise-level.

The customer service is very good.

Positive

The solution is really easy to install. It's out of the box. When you install a new server, the .NET Framework is there. A big advantage of the solution is that everything updates automatically every month, such as security updates with the Windows server updates. This is in contrast to SAP.

It takes about ten minutes to one hour to install, depending on the configuration.

For .NET Framework is doing, it is the right price. It's far less expensive than SAP when looking at the numbers. We have an annual license, and we pay extra for extended support. The product is nearing the end of its life so we have to pay extra.

I keep seeing new things coming with the .NET Framework, and Microsoft is improving a lot. In terms of functionality, .NET Framework is better than SAP. I recommend the solution.

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

However, the product is nearing its sunset, and we think that by 2028, we won't get support anymore, so we have to decide to migrate the platform.

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.

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 use the solution for DevOps for implementation release.

The boards within Microsoft Azure need improvement, especially compared to Jira, a widely utilized ticketing tool in various organizations. While Jira is cost-effective, Azure provides various features in one place through its DevOps console. However, some shortcomings in Azure's boards and Wachee require attention. These tools might suit specific industries and workflows, but enhancements in Microsoft Azure's boards and infrastructure are necessary for larger-scale enterprises with complex architectures.

I have been using Microsoft .NET Framework for two to three years.

The solution is stable.

Our client utilizes the Microsoft Stack. Therefore, we must collaborate with them for internal Proof of Concept (POC) and presentations to attract new clients. We have around 250 Microsoft users. Within this context, various components such as ETA, specific developers, working with Azure, and blockchain development are conducted within Azure.

The solution is scalable. We are using the enterprise-level subscription

Around 200 people are using Microsoft .NET Framework.

We have a dedicated support system and have subscribed to it specifically for enterprise-level digital data scripts from Microsoft, which provides us with reliable support lines.

Positive

I worked on alternate servers to build the .NET applications. I have created some pipelines for the automation practice.

I have used the .NET Framework to develop applications and build pipelines. Additionally, I have implemented multiple pipelines in the data science domain, handling data. It is easy to design and manage these pipelines.

If you spend some time delving into web development, such as watching YouTube videos, you can discover solutions that may not be as complex as AWS cases. However, Azure offers a user-friendly interface that simplifies configuration and pipeline creation. You don't need to write Java code because, with additional settings in your pipeline, Java can be automatically generated. Configure these settings, write the necessary scripts, and deploy. Azure provides an incredibly cool, user-friendly, cost-effective dashboard that allows you to do more using the GUI.

Deploying applications using the Microsoft .NET Framework involves creating a pipeline. It can be done quickly; within a few minutes, you can deploy applications.

I am the sole developer and engineer responsible for managing the entire pipeline creation process. This involves collaboration between developers and operational teams. My role encompasses implementing solutions and deploying them through Azure DevOps. The team has completed the website development, and my task now is to establish an efficient deployment pipeline that doesn't require extensive time for construction or interface.

We don’t need to pay any particular ownership charges for creating pipelines on the .NET service. We have a monthly subscription for the solution.

Azure offers numerous automation systems that are already predefined by Jira pipelines. Consequently, there's minimal intervention required as they come pre-configured for build tests and deployments. Our primary task involves configuring these setups according to our specific requirements—determining where we need to deliver and retrieve items, thus necessitating consideration for various concerns within the Azure pipeline.

Connecting components in building .NET applications becomes straightforward due to Azure's facilitation of these operations.

It doesn't require regular maintenance, but there may be instances where updates are necessary to address specific application issues or to ensure compatibility with certain updates. In the context of Azure, there is no need for additional maintenance tasks. Once a pipeline is created, the focus remains on managing that pipeline, addressing any configuration issues, or troubleshooting when necessary. There is no direct need for manual updates or upgrades for software-related updates, as Microsoft's internal IT manages these processes. There's no individual requirement for us to handle service upgrades or updates.

Microsoft Azure is highly efficient across server environments, including .NET and other frameworks like Java. It supports a wide array of servers available in the market today. Current technology seamlessly accommodates diverse server infrastructures, making it notably efficient and ideal for enterprise-level operations. I rate it a perfect five out of five for its performance in DevOps and delivering sophisticated solutions to complex challenges.

We've extensively utilized Azure in the logistics industry, implementing numerous solutions with a significant reliance on its services. Azure covers almost all data analytics, data science, and data engineering aspects. As a developer, I've been solely responsible for implementing and constructing nearly all pipelines within Azure DevOps to address these complex problems. This stands as a benchmark achievement.

Azure's user-friendly interface and productivity make it a standout solution within the Microsoft suite. I highly recommend enterprise resources consider migrating to Azure when contemplating a move to the cloud—it's the top choice.

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