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.

I work in the supply chain and transportation space. NET Framework is the core part of the technology stack. We had to build everything, including the Windows system.

We could spend more time building the application than building the framework. We've been using it since V1, and .NET has grown and changed multiple times in different directions. It brings more to the table each time, so we need to build less and less. If you think about containerization, you get that from the .NET framework.

Microsoft .NET Framework reduces the cost of entry and enables the development of applications with mature and enterprise features, thereby lowering the entry barriers.

The learning curve could be improved.

I have been using Microsoft .NET Framework since its inception.

The product is stable.

The solution’s scalability is good. We use the .NET Framework as a stack component in our project to develop software. Everyone from cybersecurity personnel and architects to customer service support uses this application.

There is a community providing solutions. Many others encounter the same issue with .NET and search for solutions online through Google.

Positive

The initial setup is very easy. We can usually get something spun up and running in a day.

The product is free.

Microsoft .NET Framework is a framework for development. We use cryptography, messaging, and many other components the platform provides for our development work. We are prototyping with the latest framework, which includes a mixed model of HTML rendering. This model is a blend of client-oriented applications, where most tasks are performed in the browser, and server-side applications, where the server renders the HTML for the web pages. The latest offering simplifies administration and development for simple pages while enabling the creation of highly interactive pages resembling control screens and back-office control centers.

We've used ASP.NET to create web UI. You might have business rules and logic running on your server. You have databases and frameworks for interacting.

We use C# and VB.NET on the backend and SQL for the database. The platform is good at implementing standards for web services. With .NET, there are competing standards, depending on whether it's coming from Microsoft or Oracle. The platform is very good, providing standards-based programming models.

The ease of finding and using third-party libraries with the .NET Framework is extensive. We use some libraries, but many more are available.

A single person is enough for the solution's maintenance.

The .NET Framework requires maintenance like any other deployed software, with patches and updates being essential to maintain. It's important to stay updated and evaluate these patches as they often address security threats. One of the major security risks in the .NET environment arises from using outdated software with known exploits. For instance, a vulnerability discovered in a particular version becomes a security risk until patched. In such cases, a patch is released, and while most companies apply it promptly, some may lag, leaving them vulnerable to attacks. These unpatched systems become easy targets for attackers, exploiting well-known vulnerabilities. Therefore, the patching process is crucial for maintaining security.

Overall, I rate the solution an eight out of ten.

I've been using the solution on the Microsoft Platform because it's very tied up with the Windows Server operating system, as it is with the Microsoft technologies. I would basically use the solution anytime that I wished to do something very efficient on Microsoft, building a software for example, which can be done on Microsoft Platform efficiently. I see the solution as the proper alternative to such programs as Java and Python. I prefer Microsoft.NET framework as it's actually tied with the Microsoft operating system and network.

So, the main advantage of the solution for me is that it's really tight. It starts with the component of the server side and proceeds to accessing the database. Work with it is really smooth with Microsoft technologies. There is no worry, no bother. Microsoft technologies is really straightforward.

Microsoft Platform is the only viable solution when I wish to do something that is not supposed to be cross-platform. This was the case later on with the .NET Core. Although we tried to obtain this on the Linux platform, we found things to be somewhat limited, as the .NET Core didn't mix very well with the Linux kernel. This is why we did not adopt it so much on Linux and prepared to do it with Python and Java, as the .NET Core was less powerful than the .NET Framework on Windows. As such, .NET Framework is better to use on Microsoft, on Windows Server. To me, Windows Server is actually the best when one wishes to do something for Windows Server but does not desire that it be cross-platform. It offers much integration. 

While Windows Server is always the best, the interoperability and, of course, cross-platform features could stand improvement. Ideally, the .NET Core should be made more efficient than it is at present. There is a need to be at the level of Java, for example, to truly overcome the weaknesses involved.

Price fraction on the Linux Platform and macOs Platform should also be taken into account. Then it will really be effective on those other platforms. 

