Microsoft .NET Framework Reviews

A team of developers in our organization are using the solution. Microsoft .NET Framework is used in our company for web and mobile application development. 

The solution has assisted our organization in the full-stack development process. The tool can be deployed on all types of devices, including mobiles and desktops. The MAUI capabilities of the solution have been the most beneficial feature for our organization's development needs.

At our company, we never had the option to develop for external users. By using specific frameworks from the solution or MAUI, our company has been able to develop mobile apps that can be deployed externally with utmost security. 

The product exhibits impressive compatibility. In our company, the solution is being integrated seamlessly with iSeries, K2 Environment and all vital databases where the data is stored in Db2 and SQL. 

Like in C#, Microsoft .NET Framework should provide code reusability options for all kinds of development processes. 

I have been working with Microsoft .NET Framework for two years. 

I would rate the stability a nine out of ten. For two years, we have been using Microsoft .NET Framework in our company, and we have never witnessed the product to be unstable. 

I would rate the scalability a nine out of ten. The scaling process may take time, but there are endless possibilities. Our organization has about 50 users of Microsoft .NET Framework. The solution is used daily in our company, and there are plans to increase the frequency and number of users. 

At our company, we are utilizing resources like GitHub and search engines to resolve our queries and issues. 

Our company was using Magic and K2 beforehand, which has a few similarities to Microsoft .NET Framework. Due to a lack of resources and developers in Magic, our organization shifted to Microsoft .NET Framework. 

I would rate the initial setup process a nine out of ten. The deployment process of Microsoft .NET Framework was found straightforward by our company. It took just a couple of hours in our organization to complete the installation process of Microsoft .NET Framework, the process got accelerated as we already had Visual Studio deployed in our environment.

Only one professional was required in our organization to deploy Microsoft .NET Framework. There is a team of seven developers in our company who use the platform. The maintenance of the product is implemented once a month in our company, but mostly its for upgrades from .NET. 

Our company has realized an ROI from the solution. Our company received high-budget quotes from clients to outsource mobile development; an ROI is found when comparing in-house development and buying off-the-shelf or development outsourcing. There has been an approximate ROI of 40%, but it's based on the money saved due to purchasing the tool. There are software and employee costs for a company that is unaccounted for in the ROI. 

I would rate the pricing an eight out of ten. It's an expensive solution. The high operational cost is often due to integration requirements with Visual Studio. There are no additional costs to the initial contract with Microsoft .NET Framework. When new developers or users are added to a project, you need to purchase Visual Studio Lab. 

Our organization is presently evaluating low-code and RPA solutions. 

The Microsoft .NET Framework enhances the development capabilities for mobile and web applications. The solution helps in developing computer applications in multiple languages and for local platforms. 

Microsoft .NET Framework is known for security features, so we haven't had any security incidents or breaches in our organization. There are four or five applications in our company that have been developed in the Microsoft .NET Framework. 

The performance of applications built with Microsoft .NET Framework depends on the server. All the applications we have built in our company using the solution don't have any response issues. I would advise others that the solution is worth it if there are full-stack developers in the company.

A lot of possibilities get unlocked in C# and JavaScript when using Microsoft .NET Framework. I would rate Microsoft .NET Framework as a nine out of ten. I would definitely recommend the product to others due to its flexible capabilities. 

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.

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

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.

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.

I am currently working on the development of a new product using Microsoft .NET Framework. The project is currently in the analysis, architecture, and user acceptance phases. It is a comprehensive system similar to ERP, designed to manage internal resources for a sizable bank. The application focuses on handling IT resources for the bank, and it is being developed in-house.

Within each specific .NET product of ours, we currently have a robust portfolio with around a dozen products actively running for our customers. Based on the user databases, it's evident that each product is implemented using .NET. In fact, one of our products boasts slightly over one thousand users. This underscores the prevalent use of .NET across our product range.

Firstly, I appreciate the decision to use Microsoft .NET Framework. I find it to be an excellent language, with a history rooted in providing an alternative to Java, albeit with initial challenges. It is gaining popularity and may be voted the most desirable programming language. What I particularly like about .NET is its language efficiency. While C# is the primary language, the platform also supports others, catering to those inclined towards functional programming. Although I started with Shell, I'm still grasping the concept of functional programming. Despite initial reservations about object-oriented programming, I acknowledge its advantages. .NET is a safer option, and despite criticisms, it has evolved over the years.

One notable aspect is .NET's transition to an open platform in recent years, distancing itself from being exclusive to Microsoft engineers. I appreciate the versatility of .NET, enabling code production for a wide range of platforms, presenting a strong competition to Java. It allows targeting practically any physical platform, showcasing its flexibility. These qualities contribute to my positive view of .NET, totaling thirteen aspects that I find appealing.

In the realm of Microsoft .NET Framework, particularly in the C# language, there have been significant developments that I find highly commendable. I am genuinely fascinated by the continuous evolution of the language, and staying abreast of the latest features in Azure is both challenging and enjoyable. Working with C# in Azure is particularly fantastic.

I appreciate in .NET, as compared to Java, is the enforcement of types, providing a better experience in terms of technicalities. Additionally, the introduction of Roslyn in the past few years has brought about the concept of late .NET, which I find interesting and powerful. This allows for the transformation of symbolic code just before execution, eliminating the runtime decision-making process and enhancing efficiency. However, late .NET does come with a drawback – a delay in the last-minute computation when starting an executable. While some may find this less appealing in terms of instant responsiveness, especially in serverless cloud environments, the efficiency gained from executing strictly binary code is valuable.

