Microsoft .NET Framework Reviews

I am building a web application and using this solution.

The platform was chosen to be used and I did not choose it, so I can't speak to what is the best feature.

There may be some topics regarding connectivity and management of certificates that require attention. We are currently facing some issues.

I have been using the solution for about two years.

As we are scaling quite nicely on Azure.

I have not contacted customer service recently.

The initial setup is complex. Once you know and have some help, it is manageable.

The company is not paying anything for the license. I am not familiar with this area. For us, it's free.

Java and Sprint are alternatives we considered.

Our solution should work for roughly 50,000 users every day. We are still collaborating, and it's okay. 

The overall product rating is eight out of ten.

You are able to develop applications using Microsoft .NET Framework. It is a development framework.

Using Microsoft.NET Framework we developed many Line of Business Applications, which empowers digital transformation and optimized business processes.

Framework provide almost all the technology stacks requires for custom development, only issue is if not used properly, it will create undesirable results.

MVC framework could be better if provide little bit more restrictive framework. Instead of allowing developers to adapt anything they want.

I have been using Microsoft .NET Framework for approximately 15 years.

The solution is stable because Mircosoft releases updates frequently.

The solution is scalable.

We have approximately 13 users using this solution.

When we have contacted Microsoft Support they ask too many questions and requiring too many details. They sometimes do not assign the right person that has the knowledge to deal with the support ticket.

The installation is straightforward. The time for the deployment depends on the environment, but it typically takes approximately 45 minutes.

I did the implementation myself. However, I would recommend using a team of experts for the deployment and maintenance of the solution.

The solution is free but you need to pay for a license for the hosting service.

Java server pages, j2ee. 

I would recommend this solution to others. However, they need to understand the capability of the Framework, and they should align their solution according to the Framework to prevent any showstopper or bottlenecks in their development process.

I rate Microsoft .NET Framework a nine out of ten.

I use the solution in my company to build internal systems that are used for developing applications to run our business, and we also use it to call web services.

The most valuable component of the product stems from the fact that it works properly. I know it might sound funny, but you don't have to go and get other third-party solutions when using Microsoft .NET Framework. With Microsoft .NET Framework, you also don't have to do a whole lot of extra configurations to make it run. The tool offers a lot of support, and there is a lot of knowledge material available, along with a lot of community groups. If you have an issue with the tool, you can find someone to help you pretty easily.

I think the main thing that my company wants is Microsoft .NET Framework to provide us with more integrations with Azure, like in the area of DevOps in Azure, which can improve its management and work in the cloud. The tool is good, but it can be made a bit better.

The product's price is an area of concern, making it an area where improvements are required. The product should be available at a low cost.

I have been using Microsoft .NET Framework for about fifteen years. The older version of the tool is automatically updated.

I have not faced any issues with the stability of the product.

Considering what cloud services can support, the scalability offered by the product is unlimited. I feel that it is a scalable solution.

My company has around 12 to 15 developers who use the product.

In terms of the size of Microsoft .NET Frameworks' environment, I feel that as a cloud-based product, it serves as a system to the customers, so it can serve the needs of hundreds of customers, meaning there are no real size limitations. The on-premises version of the tool that our company has been running had 350 people running through the applications on-site, and it was running every day with thousands of daily transactions.

I believe that the developers in my company have raised issues with the product's support team. I believe that it was never a challenge for my company to find the right person who provides the right solutions. My company has dealt with difficulties in a few technical areas attached to the solution, especially in the area of integration, but I don't remember any major issues with the solution.

Microsoft support is okay. If you are aware of the community practice when it comes to the tool, you can pay for Microsoft .NET Framework's extended support, as it can be helpful. The support is really good. I rate the technical support a seven out of ten.

Neutral

As long as somebody in your company understands how the tool works, handling its setup phase is not complex. If you are learning to use the tool for the first time, the setup phase can be difficult. You need a good understanding to start with if you want to do the setup phase easily.

