Microsoft .NET Framework Reviews

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.

I work on the C#, ASP.NET, SQL Server, and others. I am also developing some scripts for my RPA solutions when needed. 

Microsoft .NET Framework has introduced many new features, making the technology very vast. In particular, they have a very good Visual Studio environment to do development.

The solution is not limited in storage, is customizable and simple to use.

I would like to see a better response time from the technical support.

This is a stable solution.

Microsoft .NET is scalable.

My experience with Microsoft technical support is that they can be difficult to reach. The support depends on the contract between the client and the company. 

Positive

Microsoft .NET has both open source and licensing options. Microsoft Framework and Visual Studio are licensed however, they have introduced .NET Core which is open source. In .NET Core, you will find Angular which is open source.

I would rate Microsoft .NET Framework a nine out of 10 overall.

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.

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

We utilize the Microsoft .NET Framework to develop software applications, including those that are dot net based. Our work involves a wide range of tasks, such as content management systems (CMS), website creation, database management, and data analysis. Whether it's related to content organization, database reporting, or intranet and internet solutions, we cover it all. Our toolkit includes Microsoft SQL and SQL cluster servers, enabling us to leverage a comprehensive set of tools and technologies.

We have this solution deployed on public and private clouds.

We are actively involved in software development and one of the companies we are affiliated with is Ingeniux.com. It is a mid-market content management software provider based in the United States. Our focus lies in content management, where we enhance the platform with numerous application extensions and plugins. Our target user base primarily consists of mid-cap corporations and universities. Ingeniux.com serves as a well-managed alternative to WordPress, offering superior functionality. While we also have experience working with WordPress, our primary development framework for Ingeniux.com is Microsoft .NET Framework.

The most valuable feature of Microsoft .NET Framework is debugging.

If AI could be incorporated in Microsoft .NET Framework it would be helpful.

In the majority of networks and development companies, individuals are not solely limited to using the Microsoft .NET Framework. Microsoft has made significant strides in integrating various technologies, enabling seamless data flow. This integration is prominently seen in visual studio, where Microsoft emphasizes streamlining the development process. While not entirely platform-agnostic, visual studio exhibits a high degree of compatibility with different platforms, allowing for greater flexibility in development.

I have been using Microsoft .NET Framework for approximately 20 years.

When utilizing Azure for hosting, the stability can be unreliable and inconsistent. It becomes a hit-or-miss situation. As a result, we prefer to host everything in our private cloud rather than relying on Microsoft's cloud services, as the stability is not optimal in the latter case.

We have never had an issue with the scalability of the solution.

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

The support provided by the Microsoft .NET Framework can be considered satisfactory to commendable. We have submitted numerous bug reports for Azure, and in some instances, their response indicated a lack of prior knowledge about the issues being already live.

Starting from scratch can be a complex endeavor, but once you have prior experience, it becomes more predictable.

I have seen a return on investment using Microsoft .NET Framework.

Considering the bigger picture, opting for the Microsoft ecosystem can be beneficial and it is priced well. When relying on entirely open-source solutions, you may encounter challenges associated with dealing with multiple vendors and potentially compromised security measures. However, it is important to note that Microsoft could enhance its performance when it comes to addressing critical security concerns.

When conducting high-level bug analysis and providing feedback, the process often involves navigating through a complex maze of procedures. Opening a ticket may require going through various steps, making it challenging to reach someone directly involved in software debugging or problem resolution. The help desk system at Microsoft may exhibit elements of hierarchy and bureaucracy, which can add to the difficulty of accessing the appropriate support channels for addressing software issues.

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

You are able to develop applications using Microsoft .NET Framework. It is a development framework.

Using Microsoft.NET Framework we developed many Line of Business Applications, which empowers digital transformation and optimized business processes.

Framework provide almost all the technology stacks requires for custom development, only issue is if not used properly, it will create undesirable results.

MVC framework could be better if provide little bit more restrictive framework. Instead of allowing developers to adapt anything they want.

I have been using Microsoft .NET Framework for approximately 15 years.

The solution is stable because Mircosoft releases updates frequently.

The solution is scalable.

We have approximately 13 users using this solution.

When we have contacted Microsoft Support they ask too many questions and requiring too many details. They sometimes do not assign the right person that has the knowledge to deal with the support ticket.

The installation is straightforward. The time for the deployment depends on the environment, but it typically takes approximately 45 minutes.

I did the implementation myself. However, I would recommend using a team of experts for the deployment and maintenance of the solution.

The solution is free but you need to pay for a license for the hosting service.

Java server pages, j2ee. 

I would recommend this solution to others. However, they need to understand the capability of the Framework, and they should align their solution according to the Framework to prevent any showstopper or bottlenecks in their development process.

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