Microsoft .NET Framework Reviews

We primarily use this solution for point-of-sale and finances. We also use it for maintaining student information, details about teachers, attendance, and grades.

The most valuable feature is the financial accounting.

This solution should include Power BI so that we don't have to use any third-party tools. Including business intelligence tools would allow for easy understanding and quick decision making. It will help as it is for summarizing all of the business-specific analytics.

We have been using the Microsoft .NET Framework for six years.

The Microsoft .NET Framework is 100% stable. We have to use it for our day-to-day activities. Also, based on the business functionality you have to keep upgrading.

This platform is easy to scale. We have approximately 100 users, five of which are administrators and the remainder are business users.

We have been in touch with Microsoft technical support and we are happy with their work.

Prior to Microsoft .NET, we used Oracle DPK. The problem with DPK is that it is old technology that was used ten or twelve years ago. It has some limitations regarding client-server models.

We switched because .NET is a very flexible framework for enhancements, and it is cost-effective for developers.

The initial setup is easy.

We used consultants for the deployment and we use third-party business intelligence tools for the integration.

We did have the option to go with PHP and Joomla, but we were concerned that it may not be available after a few years. When it comes to Microsoft technology, it is more stable and because they are a giant in technology, .NET will be an everlasting solution for which we can always find developers and support.

This is a product that I recommend.

I would rate this solution a ten out of ten.

I use this solution for infrastructure work and Business Intelligence.

The most valuable features are the Domain Controller and the WBFS Manager.

The integration services allow us to connect to resources like Oracle.

There are certain tools, such as Oracle, that this solution does not integrate well with. The performance is slow and the connection takes a long time. Better integration with other tools to make the operation faster would be an improvement.

I have been using the Microsoft .NET Framework for one year.

There were problems with the older versions of this solution. The newest version is stable, but sometimes you have multiple versions installed and you have to switch between them. You don't always know if you're compiling with the most recent version.

I am the only one who is working with this solution in my company.

I always use the community chat and my experience with it is very good.

The initial setup is easy. Finding services is easy on the service tab. You can install the features that you want to use. It is better than using the Control Panel to add features, which was the old way to do it.

This is a solution that I recommend, but the best versions to have are 3.5 and 4. 

I would rate this solution an eight 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.

The .NET Framework is the foundation for software design and development. This is the context that I use it in, and the perspective that I view the discussion about it.

Coming out of C++, the .NET Framework simplified operations dealing with the allocation and deallocation of memory spaces and the additional processing resources. Adding this feature to the .NET Framework has freed countless hours of leak management. 

The addition of generics to handle common functionality across types, and the more recent upgrade of the dataset to the Entity Framework, has cut development time drastically, while increasing quality and confidence between builds. Finally, the test framework allows for increased velocity. 

Most recently, the updates tot he Entity Framework, and the addition of the ability to work with mobile applications have also been huge additions

• Stronger security with respect to cloud issues
• Greater flexibility with data connections
• Better control
• Extensibility of the framework as a whole

Changes in technology generally happen faster than any single entity can keep up with. But the side-by-side Runyon capability handles most stability issues behind the scenes. 

Only the ones that were fixed. 

I have not had to use the support.

No.

It is straightforward. All the components are readily available.

Started as part of a school program.

I can't measure ROI, because I've never used a different technology stack.  Switching from one to another has not been an issue. 

Do your homework. Consider the partnership program.

No.

With the advent of IoT, combined with cross-platform development, the .Net framework becomes much more versatile. We should begin to see apps scaling down in size, but also (literally) covering more ground. 

We have multiple in-house leasing and financing products (Contract Management System, Point of Sale, Credit Acceptance Management, Field Force Agent, Document Tracking) developed on .NET framework 4.5.2 with WPF, Silverlight, WCF and WWF technologies. We use smart client applications for client-side and Business Process Manager (i.e. based on WWF) for orchestration of business processes. We also have proprietary Task Assignment Workflow which is highly configurable based on business rules. Our clients can create custom business rules with the help of the data dictionary shared with them.

The product is evolving, based on the day-to-day needs of our customers and we are making sure to include maximum functionality to support their businesses. The main focus is on "more configuration and less coding," by using industry standard tools.

• Business Process Manager (BPM)
• Business Rules Engine (BRM)
• Document Management System (DMS)
• Automatic Release Deployment via PowerShell and Octopus
• Integration Hub serving as Enterprise Service Bus
• Metadata (i.e. compose database tables/columns, XML nodes; file data into placeholders so they can be placed in BPM, BRM, DMS)

I think we need improvement in our BPM module so that can become more user-friendly for our customers. There is plenty of room in WWF for improvement to make the UI/UX better for the end user, so they are comfortable with the orchestration.

We have issues with websites that are based on Angular, but the rest of the applications or websites are stable so far.

The only issue I have encountered is based on Queue Management. Regardless of whether it is Microsoft or IBM Message Queue, I have had issues while scaling them. The only option I have found is the introduction of multi-threading, but threads consume more processing power.

We were previously using PowerBuilder and then switched because of industry demands for transformation into new technology.

I would rate it at eight out of 10, as we can perform plenty of improvements in all our current products and can improve the UI/UX to meet the needs of the client.

