Microsoft .NET Framework Reviews

My main use cases for Microsoft .NET Framework are not fixed or specific tasks. My job involves working on different dynamic projects. My experience is with workflows and custom workflow engines. I have been the architect in creating workflow engines for BPM software, Business Process Management, where they use an online process for any process running in the company, such as leave requests or employee exit requests. There are many products similar to Kissflow and Microsoft .NET Framework workflow engine.

I have created my own product in one of the companies where we had our own workflow engine. In this company where I'm working, I have worked with multiple products, including Microsoft .NET Framework Workflow Engine. I prepared POCs for that and worked with several other products, including Camunda, which is a Java-based product.

The role of Microsoft .NET Framework's Base Class Library in facilitating rapid application development in my organization is that the code is much richer in C# because its main competitor is Java. Both compile to bytecode and intermediate language IL code.

Regarding rapid application development framework, Microsoft .NET Framework does not provide any type of that. As an architect, whenever there is a project, I need to choose from other libraries such as ABP Framework and ASP.NET Zero framework. These are open source products that also provide paid versions. If I have to start a project today, I will go for ABP, which runs on top of Microsoft .NET Framework. With ABP.io, you can deploy your application with users, tenants, role-based authentication in one hour. Developing APIs, services, and GUIs are done easily. Tasks that might take three to four days with bare metal Microsoft .NET Framework can be completed in four to eight hours with ABP.io, depending on complexity.

Microsoft .NET Framework has two versions. One is legacy, called Microsoft .NET Framework, with its latest version being 4.8.1, where they are maintaining it for legacy products. Their paradigm shift is toward Microsoft .NET, sometimes referred to as Microsoft .NET Core. Microsoft .NET Framework runs only on Windows.

There are many cutting-edge features that have surpassed Java, including delegates, lambda expressions, and async calls. These features make it very easy to write multi-threaded applications and create more responsive applications using the async framework. For parallel tasks, this is exceptional. Microsoft .NET has achieved significant improvements in speed, surpassing other languages including Java.

Memory management is automated in Microsoft .NET Framework through the garbage collector. We implement IDisposable interface in classes to clean up memory and free resources when an instance is not in use. This includes memory, I/O devices, or any resources used by the application. Unlike C language, we cannot manage heap or stack directly in Microsoft .NET Framework as it is automated through the garbage collector.

Microsoft .NET Framework has already made significant improvements by becoming open source. Many developers are contributing to Microsoft .NET Framework, not just Microsoft itself. They have ported it to many platforms and allow a healthy ecosystem of open source tools.

They have moved from Visual SourceSafe to supporting Git with Microsoft Visual Studio. Their IDE, Visual Studio Code, is open source and multi-platform. There are many third-party tools available, including AI-based tools such as Cursor and Bolt, which are forks of Visual Studio Code. Based on my understanding, I don't have any suggestions for improvement as they are already doing an excellent job.

I have been working with Microsoft .NET Framework since its inception around 2000 when Microsoft announced it. I started from the first version, working with Visual Basic and Visual C#. Now it has evolved into Microsoft .NET, which works on any platform including Linux and Mac.

In terms of stability, Microsoft .NET Framework servers have historically been more targeted by hackers and viruses compared to Linux, Unix, or Sun Solaris servers. This vulnerability might be due to greater familiarity with Windows products among hackers.

This vulnerability is inherently related to these products. Linux systems appear more difficult to target, possibly because fewer people have detailed knowledge of these systems. For instance, we once had a Linux server running smoothly for five years without physical maintenance, while Microsoft products occasionally face stability issues when compared to Linux, Unix, and Sun Solaris.

Microsoft .NET Framework is a powerful framework for scalability. We can write applications and native code where needed, and if some features are not provided by the framework, we can write unsafe code that runs directly on the processor. The capabilities are unlimited, but developers and architects need knowledge about working with languages C or C++, and calling those libraries from C#.

Microsoft products excel in terms of scalability. SQL server clusters run effectively in complicated environments such as banks, handling tasks such as deleting millions of records. I would rate its scalability 10 out of 10.

Technical support and service support are excellent because our company is a partner with Microsoft. We receive prompt support when working with ministries and banks. The support from Microsoft deserves a rating of 10 out of 10.

Positive

I prefer working with Java-based products such as Spring Boot and Java Hibernate for persistence. I am working with Microsoft .NET Framework due to job requirements, but I prefer Java products.

