Microsoft .NET Framework Reviews

As hardware evolved as mainframe, mid-range, mini, micro, personal computers (PC), while miniaturizing the silicon chips and other computer parts, computer software evolved as operating systems, systems software, computer applications, files (to persistent data), databases, etc. After mainframe applications, there was an age of client server software with PowerBuilder-Sybase-Oracle-Visual Basic.

Later came the web applications, where a client computer communicates a request to a server computer and the server computer sends a response to the client computer, in the form of static HTML. The browser, like Netscape or Internet Explorer, captures this response and serves it as web page on the client computer. Though the web request-response is here, still the "forms-with-fields-and-buttons" or "PDF-or-word-report"....

With the advent of client-server and web technology, applications went from monolithic spaghetti-code software to 3-layer and later, n-tier applications. Computer application code became structured and modular, functional, distributed (COM, D-COM and remoting), object-oriented to these days service-oriented web service-based applications.

All these days, Microsoft was walking hand-in-hand with other technology vendors, leading in some innovation and following in some. Microsoft was a large part of this entire IT revolution. Microsoft technology coding practices evolved from MS-DOS, Q-BASIC, MS Windows, client-server oriented Visual Basic, Visual C++ and application-friendlier COM components, and ActiveX. With the web era, Microsoft introduced server-side script (VB Script) and client-side (browser) (JavaScript)-based ASP (Active Server Pages). Until this point, the concept of .NET and the .NET framework was not in the picture. HTML pages were static and an attempt was made to introduce dynamic content (for server-side and client-side validations, custom processing, database handling, third-party component handling) with ASP (Active Server Pages)-based systems.