During the product's deployment phase, our company just needs to push the product through the pipeline, which is a very easy process. Putting the code out there is pretty easy since Microsoft processes work quite well in a simple manner.

My company has not looked at the tool from an ROI perspective since it is a product we need to use. Along with the stack of Microsoft products, Microsoft .NET Framework is a tool that works for our company.

In our company's development projects, the code is built using Microsoft .NET Framework, which is valuable and beneficial.

In our company, we have a system internally that runs several contracts that we do, and it provides a workflow application that people in our organization basically manage to make sure that the workflow for the contracts we hire is completed, so it has a lot of business rules in it, meaning it has a very strong business rules engine. The other main process our company uses is in building the cloud solution that is focused on how you deliver durability to end-customers because it is a tool that can be used in a very extensible manner, leading us to use it a lot.

The interoperability of Microsoft .NET Framework with other languages and platforms affects our company's projects since it allows us to build whatever we want. There are no limitations in the tool, and as long as someone in our company has an API we can work with, we can build a connector tool, so it is quite open to what it can achieve. In general, with some of the low code areas, you may start to run into challenges while doing some integrations and maintaining them, but with Microsoft .NET Framework, it is very simple since once something is built, it works fine, especially when doing updates and changes, it is an easy process which is not a difficult thing to manage at all.

The product's security features are fine, but I feel you need to follow a security-by-design approach for all software environments. Microsoft .NET Framework usually enables what you do, but it does not make it happen for you since it only serves as a toolkit.

The performance and the scalability of the applications developed in Microsoft .NET Framework are fine but my has got certain things on Microsoft .NET Core is on Microsoft Azure. It can take as many customers or as many users as Azure can handle, making it a very extensible tool.

The product is not difficult to maintain.

The integration of security and network of the tool has benefited our organization since we can easily integrate SIEM, SOAR, or NMS tools.

I recommend the product to others who plan to use it. I believe that you need to invest in getting to know how to use and run the tool.

 I rate the tool a nine out of ten.

I work in the supply chain and transportation space. NET Framework is the core part of the technology stack. We had to build everything, including the Windows system.

We could spend more time building the application than building the framework. We've been using it since V1, and .NET has grown and changed multiple times in different directions. It brings more to the table each time, so we need to build less and less. If you think about containerization, you get that from the .NET framework.

Microsoft .NET Framework reduces the cost of entry and enables the development of applications with mature and enterprise features, thereby lowering the entry barriers.

The learning curve could be improved.

I have been using Microsoft .NET Framework since its inception.

The product is stable.

The solution’s scalability is good. We use the .NET Framework as a stack component in our project to develop software. Everyone from cybersecurity personnel and architects to customer service support uses this application.

There is a community providing solutions. Many others encounter the same issue with .NET and search for solutions online through Google.

Positive

The initial setup is very easy. We can usually get something spun up and running in a day.

The product is free.

Microsoft .NET Framework is a framework for development. We use cryptography, messaging, and many other components the platform provides for our development work. We are prototyping with the latest framework, which includes a mixed model of HTML rendering. This model is a blend of client-oriented applications, where most tasks are performed in the browser, and server-side applications, where the server renders the HTML for the web pages. The latest offering simplifies administration and development for simple pages while enabling the creation of highly interactive pages resembling control screens and back-office control centers.

We've used ASP.NET to create web UI. You might have business rules and logic running on your server. You have databases and frameworks for interacting.

We use C# and VB.NET on the backend and SQL for the database. The platform is good at implementing standards for web services. With .NET, there are competing standards, depending on whether it's coming from Microsoft or Oracle. The platform is very good, providing standards-based programming models.

The ease of finding and using third-party libraries with the .NET Framework is extensive. We use some libraries, but many more are available.

A single person is enough for the solution's maintenance.