Deploying Microsoft .NET Framework is extremely straightforward. The wizard creates a package, and deployment is essentially copy and run. All dependencies can be compiled into one folder. We can also use Docker for deployment, making it even simpler.

Deployment time varies depending on methods used. I write automated scripts that connect to servers, copy files, stop worker processes on IIS, deploy, and restart the cycle, taking approximately five minutes. Manual deployment is also straightforward. Database changes might require more time for script preparation, but application deployment is very simple, often just requiring copy and paste operations.

The overall rating of 8 out of 10 for Microsoft .NET Framework reflects its performance and capabilities. The main reason for not giving a higher score is due to stability concerns when compared to other products.

We have been using the Viasat QoS, which is a web application platform. We are using a part of this web application.

Regarding Nexity, we are not getting whatever they are offering, but it is fine with Nexity. One thing is that for MongoDB, there is low and seamless support. For Microsoft .NET Framework, there is support. For MongoDB Limited, there is a year for MongoDB, which is something we are looking at. That is something that should be there. If it is great, and if there is not going to be often, it is going popular now. But there is real core support. We had to write our queries on the review report from Microsoft MongoDB as a machine that is possible or not. It is a nice more up section.

Right now, I am only doing the project. We are only two people doing the requirement. One is admin, but I am doing the deployment.

Microsoft security part is valuable, and also the mini V drive Microsoft .NET Framework six, the millivirus, and all these components. It is very good. The pipeline is excellent.

We have an annual application and a data application. There is a build process which will generate the documentation and a release process. We will deploy this application to Kubernetes. In any case, we are using Azure ecosystem, such as the AKS and Logistics. MongoDB is the best option for us.

The Visual Studio ID that we are using requires more RAM and IP. Sometimes it goes high on this phone exchange, and it crashes sometimes. We have to review this with Microsoft itself. That is something we do not understand. The breakage goes up, and I think it was the process that decreased, but still partitions are there somehow in Cloudera Selami. We do not even understand what the issue is. I think six more RAM would help.

I have been using this solution for more than sixteen to seventeen years.

The stability is very good. I have not experienced any problems here or any issues.

The customer service is a nine out of ten. They are very good support.

Before this, I was using Microsoft, but no other solutions.

The initial setup was very straightforward. There was not much time involved. It was very easy. The installation was not even one week. It is good to one week, but it is very easy to install. There is nothing hard about it. It is really easy to deploy, and it is very friendly.

This is good because it is very easy to get started. The deployment is easy with so much support. It is better to go with Microsoft .NET Framework. I would recommend it to other developers.

The return on investment is good because maintenance will come down. It is very easy to troubleshoot data. Everything now is better, and the ROI is even much more. It is definitely better than initial pricing.

The cost is very expensive. All in all, the system is good. I would give this product a rating of 9.

For development, we focus on specific projects.

We are an IoT company specializing in innovative solutions.

I don't know much about it as it's a development framework. We use it as it's a good language, a good environment with fairly good performance.

It's part of the Microsoft .NET Framework environment. Microsoft .NET Framework runs under the CLR, the same as Java runs under the Java virtual machine.

It's a rich library that helps with development. It's a good environment with many features and many libraries that help developers work quickly and efficiently. Since I'm using a very old version, there isn't much to add.

It's flexible, but since it's an old version of Microsoft .NET Framework, there are some limitations. As long as it can run on Windows, it's acceptable. The limitations are due to its very old version.

Some cloud features will not run in an old version of Microsoft .NET Framework easily or at all. Running on the cloud is complex. The support for a cloud environment, not as a virtual machine but, for example, in Azure App Services, proved challenging. I tried running a web application but couldn't make it work, although technically it should be possible. To run an older version, I had to make adjustments in the running environment, but ultimately couldn't get it to work. There's no support out of the box for older or very old versions.

The new Microsoft .NET Framework runs perfectly in the cloud without problems. This review concerns a very, very old version.

Since the version I'm using is many years old, they have been continuously improving. They are always adding features to the language and framework, but I cannot comment from a very old version on what needs to be improved as I'm not completely up to date.

There is a challenge and complexity in supporting a very old version of a product that is no longer supported. It's still possible with Microsoft .NET Framework, which isn't the case with many other products. That's a positive aspect.

It has limitations when trying to develop new things with Microsoft .NET Framework. But whatever works, continues to work.

