Microsoft .NET Framework Reviews

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

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

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

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

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

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

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

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

Positive

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

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

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

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

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

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

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

I'd rate the solution eight out of ten.

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.

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.

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. 

We design solutions for different applications and we use .NET core for the solutions' web portals. We primarily use .NET core for the back end of our services.

In my opinion, the best thing about Microsoft .NET is the fully featured framework. It provides most of the things which a normal developer requires of any application out of the box. There's also a great Microsoft community and support with the frame. Another important thing is that the latest versions are platinum diagnostic, which is quite valuable.

In my opinion, this solution can be improved by providing out-of-the-box support for different types of libraries.

I have been using this solution for about 10 to 15 years now.

My impression is that this solution is stable.

My impression is that this solution is scalable.

We have contacted their technical support many times. I would rate them a 10, on a scale from one to 10, with one being the worst and 10 being the best.

My impression is that this solution is not complex to set up. Installing .NET usually takes only a few minutes. If you go for full-fledged and more components, it may take longer.

If you want to go for development, there is an open-source ID call at video studio code. If you want to go for enterprise development, then there is a video studio professional or enterprise, which is a little costly for an individual. I think individual developers can do this work free of coupons. They don't need to pay anything to Microsoft for that.

I am working as a consultant for this solution for various companies.

I would recommend this solution to other people.

I would rate this solution as a whole a 10, on a scale from one to 10, with one being the worst and 10 being the best.

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.