What advice do you have for others considering Microsoft .NET Framework?

I would recommend using the latest version of Microsoft .NET Framework, especially for cross-platform and cloud-native applications. I'd rate the solution eight out of ten.

We use the solution for development purposes. When it comes to security, we depend on two levels of security. The first level is what Microsoft .NET Framework gives and the patches that Microsoft provides. The second is our internal security algorithms and logics. Licensing plays a big role when you have other systems. When using Microsoft .NET Framework, you start writing the code internally. This reduces the cost on the licensing side, which helps reduce the overall expenditure of OpEx and CapEx. I would recommend Microsoft .NET Framework if you start developing your tools and products in Microsoft. This is one of the platforms that Microsoft provides. If you are into .NET and want to develop a lot of applications, you need the Microsoft .NET Framework platform. We perform the solution’s maintenance in-house. Overall, I rate the solution ten out of ten.

The Microsoft .NET Framework enhances the development capabilities for mobile and web applications. The solution helps in developing computer applications in multiple languages and for local platforms. Microsoft .NET Framework is known for security features, so we haven't had any security incidents or breaches in our organization. There are four or five applications in our company that have been developed in the Microsoft .NET Framework. The performance of applications built with Microsoft .NET Framework depends on the server. All the applications we have built in our company using the solution don't have any response issues. I would advise others that the solution is worth it if there are full-stack developers in the company. A lot of possibilities get unlocked in C# and JavaScript when using Microsoft .NET Framework. I would rate Microsoft .NET Framework as a nine out of ten. I would definitely recommend the product to others due to its flexible capabilities.

It's essential to explore your options before making a decision. Microsoft offers the traditional .NET Framework. There are superior alternatives within the company's offerings. It remains a viable choice if your project demands a legacy framework like the .NET Framework. However, if you can choose, I highly recommend opting for the latest iterations, such as .NET Core versions like .NET 6 or 7. These versions offer enhanced support and features, making them preferable choices. I advise you to consider the specific requirements of your project. Before .NET, we used C++ and C and many other languages that did not use CLR. They were not memory-managed like the .NET Framework. Shifting to managed solutions which have CLR brings productivity to the development team. We don't need to consider garbage collection and memory in .NET because the framework will handle it. This increases our productivity. If somebody is using C# or VB.NET, you need one installer from Microsoft to take care of everything. Two different languages will translate to the same intermediate code. The only competitor to .NET in the market is Java. .NET Framework consumes much memory. The .NET Core framework requires less memory and offers firm support. It is very easy to learn compared to other languages. Five years ago, I would have rated it eight or nine. But now, since we already have superior products, I rate it six or seven due to the need for more portability and many legacy component dependencies. I rate the latest version of .NET an eight to nine out of ten.

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.

In my company, we use the tool for sales projects, CRM purposes, B2B projects, and creating applications. The tool's feature that has been very beneficial for the development process stems from the fact that it is very easy to develop applications and to find a knowledge base of Microsoft. The integration of Microsoft .NET Framework with other Microsoft tools has impacted our company's workflow since we have integrated it with Office 365. Microsoft .NET Framework is a good product with a bright future. The maintenance of the product is very easy. I rate the product's capability a ten out of ten in terms of the learning curve for developers who are new to the tool. I rate the overall tool a ten out of ten.

Overall, I would rate it nine out of ten.

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.

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.

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 rate Microsoft .NET Framework an eight out of ten.

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.

Overall, I would rate the solution an eight out of ten.

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 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.

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

The solution does not require maintenance. I would advise others to use the newest version of the solution. It is a good solution overall. I rate Microsoft .NET Framework a nine out of ten.

I am working as a consultant for this solution for various companies. I would recommend this solution to other people. I would rate this solution as a whole a 10, on a scale from one to 10, with one being the worst and 10 being the best.

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.

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.

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 would rate Microsoft .NET Framework a nine out of 10 overall.

.NET Framework is very versatile and dynamic and allows us to change properties and customize the controls. If you're familiar with programming, you can go ahead with all the functionality and create new products. I would rate .NET Framework nine out of ten.

My advice to others would go to get some training. This solution is best used with some training. I would rate Microsoft .NET Framework a nine out of ten.

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 rate Microsoft.NET Framework as a five out of ten.

