Microsoft .NET Framework Reviews

I am currently working on the development of a new product using Microsoft .NET Framework. The project is currently in the analysis, architecture, and user acceptance phases. It is a comprehensive system similar to ERP, designed to manage internal resources for a sizable bank. The application focuses on handling IT resources for the bank, and it is being developed in-house.

Within each specific .NET product of ours, we currently have a robust portfolio with around a dozen products actively running for our customers. Based on the user databases, it's evident that each product is implemented using .NET. In fact, one of our products boasts slightly over one thousand users. This underscores the prevalent use of .NET across our product range.

Firstly, I appreciate the decision to use Microsoft .NET Framework. I find it to be an excellent language, with a history rooted in providing an alternative to Java, albeit with initial challenges. It is gaining popularity and may be voted the most desirable programming language. What I particularly like about .NET is its language efficiency. While C# is the primary language, the platform also supports others, catering to those inclined towards functional programming. Although I started with Shell, I'm still grasping the concept of functional programming. Despite initial reservations about object-oriented programming, I acknowledge its advantages. .NET is a safer option, and despite criticisms, it has evolved over the years.

One notable aspect is .NET's transition to an open platform in recent years, distancing itself from being exclusive to Microsoft engineers. I appreciate the versatility of .NET, enabling code production for a wide range of platforms, presenting a strong competition to Java. It allows targeting practically any physical platform, showcasing its flexibility. These qualities contribute to my positive view of .NET, totaling thirteen aspects that I find appealing.

In the realm of Microsoft .NET Framework, particularly in the C# language, there have been significant developments that I find highly commendable. I am genuinely fascinated by the continuous evolution of the language, and staying abreast of the latest features in Azure is both challenging and enjoyable. Working with C# in Azure is particularly fantastic.

I appreciate in .NET, as compared to Java, is the enforcement of types, providing a better experience in terms of technicalities. Additionally, the introduction of Roslyn in the past few years has brought about the concept of late .NET, which I find interesting and powerful. This allows for the transformation of symbolic code just before execution, eliminating the runtime decision-making process and enhancing efficiency. However, late .NET does come with a drawback – a delay in the last-minute computation when starting an executable. While some may find this less appealing in terms of instant responsiveness, especially in serverless cloud environments, the efficiency gained from executing strictly binary code is valuable.

Despite potential drawbacks like the time required for activation, I view .NET favorably for its technical advancements and efficiency, especially in scenarios such as serverless cloud computing. It's essential to recognize the intricacies of how .NET processes code and the efficiency it brings, which some may overlook.

I have been using Microsoft .NET Framework for many years, since 1992 or 1993. 

It is stable.

I'm frequently questioned about the scalability of .NET products by the company owner. In response, I inquire about the specific aspect of scalability they are interested in. If the concern is about handling sudden surges in traffic, I affirm that .NET is indeed scalable, especially with the implementation of group health checks. This ensures automatic scaling without manual intervention, providing convenience.

Contrary to common misconceptions, I emphasize that the performance of .NET is typically not hindered by processing power but by factors such as disk I/O and database operations. Scaling the database differs significantly from scaling processing power, as it involves handling transactions, open transactions, and conflicting operations. If isolation is not well-implemented, issues may arise. For instance, a database like SQL Server, while appearing appealing a decade ago for its tools and affordability, presented challenges in terms of scaling compared to Oracle. Understanding these nuances is crucial for making informed decisions about scalability.

Regarding customer support from Microsoft, I can say that when we documented issues and submitted tickets, Microsoft was responsive and open, even without direct contact. Working with Microsoft has generally been positive, and their strategic direction is something we have followed closely. Microsoft's commitment to evolving their product has been beneficial for us, even though the unpredictability of their decisions can sometimes pose challenges. In a small company like ours, adapting to changes becomes more complex, especially considering the project size.