It is of great concern to us that the solution is not very powerful on cross platform, at it impedes the ability to build and scale with it. There are many who would like to have their servers on Linux, since hosting Windows Server, even on VPS or in any hosting company, is very expensive. It will also be expensive in the long run. Keeping it secure will be expensive. It is cheaper and easier to get it secured, to get the best performances, with Linux. Most applications that our customer companies are using they wish to have on a server and then to access it from any type of tool, computer, or smartphone, which is what we would like for ourselves at the moment. Many are interested in the type of deployment whereby the application will be set on a server with web services.

For the .NET to really be at the level of some of the tools we are using now, it is better that Microsoft should start on the .NET Core so as to make it as powerful as possible on the main Linux distributions.

This would increase my rating of the solution.

If Microsoft could put the .NET Core at the level of the other platform I would even rate it as a nine out ten.

For the moment I can only give the product a rating of five out of ten since only some of the customers will be satisfied, those that have the financial resources for hosting a platform on Windows Server. They would need to finance a team that would work to keep everything running with security and to be capable of scaling up anytime they want. A dedicated strong team for this purpose costs money. 

While there are those companies that have the money and can afford this expenditure, others that don't will opt for the cheaper solution of using Linux, which has the potential for providing the same results. 

Moreover, I would like to have interoperability with AS400. We have not done many things with the .NET and prefer using certain other tools towards this end. When we want to work on AS400 we need to use some other tools for that on Windows. If Microsoft could resolve this issue it could attract a wider array of customers. We have very powerful software running on AS400, so the its interoperability capabilities are important to resolve.

I have been working with Microsoft.NET Framework for 20 years and I have been doing so since its inception. After having switched to open source I then reverted back to the solution. I have been using it since it came out with its early versions. 

Microsoft has tested the solution and our experience with it has shown us that, while it is not as fast as some of our other software-devoted platforms, it is very stable. It's integrated with the platform and very stable on Microsoft Platform. There are certain applications we build on it which work very well and we do not experience downtime.

The ability to build and scale with the solution is hampered by the absence of its cross-platform capabilities.

There is a need to choose the version being worked on and to obtain its appropriate components, at which point the installation will proceed as it usually does for Microsoft products. This is the point where the person must click repeatedly. The PowerShell commands can then be used. The person is presented with all the other Microsoft questions upon installation. When we work with the Linux system, we primarily prepare for use of PowerShell. 

I rate Microsoft.NET Framework as a five out of ten. 

I developed an application tailored for the oil and gas sector, focusing on risk assessment and activity mapping for wells across Brazil. This tool utilized the .NET Framework, specifically version 4.6, to ensure robust performance and seamless integration with existing systems used by oil and gas companies in the region.

The .NET Framework streamlined the integration of our enterprise-level applications by leveraging .NET service-oriented architecture. This approach simplified development as we could modularize our system into microservices, enabling us to assist each component seamlessly within the .NET environment, tailored to the specific scenario at hand.

The .NET Framework's interoperability with other applications and its language independence has proven invaluable for our development projects. In my latest project, I developed a portal application capable of simulating various applications tailored to different user roles within the company. Using the .NET framework, I created a secure domain model to manage user authentication and bill distribution across these applications. I particularly appreciated the .NET Bot framework for its ability to quickly translate existing class models into code, facilitating rapid development and seamless integration with our database.

The support for multiple programming languages in .NET has influenced our choice of languages for various tasks. As a team, we possess a solid understanding of .NET, making it easy to leverage its capabilities. While clients may not always have insight into the technical aspects of our work, the versatility of .NET enhances our productivity. This allows us to deliver results to clients more efficiently and encourages their active participation in the development process.

The security model of the .NET Framework significantly contributes to the overall security of our .NET applications. This is largely facilitated by our proficient IT team, who meticulously plan and manage the infrastructure. As our .NET applications are primarily utilized within our company's intranet, security measures are inherently more manageable.