Microsoft thought of a better way with the introduction of .NET-based languages and the .NET framework. Here, Microsoft tried to generalize between the commonality between their various software products like coding languages (VB, .NET, C#, etc.),MS Windows, Microsoft Office, MS SQL Server databases and other products. These common components were introduced as the .NET Framework. The framework had a common language run-time, memory management (Garbage Collector), error handling (EXCEPTIONS), database handling block using ADO.NET and so on....

With Microsoft .NET, the dynamic web content handling became easier and the Microsoft world of web became more programmable with use of reusable and redistributable web components and systems (building blocks). The .NET framework was the core part of all Microsoft products. Data became more accessible. Forms and user interfaces became more friendlier. There is Microsoft Practices and Patterns guidance to the computer world, in designing, development, implementing, unit testing, archiving, etc.; the entire Software Development Life Cycle of the IT universe.

With Microsoft technology ,IT was as simple as the game of building blocks.

Due diligence is always given in IT technology by all IT vendors and their technicians. It is a complete rotating earth in its universe. What improvements you can suggest for the Great Wall of China or the TajMahal? The IT universe is agile.

Computer systems became a network of computers (intranet-internet) and now are social request-response driven. Web systems were request-response and now web services, WCF, Web API and SOA are making it more data driven, like fifth-generation computer systems. Soon, these computer systems will adapt to artificial intelligence technology and natural language interface; machine learning, big data will be common place. The future could be more nature driven.

I have been using the Microsoft .NET Framework to develop and implement application software for around 15 years.

I have not encountered any deployment issues.

I have not encountered any stability issues.

I have not encountered any scalability issues.

Customer service is excellent.

Technical support is excellent.

The ROI is excellent.

Microsoft technology is becoming freeware and cross-platform, embracing all changes and suggestions from the rest of the IT world.

I use the product to build websites and web pages. The product is also useful to connect to Sitecore.

The most valuable feature of the solution stems from the packages offered by the product.

There are constant improvements in the product.

I would want the product to be integrated with the different AI tools in the future since it is one of the areas where the product has certain shortcomings.

I have been using Microsoft .NET Framework for a year. I am a user of the tool.

It is a stable solution.

More than 100 people in my company use the product.

The product's initial setup phase wasn't difficult at all.

The solution is deployed on an on-premises model.

The product is not expensive.

Only if I know the purpose for which someone requires the product will I be able to recommend it to them.

I can say that users can trust and use Microsoft .NET Framework.

Microsoft .NET Framework's CLR has benefited my company's projects.

I am happy with the product's user interface, scalability, integration features, and support.

It is easy for someone to learn about how to use the product.

I rate the overall product an eight out of ten.

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.

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. 

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. 

Our development tools, our platform, every solution we've developed, most of them are Microsoft products. So we're using .NET. 

Almost all of our enterprise applications are developed within that whether it will be reading those applications, web applications, or a background service, etc. Of course, there's a different case when it comes to our mobile application. We're quite open-minded and like to explore other frameworks due to the fact that there has been a lot of frameworks getting more popular nowadays.

I have very diverse experiences in most of the major programming frameworks, whether it is DHP, Java, etc.

Basically, .NET is simply is the easiest programming language to use, based on my experience. It has flaws, however, the performance and agility are much better compared to other programming languages.

They've done a lot in the past few years. You can see this especially in the fact that they allowed .NET to be run in Linux environments.

For .NET, what I can say is that maybe it needs adaptation of a more streamlined function. What we can see is vital is a simple programming model. However, .NET Is still heavy or dependant on other Microsoft libraries and frameworks. Therefore, although they're going there, they're already open-source for that network. There are lots of improvements that can be done there within that industry.

For example, .NET support needs to offer big data similar to Mongo DB or to the other big data technologies. It's still in its infancy from I've experienced. When it comes to the big data or data science fields, I think .NET framework has a lot of things to hash out.

Another item worth improving in .NET is support to Mac. There's still a lot of grey areas when you use a Mac. There's a lot of instability when it comes to that OS. .NET programming language will be very difficult to compete with when they fully jump into the Apple territory.

I've been dealing with the solution for probably more than ten years. I've been using .NET since the beginning when it was .NET 1.0. Therefore, I believe it's been more than a decade.

The solution is stable. Aside from issues surrounding using Macs, it's not too glitchy. It doesn't freeze. It's pretty reliable.

The biggest problem with programming language nowadays, because there are a lot of things happening, is that changes happen too fast. Due to the competition, they tend to release new features almost every week. I don't think there's an exception on that one. In return, the application framework can have bugs in it. 

Nowadays when it comes to scalability performance, it's in the hand of the programmers. It's not in the framework. Even if you're using a very efficient or powerful framework, if that application was developed improperly, it just makes everything else shakey. If the framework is there to help you to do the best practices and apply everything, .NET is still really good at doing that, compared to other frameworks. Almost everything is bootstrapped or is ready for you to use, unlike other frameworks like Java. You have to develop everything to make sure that it is able to address the issues. In .NET it's pretty straightforward.

If we contacted technical support it may have been a long time ago. Nowadays, it's rare to go directly to support. For the most part, all you need to do is Google your queries and you can find the answers yourself.

The tool itself, in terms of the initial implementation, is pretty straightforward. The tool will do everything for you, unlike other programming languages where you have to install these different dependencies, et cetera. 

We're just a customer.

We use multiple deployment models. I'm using Azure Dev Ops for my previous projects, but for my company, we're using Jenkins to deploy our applications.

The good thing with the .NET framework is that it allows you to develop an application faster and in a professional way. The downside is that it's different due to the fact that it's abstract. It's different from every other program. You really need to know the fundamentals of software development. That's the downside. Using .NET You will be able to develop many applications without really knowing what the inner workings of that application are. Compared to Java, or C++ where you should be able to know every fundamental of every foundation, you don't need that deep knowledge with .NET. If there will be a trainee or entry-level person on the program, I suggest they study first computer programming fundamentals, maybe in Java or another more engineering-oriented programming language before they go deeper into the .NET framework. Or they should at least do their homework to learn those things.

Overall, I'd rate the solution eight out of ten. If they slowed down a bit with the new releases and made sure they were bug-free before releasing them, I might rate it higher.

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.