It always needs improvement, but again, it does not improve when discussing an old version of Microsoft .NET Framework. I think they're always improving, but it's a never-ending process.

I'm using a very old version that is not supported, but I do have theoretical support if needed in newer versions. I am satisfied with the support when I need it, which is almost never.

It is stable overall.

I have not started using anything new yet, just checking various features.

I'm not using WPF mostly. I have few utilities but not much, so I cannot comment extensively on that.

My usage is not high scale. I used other tools in the past and I'm using Node.js but not at a very high level.

Microsoft is better in backward compatibility compared to others. The development environment is integrated and better than in other frameworks.

Positive

I don't know about pricing. I'm paying for Visual Studio, even though I'm not using the new version yet. Prices can always be better, but I think for the environment provided, the prices are acceptable. There is a free version available for the old version and also for the new version.

The runtime is on the cloud, with the local development environment on my machines.

We're running partially on private cloud, partially on public cloud based on our infrastructure.

The development language is scalable. These aspects will improve in the newer version when I upgrade. At the moment, I'm limited to what I have.

Everything is functioning with the current setup. Microsoft .NET Framework is a very old product. If specifically referring to using a very old version, then it shouldn't raise any questions because it's not relevant anymore.

Nobody's going to start a new project with it. Everybody that uses it just continues until they change.

On a scale of 1-10, I rate this solution a 9.

I get information from different endpoints as an aggregator. From that point, we create different map responses to create different information that we will use in different micro-frontend applications. It has different micro-frontends, similar to Jira with various widgets that receive responses from specific endpoints to display on the dashboard.

I have not been working with AWS technologies for a month, but it was the last cloud platform I worked with.

I worked with Elastic Search and Grafana. It was for tracking purposes, specifically with Kibana.

I primarily used ECS, databases with RDS, S3, common services, queues, and Elastic Search, though Elastic Search is not specifically AWS.

We started working mostly with Microsoft Visual Studio because we had services that we deployed directly on Azure. It was a small amount of microservices that we were publishing. The idea was that we did not want to use Visual Studio proper, rather than Visual Studio Code, for working because it was too heavy for the developers.

The structure that can be created is beneficial because once you have the structure, you can be more productive and faster to create and interact with different clouds and implementations. It should be something that costs more at the beginning, but becomes easier once the foundation is established. The first part of the project always takes considerable time, and the structure needed inside the company can be challenging initially.

We have been using it because it helps manage all the threads for each system and lines of business that need to be implemented or consumed. This provides a standardized project. Depending on how you structure the project, if you only have microservices without shared CLS, it could be problematic. However, with a segregated domain, you can leverage it in different APIs or endpoints. You have the same domain in different places. You can also put different responses in the response part, while the whole domain continues having the proper structure from the database if using an ORM. It depends on how you use it and want to use it.

The significant challenge is that you need an enterprise-level company to maintain software in Microsoft .NET Framework with a proper structure. With different programming languages, the development process might be faster. Everything is quite expensive initially. Since it is now open source, it could be easier to progress further. Future improvements could include integration with solutions that help reduce license costs, such as working properly with Visual Studio Code without changing all components in Visual Studio community edition.

It helps big companies significantly. At my level as a software engineer, it is not as visible as it might be to people in product or other company stages.

I mostly used different workarounds that I found or created different solutions to overcome problems. I never encountered a major problem that I could not solve independently or with my peers, so I never used the service.

I have used the solution for approximately eight to nine years.

The main challenge occurs when there are frequent changes. When systems need updates, they require proper long-term support (LTS) versions. Sometimes you want the latest features, but you might have version six, then two months later version seven appears, followed by eight and nine, with nine becoming the long-term support version. Reaching that point can be tricky when you already have established systems.

We primarily use Azure DevOps and have dedicated DevOps teams managing this aspect. We create different instances or rules that grow as needed. I have not encountered any significant issues with scalability.

I never used the first setup. I typically use a blank solution and then create things independently with different layers or structures as needed. It would be beneficial to have various boilerplates available for selection. These are common requirements at this point, and having boilerplates would make it straightforward to proceed. A dashboard that allows selection of different databases, architectural patterns, or structures would be helpful. For instance, if implementing GraphQL or setting up Swagger, having configurations readily available would be beneficial. Though it is manageable to set up configurations and extensions initially, having boilerplates would expedite project startup and reduce the barrier of extensive initial setup processes.