The features that significantly enhanced our application's performance primarily revolved around integrations. For instance, in one scenario, our application was tasked with scanning field activities within the .NET framework, encompassing both onshore and offshore operations. It facilitated the streamlined scheduling process by amalgamating inputs from various sources, including location data and other systems. Users could input data and conduct simulations within the application to assess the viability of certain activities. Additionally, the application was backed by a database running SQL scripts to support its functionalities.

Improvements are needed in .NET development, particularly in a backend scenario. For example, if you're planning to develop an application to track project operations using .NET, a good starting point would be to adopt domain-driven design principles. This approach allows you to visualize all the relevant components within the .NET framework for such a project. You can begin by defining the core domain entities, such as projects, tasks, and locations, leveraging .NET classes to represent these concepts effectively. Additionally, incorporating a scheduler component in .NET to manage activities associated with each project would be beneficial. By organizing these classes systematically, you can streamline the process of generating database tables directly from your code.

I have been working with it for almost a decade.

The stability is outstanding. I encountered no issues, with any concerns primarily related to infrastructure servers rather than the .NET framework itself. I would rate it nine out of ten.

The scalability is exceptional. I would rate it nine out of ten.

We didn't require support assistance as Microsoft offers ample resources, including instructional videos, for implementing and resolving any issues independently. I would rate it nine out of ten.

Positive

The initial setup is straightforward. However, as operations start, a structured approach is essential. This involves establishing distinct layers of code, each with specific responsibilities aligned with the product's objectives. For example, if managing a product class, its functions should exclusively pertain to product-related tasks. Similarly, when dealing with a layer handling thousands of transactions, caution must be exercised to ensure it remains focused on its designated operations without encroaching upon other aspects of the project. This segregation of tasks ensures clarity and efficiency within the development process, despite its inherent complexity.

In our web and desktop application development workflow, we typically support IT personnel by providing them with the necessary components to set up a server for deploying our applications. We hold weekly meetings to discuss our approach and progress, and throughout the week, we collaborate on various tasks. Once the work is completed, we publish the applications to the server, ensuring that all required roles are fulfilled for successful deployment.

For deployment, we didn't have to do much as it was already completed for us. Additionally, we utilized GitLab and Jira in conjunction with Docker for streamlined deployment processes.

Overall, I would rate it nine out of ten.

The solution has difficulty integrating with other products. There are no such difficulties if you have the same platform, hardware, and operating system.

We have almost 15 developers using the solution. It has reliability.

Microsoft .NET Framework is lightweight. I work on Microsoft and Oracle platforms. Microsoft platform is easy to start working on, whereas Oracle is very difficult. Troubleshooting is complicated, whereas it's very easy with Oracle.

The maintenance of the Microsoft platform is very tough. You can start your development after three months of your start, but in the Oracle platform, it is not so easy. You will learn it; then you will start. There is no such difficulty when you start it. It is very easy.

The initial setup is complex and takes time.

When the development team deploys a new application, they prepare a new server. It is a very complicated task. It has dependencies.

More than one person is required to maintain the solution.

Microsoft .NET Framework is a mature application. More than 50% of applications are on .NET Framework.

Overall, I rate the solution a ten out of ten.

We use Microsoft .NET Framework for testing and development for RPE.

The most valuable thing about Microsoft .NET Framework is that it is an enterprise-grade language and platform.

Microsoft .NET Framework has a steep learning curve, which could be improved.

I have been using Microsoft .NET Framework for five years.

Microsoft .NET Framework is a stable solution.

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

Microsoft .NET Framework is a scalable solution. In my previous job, around 20 to 50 users used Microsoft .NET Framework.

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

The solution’s initial setup is easy.

The solution takes only a few minutes or hours to deploy.

Just one person is required for the solution's deployment.

Microsoft .NET Framework is a free, open source solution.

We don't maintain the solution because it's a framework that does not need to be maintained.

I recommend users use the solution's online documentation because it's open and free.

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

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 in my company to build internal systems that are used for developing applications to run our business, and we also use it to call web services.