If you want to build automation without much technical expertise then I would say not to go with, . NET. With. NET, you need the technical expertise. If you are looking for something that is readily used to be available for automation, then I would say to go with RPA tools. Also, if you want to go ahead with low code, no code platforms Power Automate gives you RPA capabilities without the user knowing the technical aspect of it. I would rate this solution an eight out of ten.

We'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.

I would definitely recommend that anyone considering implementing the solution do a proof of concept. That gives you an idea as to whether you're on the right path. A company also needs to take into account the requirements of their organization in terms of scalability and ease of maintenance and also whether they have the skill set to maintain the IT resources required. A lot goes into it but proof of concept would be good before going ahead. I would rate this product an eight out of 10.

My advice is that C# is a very rich language with lots of advanced facilities, which makes it easier to develop by not being too complex. There are a lot of libraries in out-of-the- box .NET Frameworks, which gives you tools to do almost anything you need and there are extension libraries for most of the rest. It's not the same as Python which is a bit slower but has a lot of libraries because everybody writes libraries for Python. But most of the time I find what I need. I would rate this product a 10 out of 10.

We are official partners and we are sellers for UiPath. For Microsoft, however, we're just customers. I'm not sure which version of the solution we're currently using. I'd advise others to find a solution that is suitable to the customer's needs and to examine the customer's business case before deploying anything. In our case, this solution was something that is a bit more expensive. However, it's of the highest caliber and it's stable. In this scenario, it made sense for us to choose Microsoft. I'd recommend the solution to others serving a similar type of customer. I'd rate the solution eight out of ten.

There are proper resources. Stability and scalability are quite good. We handle 3000 to 4000 users at any time and they are users from all over the world, including North America, Australia, and the Middle East. This is a good option for the level of the audience. We are using version 4.5 but we are gathering a few more projects that are running on version 4.7 and 4.8. I would rate this solution a seven out of ten.

Talking from an application developer's perspective, this platform is very helpful because it provides a common development line across all of the products that Microsoft provides. This includes things like Microsoft Dynamics, the Cloud Integration tool, and SharePoint. It makes it very easy to jump from one application tool to the other. The Community Edition can be used free of charge and is helpful for both new developers, as well as those who are shifting to the Microsoft platform. Over time, this product has matured and all of the new features have been helpful in improving the performance of application developers. Overall, we are very satisfied with using this platform for application development. It is very good. That said, there is always room for improvement. I would rate this solution a nine out of ten.

Small clients don't do their development internally. We have three of these types of clients. Small to medium-sized organizations don't have an environment because they are easy to develop with easy requirements. I would recommend this solution but it depends on the environment and what they want to do. If you do mobile applications, to avoid the headaches of doing development on multiple platforms, I think that .NET is something that really works. We have tried everything, so when we try iOS it becomes a problem because we have to re-develop what you do for Android on iOS, even though we don't use Windows phones anymore. We can still use the same tools for your desktop applications. If you have a different environment then you have to develop based on whatever application you are going to run your application on. I would rate this solution an eight out of ten.

My advice for anybody who wants to use the Microsoft .NET Framework is to have the proper foundation before implementing the solution. This means that they should lay the architecture first, properly, and then develop the solution based on the architecture. Without this, the solution will not be scalable and will suffer from problems in the long run. This is a good solution but there is always room for improvement. I would rate this solution a nine out of ten.

This is a product that I recommend. I would rate this solution a ten out of ten.

This is a solution that I recommend, but the best versions to have are 3.5 and 4. I would rate this solution an eight out of ten.

One piece of advice that I would give to people considering the use of this product is to use it because of several things: it is free of charge, it is fast, it is compatible with Microsoft Windows, and whenever a new version comes out, it supports the older version. These are all very good points. The development of the framework is really good and was approached intelligently. If considering other options, when you want to use a framework, you have to look at its ability to work with different types of other products. With the.NET Framework, you are able to work with different environments like Microsoft SQL Server 7, MySQL, Oracle — any kind of database. You have to also know its limitations. It is my opinion that when you want to use the .NET Framework, it is a very good solution and you can have confidence in the functionality. The stability of the framework you choose is very important. On a scale of one to ten with one being the worst and ten being the best, I would rate this product as a ten because my standard is Microsoft products.

With the advent of IoT, combined with cross-platform development, the .Net framework becomes much more versatile. We should begin to see apps scaling down in size, but also (literally) covering more ground.