As a company, we are also involved in software development for the European Commission, where the strong requirement is to use software from the .NET world. The challenge arises when dealing with Java in parallel, as its community processes add an element of unpredictability. Managing a team that can swiftly adapt to changing technologies is an advantage, but it requires time and effort. The unpredictability of Java's direction contrasts with the more foreseeable evolution of .NET.

We have had experiences with Oracle as well as .NET, specifically with the Silverlight framework, though that was some years ago. Silverlight, while not inherently bad, tends to be criticized, and I often advise people to understand its origin as the Presentation Foundation Everywhere (PFE), indicating its intention to provide a unified UI across various platforms. However, due to various challenges, it was eventually phased out, and Silverlight became obsolete. We once had a product active on SolarWinds 3.5, transitioned to SolarWinds Sorin, but unfortunately did not survive beyond Silverlight 5.

Yes, it is easy. .NET has expanded its scope significantly. It's worth noting that while many may mention .NET, not everyone truly comprehends its intricacies. Nowadays, people often focus on microseconds, assuming they grasp the technical aspects, which can be misleading.

Although Continuous Integration and Continuous Deployment (CICD) may seem attractive for automated deployment, the allure of the cloud has somewhat overshadowed the significance of meticulous deployment, as it's often perceived as someone else's responsibility. This shift in perception, coupled with tools like CircleCI, requires a closer examination of their efficiency compared to more conventional platforms like Azure. Understanding the true speed and efficacy of these tools is imperative for making informed decisions.

The shift in the deployment and maintenance is evident, as manual installations are no longer the norm. Intelligence is now directed towards automation, emphasizing the importance of testing. Once this process is completed, confidence in the system's functionality increases, alleviating concerns about manual loading and ensuring an automated and efficient workflow.

Everyone in our organization follows the mindset of having our proprietary tools. The majority of our internal tooling is developed in-house, making us predominantly a .NET-centric environment. While it's true that we also provide Java solutions, most of our confidence lies in .NET due to its reliability. Reflecting on past experiences, there were initial concerns about how autonomously and optimally .NET could run, especially in terms of memory management. However, over time, particularly with the introduction of .NET Core, those concerns have dissipated, and I am now completely confident in the reliability of .NET.

In the interim, there's no need to purchase videos for viewing. Microsoft has made significant moves in the .NET space, starting with their response in Visual Studio Code and now providing Visual Studio entirely for free. This is a notable shift from the past when we used to pay substantial amounts for technical subscriptions. Previously, a group of ten developers could cost several thousand dollars annually for licensing. However, the current trend is to offer these tools for free to maintain their dominance in the developer market. The market dynamics have changed, and now developers can freely download Visual Studio, making it a preferred choice over other paid options. 

It has been around for about three months, and I've had a chance to delve into the capabilities. As for the .NET Framework, it's advisable not to use it anymore. While there might be some exceptional cases, I don't consider myself an expert on .NET Framework. The trend is shifting away from Framework towards .NET Core and now .NET 5. I would anticipate platforms to adapt and run seamlessly on the newer versions. Transitioning from Framework to newer versions might not be straightforward, particularly in terms of setup and configuration. Working with .NET Core involves a different approach, especially when dealing with configurations and influencing the product's behavior externally.

Switching everything from Framework to .NET Core in a short span may not be feasible, and even if you plan to do so, existing products and customer preferences may necessitate keeping the older products alive. Users may inquire about their familiar products, and it's essential to maintain support for them. Despite these challenges, I find .NET Core, particularly version 8.5, to be highly commendable. It excels in various aspects and is a robust platform, rating it 8.5 out of 10.

We use the solution for DevOps for implementation release.

The boards within Microsoft Azure need improvement, especially compared to Jira, a widely utilized ticketing tool in various organizations. While Jira is cost-effective, Azure provides various features in one place through its DevOps console. However, some shortcomings in Azure's boards and Wachee require attention. These tools might suit specific industries and workflows, but enhancements in Microsoft Azure's boards and infrastructure are necessary for larger-scale enterprises with complex architectures.

I have been using Microsoft .NET Framework for two to three years.

The solution is stable.

