Microsoft .NET Framework Reviews

As an architect, I figure out the best solution based on the problem at hand. It doesn't always have to be a website. Sometimes a hybrid solution is needed – one solution that can be ported to mobile or websites. I want to avoid having two different sets of code that need changes in two places. My goal is to make it as generic as possible.

So, I stay updated with the current .NET Framework and try to come up with a hands-on architecture. I develop those centric modules and provide libraries to our developers, which they add as project references. I call them the organization's libraries. This way, everything follows the same design principles.

For instance, if I create a website using the MVC framework, it has to be consistent. If I need architecture on top of it, I would use screen architecture. Then, there are other architecture and design types. If I need to write a Windows application, I prefer WPF (Windows Presentation Foundation) with the MVVM framework.

We pick and choose what's needed based on complexity, data volume, storage, etc. Would the architecture be three-tier, service-oriented, or domain-driven? You break things up into database, API, and front end. Recently, I've introduced gateways for security, which have their own design pattern. I'm trying to move from API to microservices – it's about staying up-to-date and educating the team and managers.

ASP.NET within the .NET Framework improved our development process.

With the old ASP.NET, if you were using web pages, you had the traditional page lifecycle. The introduction of MVC changed things – they're two different lifecycle methodologies. 

MVC is lighter, faster, and easier to implement, while the old way goes through its own page lifecycle before rendering, which is a bit slower, in my opinion. 

Now, with .NET Core, you get out-of-the-box stylesheets like Bootstrap and more of a boilerplate setup. It's much easier – before, you had to build everything yourself. Now, with the .NET CLI (Command Line Interface), development has become even simpler.

A team of developers in our organization are using the solution. Microsoft .NET Framework is used in our company for web and mobile application development. 

The solution has assisted our organization in the full-stack development process. The tool can be deployed on all types of devices, including mobiles and desktops. The MAUI capabilities of the solution have been the most beneficial feature for our organization's development needs.

At our company, we never had the option to develop for external users. By using specific frameworks from the solution or MAUI, our company has been able to develop mobile apps that can be deployed externally with utmost security. 

The product exhibits impressive compatibility. In our company, the solution is being integrated seamlessly with iSeries, K2 Environment and all vital databases where the data is stored in Db2 and SQL. 

I'm a developer with .NET Framework. Apart from powering the Xamarin platform, I also use .NET for API development for .NET Core, which I deploy on clouds like Azure or AWS. We use .NET Core for every solution, from built-in web apps to REST APIs. I can use .NET Framework to build desktop-based applications using a company called WPF. We use .NET for Unity, a popular gaming engine. It uses .NET as well as C#. In our organization, we just use .NET for Xamarin.

Given that it's cross-platform right now, where you can use it on Windows and Mac, that is the single most significant feature that has resulted in wider adoption of .NET. Earlier, you could only build solutions for Windows and Windows server ecosystems, but now you can build a .NET Core app and deploy it on Linux VMs, and so on.

We utilize Microsoft .NET Framework for domain and web applications. We have also developed console applications and Windows services using this framework. In the past, we employed WPS upon its launch for various purposes, including web services. Currently, our focus has shifted primarily towards web applications. We are leveraging the latest versions, such as .NET 6 and .NET 8, to develop our web services.

We have different layers of security, one on the application side and another on the network side. Over time, security has continuously improved and has remained a sensitive issue. Microsoft Framework has solutions the security department recommends, enabling us to incorporate them into our solutions.

Microsoft .NET Framework is a development platform.

The web development and Microsoft Windows service development capabilities are among the most valuable features offered by the Microsoft .NET Framework. This language platform is highly user-friendly, with plenty of online examples and information available, as well as a robust development environment.

We use the solution for some internal applications we develop. We also use the Microsoft workflow engine.

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 use Azure DevOps because we have everything implemented in .NET by Microsoft, and we are integrated with the collection of the requirements, the .NET pipeline, and directing Azure DevOps for Azure Plus. I am more of a developer, so from an infrastructure point of view, I do not have feedback or experiences to share. I use it more for requirement documentation. For historical reasons, our product was born in .NET.

For us, it is better to remain under the umbrella of Microsoft.

We are creating a certain solution. There is a client, the desktop Windows application, that is used within the organization. And behind it, there are certain Windows services, and there are kinds of Windows services that run on a scheduled basis. And there's a logic behind which kind of receives data in the form of files or APIs from different endpoints. So, basically, we are working with multiple external entities, and those entities, in some cases, communicate with us via API. And in some cases, they send us files, which are huge files, via a file gate. 

So, .NET, in that sense, we are using after receiving those files, we process them as normal. Then, there is communication with multiple endpoints to actually update certain backend gate systems within the organization. It's a good, big implementation for business purposes of the .NET framework. And the team that I'm a part of is responsible for creating those new requirements that we get from business. We create the solutions for that within this application as part of that application. Also, we are maintaining that application in the production environment, which is being used for running the business.

When we talk about .NET development, we use Visual Studio IDE to create these things. In recent years, there have been a lot of improvements in Visual Studio 2022. It would be a daunting task to list all of the features that have benefited us, as it would require a lot of time and effort. However, there are definitely many improvements year after year in .NET development. 

One of the improvements is the ability to make changes to the code while debugging applications within the environment, and the changes will be reflected in real-time. There are also many other improvements, such as the integration of Git and Azure DevOps.