Microsoft .NET Framework Reviews

We primarily use this solution for point-of-sale and finances. We also use it for maintaining student information, details about teachers, attendance, and grades.

The most valuable feature is the financial accounting.

This solution should include Power BI so that we don't have to use any third-party tools. Including business intelligence tools would allow for easy understanding and quick decision making. It will help as it is for summarizing all of the business-specific analytics.

We have been using the Microsoft .NET Framework for six years.

The Microsoft .NET Framework is 100% stable. We have to use it for our day-to-day activities. Also, based on the business functionality you have to keep upgrading.

This platform is easy to scale. We have approximately 100 users, five of which are administrators and the remainder are business users.

We have been in touch with Microsoft technical support and we are happy with their work.

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.

The initial setup is easy.

We used consultants for the deployment and we use third-party business intelligence tools for the integration.

We did have the option to go with PHP and Joomla, but we were concerned that it may not be available after a few years. When it comes to Microsoft technology, it is more stable and because they are a giant in technology, .NET will be an everlasting solution for which we can always find developers and support.

This is a product that I recommend.

I would rate this solution a ten out of ten.

I developed an application tailored for the oil and gas sector, focusing on risk assessment and activity mapping for wells across Brazil. This tool utilized the .NET Framework, specifically version 4.6, to ensure robust performance and seamless integration with existing systems used by oil and gas companies in the region.

The .NET Framework streamlined the integration of our enterprise-level applications by leveraging .NET service-oriented architecture. This approach simplified development as we could modularize our system into microservices, enabling us to assist each component seamlessly within the .NET environment, tailored to the specific scenario at hand.

The .NET Framework's interoperability with other applications and its language independence has proven invaluable for our development projects. In my latest project, I developed a portal application capable of simulating various applications tailored to different user roles within the company. Using the .NET framework, I created a secure domain model to manage user authentication and bill distribution across these applications. I particularly appreciated the .NET Bot framework for its ability to quickly translate existing class models into code, facilitating rapid development and seamless integration with our database.

The support for multiple programming languages in .NET has influenced our choice of languages for various tasks. As a team, we possess a solid understanding of .NET, making it easy to leverage its capabilities. While clients may not always have insight into the technical aspects of our work, the versatility of .NET enhances our productivity. This allows us to deliver results to clients more efficiently and encourages their active participation in the development process.

The security model of the .NET Framework significantly contributes to the overall security of our .NET applications. This is largely facilitated by our proficient IT team, who meticulously plan and manage the infrastructure. As our .NET applications are primarily utilized within our company's intranet, security measures are inherently more manageable.

The features that significantly enhanced our application's performance primarily revolved around integrations. For instance, in one scenario, our application was tasked with scanning field activities within the .NET framework, encompassing both onshore and offshore operations. It facilitated the streamlined scheduling process by amalgamating inputs from various sources, including location data and other systems. Users could input data and conduct simulations within the application to assess the viability of certain activities. Additionally, the application was backed by a database running SQL scripts to support its functionalities.

Improvements are needed in .NET development, particularly in a backend scenario. For example, if you're planning to develop an application to track project operations using .NET, a good starting point would be to adopt domain-driven design principles. This approach allows you to visualize all the relevant components within the .NET framework for such a project. You can begin by defining the core domain entities, such as projects, tasks, and locations, leveraging .NET classes to represent these concepts effectively. Additionally, incorporating a scheduler component in .NET to manage activities associated with each project would be beneficial. By organizing these classes systematically, you can streamline the process of generating database tables directly from your code.

I have been working with it for almost a decade.

The stability is outstanding. I encountered no issues, with any concerns primarily related to infrastructure servers rather than the .NET framework itself. I would rate it nine out of ten.

The scalability is exceptional. I would rate it nine out of ten.

We didn't require support assistance as Microsoft offers ample resources, including instructional videos, for implementing and resolving any issues independently. I would rate it nine out of ten.

Positive

The initial setup is straightforward. However, as operations start, a structured approach is essential. This involves establishing distinct layers of code, each with specific responsibilities aligned with the product's objectives. For example, if managing a product class, its functions should exclusively pertain to product-related tasks. Similarly, when dealing with a layer handling thousands of transactions, caution must be exercised to ensure it remains focused on its designated operations without encroaching upon other aspects of the project. This segregation of tasks ensures clarity and efficiency within the development process, despite its inherent complexity.

In our web and desktop application development workflow, we typically support IT personnel by providing them with the necessary components to set up a server for deploying our applications. We hold weekly meetings to discuss our approach and progress, and throughout the week, we collaborate on various tasks. Once the work is completed, we publish the applications to the server, ensuring that all required roles are fulfilled for successful deployment.

For deployment, we didn't have to do much as it was already completed for us. Additionally, we utilized GitLab and Jira in conjunction with Docker for streamlined deployment processes.

Overall, I would rate it nine out of ten.

We use Microsoft .NET Framework to develop various products, including an ERP system.

The technology is very scalable and accessible to use.

The product could have a better framework for application development. We have used Xamarin technology by Microsoft. It needs to be up-to-date compared to other technologies.

The platform is very stable. I rate its stability a nine out of ten.

We have 20 Microsoft .NET Framework users in our organization. We use it every day. I rate its scalability an eight out of ten.

The technical support services are good.

Positive

I rate Microsoft .NET Framework an eight out of ten.

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. 

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.

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.

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.

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.