Despite potential drawbacks like the time required for activation, I view .NET favorably for its technical advancements and efficiency, especially in scenarios such as serverless cloud computing. It's essential to recognize the intricacies of how .NET processes code and the efficiency it brings, which some may overlook.

I have been using Microsoft .NET Framework for many years, since 1992 or 1993. 

It is stable.

I'm frequently questioned about the scalability of .NET products by the company owner. In response, I inquire about the specific aspect of scalability they are interested in. If the concern is about handling sudden surges in traffic, I affirm that .NET is indeed scalable, especially with the implementation of group health checks. This ensures automatic scaling without manual intervention, providing convenience.

Contrary to common misconceptions, I emphasize that the performance of .NET is typically not hindered by processing power but by factors such as disk I/O and database operations. Scaling the database differs significantly from scaling processing power, as it involves handling transactions, open transactions, and conflicting operations. If isolation is not well-implemented, issues may arise. For instance, a database like SQL Server, while appearing appealing a decade ago for its tools and affordability, presented challenges in terms of scaling compared to Oracle. Understanding these nuances is crucial for making informed decisions about scalability.

Regarding customer support from Microsoft, I can say that when we documented issues and submitted tickets, Microsoft was responsive and open, even without direct contact. Working with Microsoft has generally been positive, and their strategic direction is something we have followed closely. Microsoft's commitment to evolving their product has been beneficial for us, even though the unpredictability of their decisions can sometimes pose challenges. In a small company like ours, adapting to changes becomes more complex, especially considering the project size.

As a company, we are also involved in software development for the European Commission, where the strong requirement is to use software from the .NET world. The challenge arises when dealing with Java in parallel, as its community processes add an element of unpredictability. Managing a team that can swiftly adapt to changing technologies is an advantage, but it requires time and effort. The unpredictability of Java's direction contrasts with the more foreseeable evolution of .NET.

We have had experiences with Oracle as well as .NET, specifically with the Silverlight framework, though that was some years ago. Silverlight, while not inherently bad, tends to be criticized, and I often advise people to understand its origin as the Presentation Foundation Everywhere (PFE), indicating its intention to provide a unified UI across various platforms. However, due to various challenges, it was eventually phased out, and Silverlight became obsolete. We once had a product active on SolarWinds 3.5, transitioned to SolarWinds Sorin, but unfortunately did not survive beyond Silverlight 5.

Yes, it is easy. .NET has expanded its scope significantly. It's worth noting that while many may mention .NET, not everyone truly comprehends its intricacies. Nowadays, people often focus on microseconds, assuming they grasp the technical aspects, which can be misleading.

Although Continuous Integration and Continuous Deployment (CICD) may seem attractive for automated deployment, the allure of the cloud has somewhat overshadowed the significance of meticulous deployment, as it's often perceived as someone else's responsibility. This shift in perception, coupled with tools like CircleCI, requires a closer examination of their efficiency compared to more conventional platforms like Azure. Understanding the true speed and efficacy of these tools is imperative for making informed decisions.

The shift in the deployment and maintenance is evident, as manual installations are no longer the norm. Intelligence is now directed towards automation, emphasizing the importance of testing. Once this process is completed, confidence in the system's functionality increases, alleviating concerns about manual loading and ensuring an automated and efficient workflow.

Everyone in our organization follows the mindset of having our proprietary tools. The majority of our internal tooling is developed in-house, making us predominantly a .NET-centric environment. While it's true that we also provide Java solutions, most of our confidence lies in .NET due to its reliability. Reflecting on past experiences, there were initial concerns about how autonomously and optimally .NET could run, especially in terms of memory management. However, over time, particularly with the introduction of .NET Core, those concerns have dissipated, and I am now completely confident in the reliability of .NET.

In the interim, there's no need to purchase videos for viewing. Microsoft has made significant moves in the .NET space, starting with their response in Visual Studio Code and now providing Visual Studio entirely for free. This is a notable shift from the past when we used to pay substantial amounts for technical subscriptions. Previously, a group of ten developers could cost several thousand dollars annually for licensing. However, the current trend is to offer these tools for free to maintain their dominance in the developer market. The market dynamics have changed, and now developers can freely download Visual Studio, making it a preferred choice over other paid options. 

It has been around for about three months, and I've had a chance to delve into the capabilities. As for the .NET Framework, it's advisable not to use it anymore. While there might be some exceptional cases, I don't consider myself an expert on .NET Framework. The trend is shifting away from Framework towards .NET Core and now .NET 5. I would anticipate platforms to adapt and run seamlessly on the newer versions. Transitioning from Framework to newer versions might not be straightforward, particularly in terms of setup and configuration. Working with .NET Core involves a different approach, especially when dealing with configurations and influencing the product's behavior externally.

Switching everything from Framework to .NET Core in a short span may not be feasible, and even if you plan to do so, existing products and customer preferences may necessitate keeping the older products alive. Users may inquire about their familiar products, and it's essential to maintain support for them. Despite these challenges, I find .NET Core, particularly version 8.5, to be highly commendable. It excels in various aspects and is a robust platform, rating it 8.5 out of 10.