The most valuable component of the product stems from the fact that it works properly. I know it might sound funny, but you don't have to go and get other third-party solutions when using Microsoft .NET Framework. With Microsoft .NET Framework, you also don't have to do a whole lot of extra configurations to make it run. The tool offers a lot of support, and there is a lot of knowledge material available, along with a lot of community groups. If you have an issue with the tool, you can find someone to help you pretty easily.

I think the main thing that my company wants is Microsoft .NET Framework to provide us with more integrations with Azure, like in the area of DevOps in Azure, which can improve its management and work in the cloud. The tool is good, but it can be made a bit better.

The product's price is an area of concern, making it an area where improvements are required. The product should be available at a low cost.

I have been using Microsoft .NET Framework for about fifteen years. The older version of the tool is automatically updated.

I have not faced any issues with the stability of the product.

Considering what cloud services can support, the scalability offered by the product is unlimited. I feel that it is a scalable solution.

My company has around 12 to 15 developers who use the product.

In terms of the size of Microsoft .NET Frameworks' environment, I feel that as a cloud-based product, it serves as a system to the customers, so it can serve the needs of hundreds of customers, meaning there are no real size limitations. The on-premises version of the tool that our company has been running had 350 people running through the applications on-site, and it was running every day with thousands of daily transactions.

I believe that the developers in my company have raised issues with the product's support team. I believe that it was never a challenge for my company to find the right person who provides the right solutions. My company has dealt with difficulties in a few technical areas attached to the solution, especially in the area of integration, but I don't remember any major issues with the solution.

Microsoft support is okay. If you are aware of the community practice when it comes to the tool, you can pay for Microsoft .NET Framework's extended support, as it can be helpful. The support is really good. I rate the technical support a seven out of ten.

Neutral

As long as somebody in your company understands how the tool works, handling its setup phase is not complex. If you are learning to use the tool for the first time, the setup phase can be difficult. You need a good understanding to start with if you want to do the setup phase easily.

During the product's deployment phase, our company just needs to push the product through the pipeline, which is a very easy process. Putting the code out there is pretty easy since Microsoft processes work quite well in a simple manner.

My company has not looked at the tool from an ROI perspective since it is a product we need to use. Along with the stack of Microsoft products, Microsoft .NET Framework is a tool that works for our company.

In our company's development projects, the code is built using Microsoft .NET Framework, which is valuable and beneficial.

In our company, we have a system internally that runs several contracts that we do, and it provides a workflow application that people in our organization basically manage to make sure that the workflow for the contracts we hire is completed, so it has a lot of business rules in it, meaning it has a very strong business rules engine. The other main process our company uses is in building the cloud solution that is focused on how you deliver durability to end-customers because it is a tool that can be used in a very extensible manner, leading us to use it a lot.

The interoperability of Microsoft .NET Framework with other languages and platforms affects our company's projects since it allows us to build whatever we want. There are no limitations in the tool, and as long as someone in our company has an API we can work with, we can build a connector tool, so it is quite open to what it can achieve. In general, with some of the low code areas, you may start to run into challenges while doing some integrations and maintaining them, but with Microsoft .NET Framework, it is very simple since once something is built, it works fine, especially when doing updates and changes, it is an easy process which is not a difficult thing to manage at all.

The product's security features are fine, but I feel you need to follow a security-by-design approach for all software environments. Microsoft .NET Framework usually enables what you do, but it does not make it happen for you since it only serves as a toolkit.

The performance and the scalability of the applications developed in Microsoft .NET Framework are fine but my has got certain things on Microsoft .NET Core is on Microsoft Azure. It can take as many customers or as many users as Azure can handle, making it a very extensible tool.

The product is not difficult to maintain.

The integration of security and network of the tool has benefited our organization since we can easily integrate SIEM, SOAR, or NMS tools.

I recommend the product to others who plan to use it. I believe that you need to invest in getting to know how to use and run the tool.

 I rate the tool a nine out of ten.