Our client utilizes the Microsoft Stack. Therefore, we must collaborate with them for internal Proof of Concept (POC) and presentations to attract new clients. We have around 250 Microsoft users. Within this context, various components such as ETA, specific developers, working with Azure, and blockchain development are conducted within Azure.

The solution is scalable. We are using the enterprise-level subscription

Around 200 people are using Microsoft .NET Framework.

We have a dedicated support system and have subscribed to it specifically for enterprise-level digital data scripts from Microsoft, which provides us with reliable support lines.

Positive

I worked on alternate servers to build the .NET applications. I have created some pipelines for the automation practice.

I have used the .NET Framework to develop applications and build pipelines. Additionally, I have implemented multiple pipelines in the data science domain, handling data. It is easy to design and manage these pipelines.

If you spend some time delving into web development, such as watching YouTube videos, you can discover solutions that may not be as complex as AWS cases. However, Azure offers a user-friendly interface that simplifies configuration and pipeline creation. You don't need to write Java code because, with additional settings in your pipeline, Java can be automatically generated. Configure these settings, write the necessary scripts, and deploy. Azure provides an incredibly cool, user-friendly, cost-effective dashboard that allows you to do more using the GUI.

Deploying applications using the Microsoft .NET Framework involves creating a pipeline. It can be done quickly; within a few minutes, you can deploy applications.

I am the sole developer and engineer responsible for managing the entire pipeline creation process. This involves collaboration between developers and operational teams. My role encompasses implementing solutions and deploying them through Azure DevOps. The team has completed the website development, and my task now is to establish an efficient deployment pipeline that doesn't require extensive time for construction or interface.

We don’t need to pay any particular ownership charges for creating pipelines on the .NET service. We have a monthly subscription for the solution.

Azure offers numerous automation systems that are already predefined by Jira pipelines. Consequently, there's minimal intervention required as they come pre-configured for build tests and deployments. Our primary task involves configuring these setups according to our specific requirements—determining where we need to deliver and retrieve items, thus necessitating consideration for various concerns within the Azure pipeline.

Connecting components in building .NET applications becomes straightforward due to Azure's facilitation of these operations.

It doesn't require regular maintenance, but there may be instances where updates are necessary to address specific application issues or to ensure compatibility with certain updates. In the context of Azure, there is no need for additional maintenance tasks. Once a pipeline is created, the focus remains on managing that pipeline, addressing any configuration issues, or troubleshooting when necessary. There is no direct need for manual updates or upgrades for software-related updates, as Microsoft's internal IT manages these processes. There's no individual requirement for us to handle service upgrades or updates.

Microsoft Azure is highly efficient across server environments, including .NET and other frameworks like Java. It supports a wide array of servers available in the market today. Current technology seamlessly accommodates diverse server infrastructures, making it notably efficient and ideal for enterprise-level operations. I rate it a perfect five out of five for its performance in DevOps and delivering sophisticated solutions to complex challenges.

We've extensively utilized Azure in the logistics industry, implementing numerous solutions with a significant reliance on its services. Azure covers almost all data analytics, data science, and data engineering aspects. As a developer, I've been solely responsible for implementing and constructing nearly all pipelines within Azure DevOps to address these complex problems. This stands as a benchmark achievement.

Azure's user-friendly interface and productivity make it a standout solution within the Microsoft suite. I highly recommend enterprise resources consider migrating to Azure when contemplating a move to the cloud—it's the top choice.

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

I have been using the tool mostly for building web applications. Azure’s cloud integrations are pretty good.

The project that I worked on was a legacy application. It was pretty easy to use once we learned about the stack and understood the MDC architecture well. The product incorporates ML features and is continuously improving its features. The learning scale is good. We need a scalable website if we want dynamic web content for more than 5000 users.

In-built refactoring and .Net profilers are the most valuable features of the solution. We can use any language. We can use the product’s compiler to generate an intermediate language. Currently, the solution is becoming platform-independent. MAUI is not a specific platform or environment.

