Microsoft .NET Framework Reviews

I use .NET Framework for development because my client uses it. It was already in place when I started the product. They work with .NET because it's mainstream and .NET programs are widely available.

Pre-programmed functions for .NET Framework are widely available.

I would like more web integration.

I have been working with .NET Framework for the past two years.

The framework is stable, but it depends on the size of the application. If it's a larger application running on multiple machines, you may experience issues because it's on Windows, the least stable platform. 

The initial setup is easy, and it takes less than half a day.

I rate .NET Framework seven out of 10. If you are using .NET, make sure your setup meets the requirements because that was an issue that caused a lot of problems.  I would recommend Magic rather than .NET. It takes longer to develop something on .NET. The framework has extensive possibilities, so the learning curve is steep.

Our primary use case is custom business applications, Integration services using WCF/Web API.

Using this framework has enabled us to create services out of things things that we used to do manually. Not only has it made our lives easier, but it has increased productivity as well.

The most valuable features for us are web frameworks like MVC, Web API, and WCF.

I would like to see more pre-built features in the MVC framework because as it is now, it's very open and you have to develop your own controls in order to use it. It would be much easier for us if there were more pre-built controls.

There should be more security features included.

The performance should be improved.

The technical support is in need of improvement to make solving issues more efficient.

I have been using the Microsoft .NET Framework for more than 16 years.

This is a very stable solution and we haven't had any issues.

This is a scalable framework but it depends on how you deploy the solution. Because it is a framework and not a product, it will give you options on how to develop your solution. If you develop it in a way that is scalable, then it will be scalable. But if you don't develop it properly then it will not be scalable.

In my previous company, we had approximately ten thousand users.

In my current company, we only use this solution internally. We have fewer than ten people, and they are business users. We do not currently have plans to increase usage but it may happen in the future.

On a scale from one to ten, I would rate Microsoft technical support a seven.

Whenever we are trying to solve issues by dealing with Microsoft, they ask so many irrelevant questions that it delays things.

We are also using WebLogic Suite with SharePoint on the server-side.

The initial setup was straightforward and the deployment took not more than two to three days.

We implemented this solution using our in-house team.

The Microsoft .NET Framework is free of charge, without licensing cost. The only cost is purchasing the hardware that it runs on.

Java SDK. Java SDK is also good but require little bit more effort.

My advice for anybody who wants to use the Microsoft .NET Framework is to have the proper foundation before implementing the solution. This means that they should lay the architecture first, properly, and then develop the solution based on the architecture. Without this, the solution will not be scalable and will suffer from problems in the long run.

This is a good solution but there is always room for improvement.

I would rate this solution a nine out of ten.

We are part of the development team.

We use this solution with TFS as our ALM tool, and we use the information server for the deployment.

We have been using this solution for development for a long time and it has proven to be helpful.

The .NET framework is a mature platform that is very helpful and saves time during the software development process.

The IDE is quite helpful.

There is a lot of very extensive documentation available.

The price of the Enterprise version is quite high and can be improved. If Microsoft would provide a monthly subscription at a cost that a developer can afford then it would be really helpful.

From a security standpoint, the tools are not that mature.

I have been using the Microsoft .NET Framework for more than 25 years.

This is a very stable platform for enterprise development. It has been maturing since its inception and is very helpful for delivering products.

We have dealt with the technical support team and they are very helpful. Whenever there are issues, especially when troubleshooting in a production environment, Microsoft and the support people provide a lot of technical expertise and we are very happy with it.

This product is really helpful when compared to other solutions such as open-source platforms. All of the tools are interlinked, rather than having individual tools for individual features. What Microsoft provides is a complete tool, with all of the features contained.

The initial setup is easy. There is a vast amount of resources made available by Microsoft and a lot of guidance being provided to the developers. 

I lead a development team and the team members perform the deployments. There is a lot of guidance available on the Microsoft website that is really good, so the deployments are not troublesome.

There is a Community Edition that can be used free of charge, but the licensing cost for the Enterprise version is quite high. Some of the tools that are available in the Community Edition need a valid license to run.

Compared to other vendors, Microsoft products definitely have a higher price tag. I would say that is my only grievance.

