Microsoft .NET Framework Reviews

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.

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