I have been working with Next.js, and in one of the projects, we worked with Azure using Microsoft .NET Framework applications that we deployed in Azure resources.

I was reviewing the website and understanding the product. It appears to be a tool for different technologies and approaches for solutions, serving as a consultant.

Once the software or application structure is complete, it becomes a matter of creating different domains and publishing. It would be beneficial to have architects establish a proper structure, allowing semi-senior or junior developers to follow up on projects. When they encounter issues they cannot solve, senior developers can address those specific challenges. This ensures senior developers are not constrained by moving domains or creating simple information endpoints, but can focus on more complex structural problems at their level.

Based on my experience, I would rate Microsoft .NET Framework 8 out of 10.

Whenever I need a back-end system, I create all the applications or all the products. For example, flights, hotels, and car engines have been created. .NET and Chase use my system, and I have developed flights, hotels, and car engines completely; the entire back-end system in .NET for them.

The APIs are completely effective. I can create .NET APIs very easily through .NET. For example, if I need to design any system, I can use C# and .NET.

Their system is very vast. I have spent 12 years here, and I can definitely say there is still a lot of scope for improvement. They have done a lot, however, .NET still has room to improve.

I think I have used the solution for almost 12 years.

The stability is very good right now. With the newer version, the solution is performing very well.

Scalability is good. The system has managed the scalability very well. The compatibility with Azure cloud system is very good from the scalability side, and I am deploying a lot of applications on Azure. I didn't see any scalability issues there.

Customer service is very helpful.

Positive

Whenever someone needs a very good back-end system or a strong system, they should go with C# .NET technologies. 

Overall, I would give it a rating of nine for .NET. This is definitely the way to go.

I use Azure DevOps because we have everything implemented in .NET by Microsoft, and we are integrated with the collection of the requirements, the .NET pipeline, and directing Azure DevOps for Azure Plus. I am more of a developer, so from an infrastructure point of view, I do not have feedback or experiences to share. I use it more for requirement documentation. For historical reasons, our product was born in .NET.

For us, it is better to remain under the umbrella of Microsoft.

They do provide the .NET library, however, for me, the most important capability we want to investigate in the future is the integration with Copilot. This would help speed up the development of the code and also the testing and documentation of the requirement.

I have used the solution for 20 years.

I do not know the pricing. I am not directly involved in the process. However, in the end, the cost of .NET is something that the corporation can absorb.

I do not think that now there is a reason to change our fleet. 

I rate the overall solution eight out of ten.

We use Microsoft .NET Framework to develop Windows applications. It is utilized for Windows form solutions to create Windows-based applications. Our team uses it in our software development process for data connectivity, user input form validation, user management, authentication, and authorization.

It is beneficial for running smooth operations on every application. We face minimal problems using it, allowing for stable and efficient operations.

All team management features, application management, core security, and integration capabilities are very helpful. It facilitates running Windows business applications and leveraging enterprise application development.

There is room for Microsoft .NET Framework to improve cloud platform capabilities. They have already made improvements in their new version by making it multi-platform and upgrading it for cloud platform capability.

We have been working with Microsoft .NET Framework for the last fifteen years.

Microsoft .NET Framework has a high level of stability, rated eight out of ten. The stability benefits our operations by ensuring smooth and reliable performance, minimizing the occurrence of problems during application usage.

Microsoft .NET Core is more scalable than the traditional version. By making it cloud-compatible, scalability has improved in their new version. However, as Microsoft .NET Framework is not built for the cloud, its scalability remains limited.

We manage it internally, and if any problem arises, we use online resources. We have never reached out directly to Microsoft technical support.

Positive

Before Microsoft .NET Framework, we were using the old version of Microsoft technology, Visual Studio 6. It was retired as it was outdated, prompting the switch to Microsoft .NET Framework.

The initial setup is easy to complete. On a scale of one to ten, where ten is the easiest, I would rate it a ten. No challenges or difficulties were encountered during the initial setup process.

The same team of five people handle the deployment and maintenance activities.

Microsoft .NET Framework helps in running smooth operations, which we value greatly. It is time-efficient and has saved us a significant amount of time.

The pricing is rated six out of ten. It provides value for the cost.

We did not evaluate other options before choosing Microsoft .NET Framework. Being already familiar with Microsoft products, it was easy for us to switch to their new technology.

