The others, like React and Angular, use freeware Apache licenses. 

React is maintained by Facebook, Angular is a Google product. Microsoft has Blazor, but it lags behind. React and Angular are much faster. 

For example, React has a virtual DOM, so if you make changes, only the changed section of the page updates. It uses one-way binding, which makes it quicker to respond. Microsoft's approach involves a full-page lifecycle.

Even compared to Angular, it's different. Angular doesn't use a virtual DOM, but it leverages an MVC framework behind the scenes. 

In terms of the end product, there's some overhead. If you build an app and publish it to AWS or Azure, these applications tend to be a bit larger.

I have used a Java development environment. 

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.

I worked on alternate servers to build the .NET applications. I have created some pipelines for the automation practice.

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.

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.

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.

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

No.

I'm also familiar with Java. 

I"ve used Java previously and find it a more portable solution. 

We have had experiences with Oracle as well as .NET, specifically with the Silverlight framework, though that was some years ago. Silverlight, while not inherently bad, tends to be criticized, and I often advise people to understand its origin as the Presentation Foundation Everywhere (PFE), indicating its intention to provide a unified UI across various platforms. However, due to various challenges, it was eventually phased out, and Silverlight became obsolete. We once had a product active on SolarWinds 3.5, transitioned to SolarWinds Sorin, but unfortunately did not survive beyond Silverlight 5.

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

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.

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

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.

We did previously use a different solution. We switched because of the lack of quality within the other solution. The way Microsoft adapted to the corporate customers, offered stability and scalability, and also the quality of support were some of the reasons we switched.