The .NET Framework requires maintenance like any other deployed software, with patches and updates being essential to maintain. It's important to stay updated and evaluate these patches as they often address security threats. One of the major security risks in the .NET environment arises from using outdated software with known exploits. For instance, a vulnerability discovered in a particular version becomes a security risk until patched. In such cases, a patch is released, and while most companies apply it promptly, some may lag, leaving them vulnerable to attacks. These unpatched systems become easy targets for attackers, exploiting well-known vulnerabilities. Therefore, the patching process is crucial for maintaining security.

Overall, I rate the solution an eight 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.

The solution has difficulty integrating with other products. There are no such difficulties if you have the same platform, hardware, and operating system.

We have almost 15 developers using the solution. It has reliability.

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.

The initial setup is complex and takes time.

When the development team deploys a new application, they prepare a new server. It is a very complicated task. It has dependencies.

More than one person is required to maintain the solution.

Microsoft .NET Framework is a mature application. More than 50% of applications are on .NET Framework.

Overall, I rate the solution a ten out of ten.

We use Microsoft .NET Framework for testing and development for RPE.

The most valuable thing about Microsoft .NET Framework is that it is an enterprise-grade language and platform.

Microsoft .NET Framework has a steep learning curve, which could be improved.

I have been using Microsoft .NET Framework for five years.

Microsoft .NET Framework is a stable solution.

I rate Microsoft .NET Framework a nine out of ten for stability.

Microsoft .NET Framework is a scalable solution. In my previous job, around 20 to 50 users used Microsoft .NET Framework.

I rate Microsoft .NET Framework a nine out of ten for scalability.

The solution’s initial setup is easy.

The solution takes only a few minutes or hours to deploy.

Just one person is required for the solution's deployment.

Microsoft .NET Framework is a free, open source solution.

We don't maintain the solution because it's a framework that does not need to be maintained.

I recommend users use the solution's online documentation because it's open and free.

Overall, I rate Microsoft .NET Framework a nine out of ten.

For testing purposes, we deploy it on our own server (on the Infrastructure server). For our production, we're deploying it on AWCC too.

Nowadays, Microsoft is trying to fix a few things and build a framework faster than other frameworks. There are a few reasons to choose .NET. However, my supervisor selected this framework for a few scenarios, and our scenario is also quite a good match with the .NET Framework. 

We are using, the .NET Core Framework right now. It's the Core platform. They are releasing a new version, and the new version is becoming faster and easier to use compared to other frameworks and other languages. 

The initial setup is easy.

They offer good CLI support.

It's easy to create and integrate things.

They're improving many features day by day. Maybe other kinds of support would be helpful. Making it even faster would be welcome. Their ORM is a little bit slow compared to other ORM. That said, comparing to the current version and previous versions, their ORM is now much faster.

They should try to improve their Blazor WebAssembly.

Previously, we used to face difficulties in designing a pattern or this kind of feature. However, right now, they're improving this so it's easier to write than it was before.

I've been using the solution for three years. 

The solution has been very stable and reliable. We haven't had issues with bugs or crashes. 

In my company, we have more than 100 employees, and more than 50 are using .NET Framework.

Compared to the previous version, the current version is more scalable in .NET Framework.

I've never used technical support. 

I'm also familiar with Java. 

The product was easy to set up. It was not an overly complex process. I'd give it an eight or nine out of ten for ease of deployment. Their CLI support is very good. 

The deployment itself is fast and takes about 20 minutes or so. I'm using a Windows server. It might vary based on dependencies. In our case, it was very straightforward since we had everything set up and ready to go. Only one technician was needed to set up the server. 

We do not have to pay to use the .NET Framework or other kinds of frameworks. 

We are end-users. 

I'm not sure why the company decided to use the solution. However, they have used it for a while. 

Choosing a framework totally depends on the scenario and project. If you want to build an interface, then the .NET Framework will be good. That said, a Java framework also will be good. I'd recommend either of those frameworks in general. 

I'd rate the solution eight out of ten. they are always trying to improve, unlike other frameworks or languages. There are also good features and a good community around it.