Microsoft .NET Framework Reviews

Our company is a partner with Microsoft and we install the solution for our customers. 

I like that ASP.NET is used for the framework and the core web services. 

There are performance constraints when multiple users are accessing the application and that consumes CPU resources. 

The ASP.NET framework is no longer supported because the new .NET framework has taken over so any core changes require us to redo projects. 

The setup process for on-premises is complex. 

I have been using the solution for ten years. 

The on-premises solution is quite stable. 

The on-premises solution is hard to scale.

The cloud-based solution is easy to scale because you have access to multiple servers and distributed services. 

Technical support is challenging because staff work on shifts in different regions and do not have knowledge about support tickets or what has already been investigated. 

There are costly fees for support based on the level of support ticket such as normal, high priority, and urgent priority. Once you pay for support, you are sometimes routed to another technician and need to explain the issue again which is not efficient. It would be more efficient and cost effective to remain with the same technician throughout the support experience. 

There are complexities and constraints to setup in on-premises environments. The initial setup requires a Windows server and an IIS server so you might experience compatibility issues. The development version and the machine version need to match or you will be required to install libraries and additional framework. You will also need to check routing to ensure it is correct.

The cloud-based setup is easier and less time consuming because all features and libraries are readily available. 

Our company includes 40 skilled engineers who implement the solution for our customers. 

The solution is a bit costly when compared to open source products or open gear licenses. 

I rate the cost a six out of ten. 

We are using this solution for Forms. 

Website for basic monitoring of the tools, and we have developed intelligent automation which is like a service and is running in the backend to monitor bots.

We are using basic coding to do the automation monitoring stops.

If we take low code, no code platform such as RPA platforms, you might end up writing 100 lines of code and you might do it in a single line of code using. NET.

It comes with many features that you can interact with and has all of the libraries readily available, which is not available in the RPA platforms.

You can create your own SSIS package. You can integrate with all of the Windows objects, which is not available in Automation Anywhere, and you need to rely on their Object Cloning technologies to interact with them.

You need to have the technical expertise to use this product.

We have not had any issues with bugs or glitches.

It's an in-house development, we don't have more than 12 users.

We have contacted technical support but not for. NET. We contacted them for Power Automate.

We have only just started interacting with them, so I am not able to evaluate them.

If you want to build automation without much technical expertise then I would say not to go with, . NET. With. NET, you need the technical expertise.

If you are looking for something that is readily used to be available for automation, then I would say to go with RPA tools. Also, if you want to go ahead with low code, no code platforms Power Automate gives you RPA capabilities without the user knowing the technical aspect of it.

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

We primarily use the solution as a self-check-in tool for customers for a number of hotels.

The ability to incorporate the customers is the solution's most valuable aspect.

The pricing and support have room for improvement. The pricing is too high currently. We are thinking about the pricing from the end customer's perspective.

I've been using the solution for around three years.

I'd rate the solution as highly stable.

The solution offers good scalability capabilities. There are tens of thousands of end-users on the solution currently.

I've never been directly in touch with Microsoft's technical support team. My team has been, however, and I'd say, according to them, they are quite responsive.

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.

The initial setup is not straightforward. It's complex. Typically, deployment takes one year.

I handled the implementation myself with the assistance of my team.

The pricing is a bit expensive.

We did evaluate other options. We looked at both Java and PHP.

We are official partners and we are sellers for UiPath. For Microsoft, however, we're just customers.

I'm not sure which version of the solution we're currently using.

I'd advise others to find a solution that is suitable to the customer's needs and to examine the customer's business case before deploying anything. In our case, this solution was something that is a bit more expensive. However, it's of the highest caliber and it's stable. In this scenario, it made sense for us to choose Microsoft.

I'd recommend the solution to others serving a similar type of customer.

I'd rate the solution eight 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.