If you were talking to someone whose organization is considering Microsoft .NET Framework, what would you say?
How would you rate it and why? Any other tips or advice?
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.
This is a product that I recommend. I would rate this solution a ten 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 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.