As hardware evolved as mainframe, mid-range, mini, micro, personal computers (PC), while miniaturizing the silicon chips and other computer parts, computer software evolved as operating systems, systems software, computer applications, files (to persistent data), databases, etc. After mainframe applications, there was an age of client server software with PowerBuilder-Sybase-Oracle-Visual Basic.

Later came the web applications, where a client computer communicates a request to a server computer and the server computer sends a response to the client computer, in the form of static HTML. The browser, like Netscape or Internet Explorer, captures this response and serves it as web page on the client computer. Though the web request-response is here, still the "forms-with-fields-and-buttons" or "PDF-or-word-report"....

With the advent of client-server and web technology, applications went from monolithic spaghetti-code software to 3-layer and later, n-tier applications. Computer application code became structured and modular, functional, distributed (COM, D-COM and remoting), object-oriented to these days service-oriented web service-based applications.

All these days, Microsoft was walking hand-in-hand with other technology vendors, leading in some innovation and following in some. Microsoft was a large part of this entire IT revolution. Microsoft technology coding practices evolved from MS-DOS, Q-BASIC, MS Windows, client-server oriented Visual Basic, Visual C++ and application-friendlier COM components, and ActiveX. With the web era, Microsoft introduced server-side script (VB Script) and client-side (browser) (JavaScript)-based ASP (Active Server Pages). Until this point, the concept of .NET and the .NET framework was not in the picture. HTML pages were static and an attempt was made to introduce dynamic content (for server-side and client-side validations, custom processing, database handling, third-party component handling) with ASP (Active Server Pages)-based systems.

Microsoft thought of a better way with the introduction of .NET-based languages and the .NET framework. Here, Microsoft tried to generalize between the commonality between their various software products like coding languages (VB, .NET, C#, etc.),MS Windows, Microsoft Office, MS SQL Server databases and other products. These common components were introduced as the .NET Framework. The framework had a common language run-time, memory management (Garbage Collector), error handling (EXCEPTIONS), database handling block using ADO.NET and so on....

With Microsoft .NET, the dynamic web content handling became easier and the Microsoft world of web became more programmable with use of reusable and redistributable web components and systems (building blocks). The .NET framework was the core part of all Microsoft products. Data became more accessible. Forms and user interfaces became more friendlier. There is Microsoft Practices and Patterns guidance to the computer world, in designing, development, implementing, unit testing, archiving, etc.; the entire Software Development Life Cycle of the IT universe.

With Microsoft technology ,IT was as simple as the game of building blocks.

Due diligence is always given in IT technology by all IT vendors and their technicians. It is a complete rotating earth in its universe. What improvements you can suggest for the Great Wall of China or the TajMahal? The IT universe is agile.

Computer systems became a network of computers (intranet-internet) and now are social request-response driven. Web systems were request-response and now web services, WCF, Web API and SOA are making it more data driven, like fifth-generation computer systems. Soon, these computer systems will adapt to artificial intelligence technology and natural language interface; machine learning, big data will be common place. The future could be more nature driven.

I have been using the Microsoft .NET Framework to develop and implement application software for around 15 years.

I have not encountered any deployment issues.

I have not encountered any stability issues.

I have not encountered any scalability issues.

Customer service is excellent.

Technical support is excellent.

The ROI is excellent.

Microsoft technology is becoming freeware and cross-platform, embracing all changes and suggestions from the rest of the IT world.

I use the product to build websites and web pages. The product is also useful to connect to Sitecore.

The most valuable feature of the solution stems from the packages offered by the product.

There are constant improvements in the product.

I would want the product to be integrated with the different AI tools in the future since it is one of the areas where the product has certain shortcomings.

I have been using Microsoft .NET Framework for a year. I am a user of the tool.

It is a stable solution.

More than 100 people in my company use the product.

The product's initial setup phase wasn't difficult at all.

The solution is deployed on an on-premises model.

The product is not expensive.

Only if I know the purpose for which someone requires the product will I be able to recommend it to them.

I can say that users can trust and use Microsoft .NET Framework.

Microsoft .NET Framework's CLR has benefited my company's projects.

I am happy with the product's user interface, scalability, integration features, and support.

It is easy for someone to learn about how to use the product.

I rate the overall product an eight out of ten.

We use Microsoft .NET Framework for developing plug-ins for different software.

The product has a good interface and easy-to-use programming language. It fits our technical requirements.

The runtime environment for ASP.NET needs improvement to make it more universal.

We have been using Microsoft .NET Framework for three years.

We have 50 Microsoft .NET Framework users in our organization. It is a scalable platform.

The initial setup is easy. It takes several hours to complete and requires a team of four executives to work on the process. Its maintenance has medium complexity. We need to ensure the system's compatibility before doing any further updates.

The product has good technical support services compared to the Java Spring Boot's ecosystem. It provides centralized support, which is helpful for developers.

The tools you use are more important than the framework language. Microsoft .NET Framework is a good choice to develop software from scratch. However, having a licensing ecosystem in your organization would be best.

I rate the product an eight out of ten. It is a solid framework and runtime system supporting different languages.