Microsoft .NET Framework Reviews

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.

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.

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.

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.

I have built many things in Microsoft .NET Framework. At a high level, the main focus would be on integration.

Microsoft .NET Framework is primarily for the integration of solutions.

It enables us to do rapid development. We can develop solutions very quickly.

It is easy to use, and it runs on a Windows platform.

The .NET Framework is a very good framework. It does what I need it to do.

I have been working with different versions of Microsoft .NET Framework for 15 years.

Microsoft .NET Framework is a stable solution.

It's a scalable product.

In our organization, we have 700 users.

Microsoft technical support is excellent.

The previous solution we used, was also provided by Microsoft and Microsoft retired it.

The installation is straightforward. It's very easy.

It took an hour to deploy this solution.

We have a team of five analysts, and developers to maintain this solution.

Hitachi Consulting and Oracle Consulting have assisted us in other companies.

Microsoft .NET Framework is licensed under the Windows License.

My advice to others would go to get some training. This solution is best used with some training.

I would rate Microsoft .NET Framework 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.

For testing purposes, we deploy it on our own server (on the Infrastructure server). For our production, we're deploying it on AWCC too.

Nowadays, Microsoft is trying to fix a few things and build a framework faster than other frameworks. There are a few reasons to choose .NET. However, my supervisor selected this framework for a few scenarios, and our scenario is also quite a good match with the .NET Framework. 

We are using, the .NET Core Framework right now. It's the Core platform. They are releasing a new version, and the new version is becoming faster and easier to use compared to other frameworks and other languages. 

The initial setup is easy.

They offer good CLI support.

It's easy to create and integrate things.

They're improving many features day by day. Maybe other kinds of support would be helpful. Making it even faster would be welcome. Their ORM is a little bit slow compared to other ORM. That said, comparing to the current version and previous versions, their ORM is now much faster.

They should try to improve their Blazor WebAssembly.

Previously, we used to face difficulties in designing a pattern or this kind of feature. However, right now, they're improving this so it's easier to write than it was before.

I've been using the solution for three years. 

The solution has been very stable and reliable. We haven't had issues with bugs or crashes. 

In my company, we have more than 100 employees, and more than 50 are using .NET Framework.

Compared to the previous version, the current version is more scalable in .NET Framework.

I've never used technical support. 

I'm also familiar with Java. 

The product was easy to set up. It was not an overly complex process. I'd give it an eight or nine out of ten for ease of deployment. Their CLI support is very good. 

The deployment itself is fast and takes about 20 minutes or so. I'm using a Windows server. It might vary based on dependencies. In our case, it was very straightforward since we had everything set up and ready to go. Only one technician was needed to set up the server. 

We do not have to pay to use the .NET Framework or other kinds of frameworks. 

We are end-users. 

I'm not sure why the company decided to use the solution. However, they have used it for a while. 

Choosing a framework totally depends on the scenario and project. If you want to build an interface, then the .NET Framework will be good. That said, a Java framework also will be good. I'd recommend either of those frameworks in general. 

I'd rate the solution eight out of ten. they are always trying to improve, unlike other frameworks or languages. There are also good features and a good community around it. 

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.