Talking from an application developer's perspective, this platform is very helpful because it provides a common development line across all of the products that Microsoft provides. This includes things like Microsoft Dynamics, the Cloud Integration tool, and SharePoint. It makes it very easy to jump from one application tool to the other.

The Community Edition can be used free of charge and is helpful for both new developers, as well as those who are shifting to the Microsoft platform.

Over time, this product has matured and all of the new features have been helpful in improving the performance of application developers. Overall, we are very satisfied with using this platform for application development. It is very good. That said, there is always room for improvement.

I would rate this solution a nine out of ten.

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.

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.

I'm an associate professor of computer engineering.

The solution is user-friendly and straightforward. I enjoy using it.  

It's a little difficult to scale this product for large organizations.

I've been using this solution for 10 years. 

It usually takes a few months for each new version to become stable. 

Scalability is a bit messy so we're forced to use different solutions for different clustering. 

We're satisfied with customer service. 

This is a good product and although it's not suitable for everyone, we're able to support various clients who use this. 

I rate this solution seven out of 10. 

We are working with version 2019, but we have clients who are still on older versions. We deployed the solution in 2014 or 2015 and they still haven't upgraded.

Cross-platform development is better than all of the other frameworks. When it comes to the user interface, the context is better than other tools because it is easier to use. You can still use C# in the developer infrastructure, which makes it far better and you don't have to learn a new language.

For me, the cost is what is most important. We have an agreement with Microsoft to co-sell some of the applications. When we started developing using the Microsoft Framework, it went well because we started making more money than the cost to Microsoft. We don't have this agreement with Red Hat or JBoss.

One thing that I like is that from the usability point of view, nothing has changed all that much. We use Visual Studio and if you compare the older version of Visual Studio from 2013 to the 2019 edition, the scale is still there. You're not moving to a different environment and you are still able to find your way around very quickly. With the new features, we are still able to feel those out within a short period.

For the mobile application, I like the iOS interface. Android is a little different from what you have on iOS, but the iOS package includes the same thing.

The pricing could be cheaper.

They should have more training materials available that are specific to .NET. We spend a lot of money training our engineers. I think that it would be better if there was more training available to the partners who invest in Microsoft.

At this time, the training is all over the place and there is no specific certification.

This solution is not scalable with older versions without using patches for it to work.

I have been working with this solution for more than ten years.

Microsoft's strategy is not scalable, especially with the Visual Studio environment. If for example, I am testing things from on older version, it's not available in the newer version. You will have to use notes and the patches for it to work.

Currently, we have two enterprises. One of them has over 1000 employees and an IT department with 200 developers.

The technical support has been excellent. If you are working with them, they are always there to connect with you all the way, which makes things so much better.

The first day takes a couple of hours and the second day is for the configuration and switching everything out to make sure that everyone has access to it. Then they test everything to make sure that it is fine and working. It's not a lot of work for us to do.

The support has been very good, maybe because we have a local office with resources.

Some of the issues with support is not with .NET, it's dealing with some of the packages that should offer support. One of the new products that Microsoft has introduced is called Dynamics 365, this is outside of .NET. We have been struggling to find someone for support, but unfortunately, it has to be through the US.

When it comes to everything else, the .NET Framework has a lot of support from the local Office.

If they struggle with .NET there is someone in the UK office that would be able to assist us.

The initial setup is easy for our guys who spend quite a bit of time with Microsoft.

Just today, one of the guys set up an environment for one of our clients on Azure. This was a Visual Studio environment and it took him two hours. He did not encounter any difficulties. 

We have guys take care of the server section and we have our developers that implement from the installation for the environment.

It seems very easy for them to get everything up and running.

Small clients don't do their development internally. We have three of these types of clients. Small to medium-sized organizations don't have an environment because they are easy to develop with easy requirements.

I would recommend this solution but it depends on the environment and what they want to do.

If you do mobile applications, to avoid the headaches of doing development on multiple platforms, I think that .NET is something that really works. We have tried everything, so when we try iOS it becomes a problem because we have to re-develop what you do for Android on iOS, even though we don't use Windows phones anymore. We can still use the same tools for your desktop applications.

If you have a different environment then you have to develop based on whatever application you are going to run your application on. 

I would rate this solution an eight out of ten.

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.