I would recommend using the latest version of Microsoft .NET Framework, especially for cross-platform and cloud-native applications.

I'd rate the solution eight out of ten.

We use the solution for some internal applications we develop. We also use the Microsoft workflow engine.

When using Microsoft .NET Framework, you start writing the code internally. This reduces the cost on the licensing side, which helps reduce the overall expenditure of OpEx and CapEx.

The solution needs to update its security periodically because there are many security concerns. It should also provide audit reports so that it is easy for the auditors to see the security controls.

I have been using the solution for 10 to 15 years.

I rate the solution’s stability ten out of ten.

Microsoft .NET Framework is a scalable solution.

I rate the solution’s scalability an eight out of ten.

Since most of our developments are in-house, we are less dependent on technical support unless it concerns the engines.

Positive

The solution’s initial setup is easy. It takes around half a day to get the servers ready, install it, test it, reboot the server, and retest.

Microsoft .NET Framework is very cost-effective for corporate users. If you're on Microsoft, you have no choice but to use it. We have an enterprise agreement with Microsoft, and the solution comes to us as part of a bundle. Overall, we are satisfied with the solution's pricing. The solution has helped us save around 25% of our operational costs.

On a scale from one to ten, where one is bad and ten is good, I rate the solution's pricing ten out of ten.

We use the solution for development purposes. When it comes to security, we depend on two levels of security. The first level is what Microsoft .NET Framework gives and the patches that Microsoft provides. The second is our internal security algorithms and logics.

Licensing plays a big role when you have other systems. When using Microsoft .NET Framework, you start writing the code internally. This reduces the cost on the licensing side, which helps reduce the overall expenditure of OpEx and CapEx.

I would recommend Microsoft .NET Framework if you start developing your tools and products in Microsoft. This is one of the platforms that Microsoft provides. If you are into .NET and want to develop a lot of applications, you need the Microsoft .NET Framework platform. We perform the solution’s maintenance in-house.

Overall, I rate the solution ten out of ten.

I'm a developer with .NET Framework. Apart from powering the Xamarin platform, I also use .NET for API development for .NET Core, which I deploy on clouds like Azure or AWS. We use .NET Core for every solution, from built-in web apps to REST APIs. I can use .NET Framework to build desktop-based applications using a company called WPF. We use .NET for Unity, a popular gaming engine. It uses .NET as well as C#. In our organization, we just use .NET for Xamarin.

Given that it's cross-platform right now, where you can use it on Windows and Mac, that is the single most significant feature that has resulted in wider adoption of .NET. Earlier, you could only build solutions for Windows and Windows server ecosystems, but now you can build a .NET Core app and deploy it on Linux VMs, and so on.

One thing that could be improved is the tooling and IDE for .NET in non-Windows environments like Mac. This is a common gripe across the developer community. Visual Studio for Mac is nowhere near as feature-rich and productive as Visual Studio for Windows. Visual Studio for Mac is a shadow of what Visual Studio for Windows offers. For developers who switch from Windows to Mac and those who are using Visual Studio or both, they find that the Visual Studio provided by Microsoft for Mac is very primitive compared to what's offered for Windows.

I've worked with .NET Framework since 2002 on and off.

I rate .NET Framework’s stability a nine out of ten.

I rate the initial setup a nine out of ten. The initial setup is very easy. When you install Visual Studio, it will install the latest .NET runtime for you. You don't have to do anything extra to get .NET installed.

If you build cloud solutions, your .NET Framework will be installed as part of your solution. Suppose you are deploying something on the cloud, microservices, for example. In that case, you'll most likely deploy Microsoft services as part of the container, and the container will ensure that all the prerequisite underlying software, like .NET Framework, is installed. In my organization, we already use .NET Framework for mobile development on Xamarin, and that requires us to install the .NET Framework on the system we're developing on. .NET Framework gets automatically installed when you install the Visual Studio IDE that comes bundled with all the dependencies like the .NET Framework.

How fast .NET Framework deploys depends on your Internet connectivity, but it can take less than two minutes. The solution does not require maintenance. One person is enough for deployment.