Since the product belongs to Microsoft, users trust it. The scalability of the applications built into the solution is pretty good. It can handle much workload. Microsoft keeps improving its tool stack based on market updates. It incorporates artificial intelligence and machine learning features. The solution also provides content embedding and multi-factor authentication.

It is not a pretty compact product because of the assemblies that are being loaded. The cloud features must be improved. The deployment must also be improved.

Automatic code completion and natural language processing would be a good addition to the tool. I'm not sure whether these features are already present.

I have been using the product for the last five years. From 2018 to 2020, I have been using versions 4.5 and 4.6.2. After 2020, I moved to .NET Core 3.1.

The tool’s stability is good. I rate the stability a seven and a half out of ten.

I would rate the tool’s scalability a seven or seven and a half out of ten.

The support is good.

Positive

The initial setup was straightforward. Large-scale deployments are done on Azure’s cloud, and it's easy.

I definitely see a return on investment.

The product’s pricing is a bit high. It's not an open-source tool. Organizations prefer the enterprise edition. Though there are some restrictions, developer versions are useful for learning purposes.

The product has to compete with Spring Boot.

People wanting to use the solution must learn the basics as much as possible and explore and utilize the features. Overall, I rate the product an eight out of ten.

We utilize the Microsoft .NET Framework to develop software applications, including those that are dot net based. Our work involves a wide range of tasks, such as content management systems (CMS), website creation, database management, and data analysis. Whether it's related to content organization, database reporting, or intranet and internet solutions, we cover it all. Our toolkit includes Microsoft SQL and SQL cluster servers, enabling us to leverage a comprehensive set of tools and technologies.

We have this solution deployed on public and private clouds.

We are actively involved in software development and one of the companies we are affiliated with is Ingeniux.com. It is a mid-market content management software provider based in the United States. Our focus lies in content management, where we enhance the platform with numerous application extensions and plugins. Our target user base primarily consists of mid-cap corporations and universities. Ingeniux.com serves as a well-managed alternative to WordPress, offering superior functionality. While we also have experience working with WordPress, our primary development framework for Ingeniux.com is Microsoft .NET Framework.

The most valuable feature of Microsoft .NET Framework is debugging.

If AI could be incorporated in Microsoft .NET Framework it would be helpful.

In the majority of networks and development companies, individuals are not solely limited to using the Microsoft .NET Framework. Microsoft has made significant strides in integrating various technologies, enabling seamless data flow. This integration is prominently seen in visual studio, where Microsoft emphasizes streamlining the development process. While not entirely platform-agnostic, visual studio exhibits a high degree of compatibility with different platforms, allowing for greater flexibility in development.

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

When utilizing Azure for hosting, the stability can be unreliable and inconsistent. It becomes a hit-or-miss situation. As a result, we prefer to host everything in our private cloud rather than relying on Microsoft's cloud services, as the stability is not optimal in the latter case.

We have never had an issue with the scalability of the solution.

 I rate the scalability of Microsoft .NET Framework a ten out of ten.

The support provided by the Microsoft .NET Framework can be considered satisfactory to commendable. We have submitted numerous bug reports for Azure, and in some instances, their response indicated a lack of prior knowledge about the issues being already live.

Starting from scratch can be a complex endeavor, but once you have prior experience, it becomes more predictable.

I have seen a return on investment using Microsoft .NET Framework.

Considering the bigger picture, opting for the Microsoft ecosystem can be beneficial and it is priced well. When relying on entirely open-source solutions, you may encounter challenges associated with dealing with multiple vendors and potentially compromised security measures. However, it is important to note that Microsoft could enhance its performance when it comes to addressing critical security concerns.

When conducting high-level bug analysis and providing feedback, the process often involves navigating through a complex maze of procedures. Opening a ticket may require going through various steps, making it challenging to reach someone directly involved in software debugging or problem resolution. The help desk system at Microsoft may exhibit elements of hierarchy and bureaucracy, which can add to the difficulty of accessing the appropriate support channels for addressing software issues.

I rate Microsoft .NET Framework an 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.