Microsoft .NET Framework Reviews

We are a software company, and we build software. This is one of the solutions that we use in our development environment.

I have a profound handle on Microsoft. Net Framework.

As we are a software company, we find that accessing resources using this technology is easier compared to the others.

The main obstacle in this technology is that it is currently paid. If you want to develop an enterprise-level application, you have to purchase the enterprise-level development license. I think that this is a hurdle. If it is made free then more people will learn and the industry will have more proficient people with better performance.

In the next release, I am looking for more advanced technologies such as socket communication and enhanced features like realtime chat with the clients. This is what I have been looking at adopting into my existing application.

I have approximately six years of experience with Microsoft .NET Framework.

This solution is stable if the logic is handled sufficiently. It all depends on what kind of coding you are doing while you are developing the application.

This solution is scalable. The modular development plus expansion is quite easy.

We have 2000 users who are actively using this solution.

When we contact technical support, we open a ticket with the vendor, who then assigns us to a person. We meet to discuss the technical challenges we are facing and they come up with a solution.

Previously, we were using the IBM integration bus.

We were using Microsoft, Mobility Android, and iOS applications.

Most of my experience is with Microsoft solutions.

The initial setup was quite easy. The installation itself is easy. The prerequisites are already available on the internet.

It is a two-step deployment, the first being the development environment. The installation of that took between one hour and an hour and a half. For the processing, the deployment was a little bit different. I needed the information server hosting the Microsoft application.

While it's on a public cloud, some are on-premises that are accessed by the application.

We have a team of ten to maintain this solution. There are several internal connections to the system. For example, an interface with the other system which included SAP, Oracle, and IAD. The team looks for support queries that include any issues found or for any troubleshooting that needs assistance.

There are proper resources. Stability and scalability are quite good. We handle 3000 to 4000 users at any time and they are users from all over the world, including North America, Australia, and the Middle East. This is a good option for the level of the audience.

We are using version 4.5 but we are gathering a few more projects that are running on version 4.7 and 4.8.

I would rate this solution a seven out of ten.

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.

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.

Our primary use is to be able to build solutions more quickly and easily that has good flexibility. When you want to build a product, you have to have faith in the nature of its functionality and know you can write your code to run on their core. Another solution is to write software code to run on top of the framework. 

Microsoft .NET Framework is a very good infrastructure and we program over that. It handles many tasks for us and it helps us to write our programs very fast and very efficiently. Although it is like a virtual machine, it is still fast — or faster — and it is efficient. Compared to Java Virtual Machine (JVM), I prefer to use the Microsoft .NET Framework because it is built specifically to work with Microsoft Windows. I have grown to trust Microsoft over a long time and we can easily write programs in familiar languages to work with Windows over the Microsoft .NET Framework.

It has improved our efficiency in the time it takes to program a solution.

For us, direct integration with Microsoft Windows is probably the most valuable feature.

One thing that could improve Microsoft .NET Framework is to give it more flexibility. It is designed to work just on Windows. If it could run over Linux, over MAC, over mobile phone, etcetera, it would be a very good improvement. If it were the case, I would be able to write a program and I could be sure that my program would run on all those platforms and over other operating systems.

I know that Microsoft is currently working on solutions for this and the company makes .NET Core now. The .NET Core they propose is a framework like .NET Framework that will allow implementing programs across other operating systems like Linux. It is introduced in idea, but it has a lot of room for improvement.

If I were able to install Microsoft .NET Core over other operating systems, such as Linux, Unix, or mobile and it works as well as .NET Framework, then it solves other problems for me. 

The stability of the current version of the product is very good. In the lower versions of the framework, sometimes I saw a crash but after version 4, I haven't seen any crashes. It is really, really stable and I like it. I wrote some services that have run for about a year without any crash at all. All issues with stability seem to be fixed.

Microsoft .NET Framework is a solution, where the scalability is dependent on the programmer. The programmer could write a very large scale project — a large scale enterprise solution — using .NET Framework. They can also work on much smaller projects. It is just a tool to use.

All of our company members and all of our customers currently use the .NET Framework. The programmers write based on that .NET Framework. We define the scope of our work based on the project. Some projects need four to five programmers, but on some projects need ten to twenty staff. It depends what has to be done.

We can scale at any time except with some limitations on operating systems. By making our applications based on .NET Framework, our applications run already on the .NET Framework for our clients. When we do the development for our programs based on .NET Framework, our customers who want to use this solution also have to use .NET Framework. This is why it is a little limiting.

The technical support is really, really good. Every time that I ask a question on the Microsoft Network, someone answers me and I never have felt ignored when I need some type of support. I am very satisfied with their work in supporting the .NET Framework.

Previously, I used C++ for my development and it wasn't over any framework. It was the mentality at the time. When I saw the benefit of using a framework like .NET, I saw the simplicity of working over frameworks and the development advantages. That is when I decided to switch over to .NET Framework.

Installation is very straightforward for the Microsoft .NET Framework. I never heard any complaints from any of my customers. Even those customers who still use a lower version of Windows like Windows XP or Windows 7 don't have problems. Because .NET Framework is not pre-installed on Windows 7 or on Windows XP or 7, the customers need to install it themselves. But on Windows 8 and 10, Microsoft .NET Framework is pre-installed.

I never heard any complaints from my customers who couldn't install the .NET Framework, and none have said they had difficulty with .NET Framework. They all have said they could install it very easily and get running with it without a problem.

How long will it take to make it do what you want depends on the things you want to accomplish. Some products take more or less time to deploy and some solutions take more to build. But the .NET Framework is very fast, not hard to learn, and even amateurs don't have a hard time with deployment and getting started.

We deploy this solution by ourselves. We never have had to reach out for help from vendors or other consultancies for the product itself. The programming is a different thing and is not the fault of the product.

One advantage to Microsoft .NET Framework is that it is a free product and everyone can use it. It is a very good point about that product because it makes it friendly and easy to adopt over many users. The solutions and use of technical support are free as well.

We did evaluate at least one other option before choosing Microsoft's .NET Framework. It was JAVA Bridge, but I prefer to use Microsoft .NET Framework because I only wanted to develop for Microsoft products and Microsoft Windows. The .NET Framework is, I think, more compatible with Windows than JAVA Bridge Virtual Machine.

One piece of advice that I would give to people considering the use of this product is to use it because of several things: it is free of charge, it is fast, it is compatible with Microsoft Windows, and whenever a new version comes out, it supports the older version. These are all very good points. The development of the framework is really good and was approached intelligently.

If considering other options, when you want to use a framework, you have to look at its ability to work with different types of other products. With the.NET Framework, you are able to work with different environments like Microsoft SQL Server 7, MySQL, Oracle — any kind of database. You have to also know its limitations. It is my opinion that when you want to use the .NET Framework, it is a very good solution and you can have confidence in the functionality. The stability of the framework you choose is very important.

On a scale of one to ten with one being the worst and ten being the best, I would rate this product as a ten because my standard is Microsoft products.

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.

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