I rate the solution's pricing a two out of ten because .NET is an open-source framework. You don't have to pay for a license. .NET alone wouldn't do the job for you. .NET is the underlying framework, so you must install IDEs or something to build apps on top of .NET. Visual Studio, for example. Only the Visual Studio Community edition is free. The other variants of Visual Studio will cost you money, and they have increased their prices. Everything is free if you use the Community edition, but if you have to deploy the solution to the cloud, like Azure or AWS, they will charge you money. Likewise, if you are building something on Unity for game development, you can always distribute your games through the Apple, Windows, or Google Play stores, and they will charge you.

In my organization, .NET Framework is only used for mobile development in Xamarin. It's not used for server-side or cloud development because we use Java and Node.js. Once we move from Xamarin to another technology, our organization will probably not use .NET.

Suppose you want to work within the Microsoft ecosystem, which many organizations do because many organizations have had a partnership with Microsoft for a long period. In that case, .NET is the de facto development framework organizations use. .NET is very mature, well supported, and adopted by major Fortune 100 or Fortune 200 companies. Big companies use .NET, but maybe not for their entire spectrum of services and solutions. But most big companies use Microsoft .NET for some other part of their solution. It's been there for the last 20 years, and Microsoft releases new versions yearly. The current one is cross-platform, very robust, and stable. I rate .NET Framework a nine out of ten on all these criteria.

A team of developers in our organization are using the solution. Microsoft .NET Framework is used in our company for web and mobile application development. 

The solution has assisted our organization in the full-stack development process. The tool can be deployed on all types of devices, including mobiles and desktops. The MAUI capabilities of the solution have been the most beneficial feature for our organization's development needs.

At our company, we never had the option to develop for external users. By using specific frameworks from the solution or MAUI, our company has been able to develop mobile apps that can be deployed externally with utmost security. 

The product exhibits impressive compatibility. In our company, the solution is being integrated seamlessly with iSeries, K2 Environment and all vital databases where the data is stored in Db2 and SQL. 

Like in C#, Microsoft .NET Framework should provide code reusability options for all kinds of development processes. 

I have been working with Microsoft .NET Framework for two years. 

I would rate the stability a nine out of ten. For two years, we have been using Microsoft .NET Framework in our company, and we have never witnessed the product to be unstable. 

I would rate the scalability a nine out of ten. The scaling process may take time, but there are endless possibilities. Our organization has about 50 users of Microsoft .NET Framework. The solution is used daily in our company, and there are plans to increase the frequency and number of users. 

At our company, we are utilizing resources like GitHub and search engines to resolve our queries and issues. 

Our company was using Magic and K2 beforehand, which has a few similarities to Microsoft .NET Framework. Due to a lack of resources and developers in Magic, our organization shifted to Microsoft .NET Framework. 

I would rate the initial setup process a nine out of ten. The deployment process of Microsoft .NET Framework was found straightforward by our company. It took just a couple of hours in our organization to complete the installation process of Microsoft .NET Framework, the process got accelerated as we already had Visual Studio deployed in our environment.

Only one professional was required in our organization to deploy Microsoft .NET Framework. There is a team of seven developers in our company who use the platform. The maintenance of the product is implemented once a month in our company, but mostly its for upgrades from .NET. 

Our company has realized an ROI from the solution. Our company received high-budget quotes from clients to outsource mobile development; an ROI is found when comparing in-house development and buying off-the-shelf or development outsourcing. There has been an approximate ROI of 40%, but it's based on the money saved due to purchasing the tool. There are software and employee costs for a company that is unaccounted for in the ROI. 

I would rate the pricing an eight out of ten. It's an expensive solution. The high operational cost is often due to integration requirements with Visual Studio. There are no additional costs to the initial contract with Microsoft .NET Framework. When new developers or users are added to a project, you need to purchase Visual Studio Lab. 

Our organization is presently evaluating low-code and RPA solutions. 

The Microsoft .NET Framework enhances the development capabilities for mobile and web applications. The solution helps in developing computer applications in multiple languages and for local platforms. 

Microsoft .NET Framework is known for security features, so we haven't had any security incidents or breaches in our organization. There are four or five applications in our company that have been developed in the Microsoft .NET Framework. 

The performance of applications built with Microsoft .NET Framework depends on the server. All the applications we have built in our company using the solution don't have any response issues. I would advise others that the solution is worth it if there are full-stack developers in the company.

A lot of possibilities get unlocked in C# and JavaScript when using Microsoft .NET Framework. I would rate Microsoft .NET Framework as a nine out of ten. I would definitely recommend the product to others due to its flexible capabilities.