.NET Manufacturing Reviews & Insights

.NET is used across my department, it is used for [mission-critical real-time applications], for the manufacturing. It supports other software that run[s] in Windows O.S. so .NET can access [the] very easily and natively to the OS features. I use it even for integrating different systems, accessing DB, exporting data through web API, rest, etc.

Useful for background application, console, server-side. If you already know JAVA the migration would be seamless. a must if used in [a] windows environment. the developing and releasing time is very good, integration with source control systems like GIT is native, if you do not have visual studio professional, visual studio code is free.

We are using .NET as the platform for a majority of our Windows-based applications. It has provided us with a highly portable solution and has let our team build several solutions across the enterprise. We've gone through several generations of the software.

If you are looking to start building a development team and need a compiled language, I would recommend .NET as it checks all the boxes from a development platform. Easy to start, great IDE, good documentation and a very large user community to help answer any questions that you may have.

Microsoft .NET is currently being used widely across our entire organization. We are creating web apps, services, web services, console application and more with Microsoft .NET. Utilizing the Microsoft .NET framework we are able to integrate many different applications and data that could not easily be integrated without costly or cumbersome applications.

Microsoft .NET is excellent for creating custom applications that can integrate between non custom applications. The framework that Microsoft .NET provides allows you to quickly and easily stand up a custom application, service, web service or web application utilizing the same methods and classes making it a very seamless experience for the developer.

We have used .NET platform for developing both web and windows based applications that are internal and external facing. There are several use cases like
1. Inventory Management
2. Quality Control
3. Safety and Security
4. Packaging optimization
5. Logistics and Supply Chain Optimization

We have used in all the areas for Global Operations, Spares etc. organizations for all day to day production floor support and shipment releases. We also used it for Product Life Cycle Management interface to perform Problem Report and Engineering Change Management business processes.

To achieve these .NET and HTML together were used to generate dynamic web pages smoothly.
Being an ideal server-side scripting technology, Asp.NET code first runs on Windows server before displaying on the web browser.
With the built-in configuration information, Asp.NET is easy to deploy.
The .NET Framework quickly gives an alert for memory leaks, unbounded loops, and other wrong behaviors, immediately killing them and restart them over again.

I highly recommend .Net as a platform for custom development. We can leverage several UI elements and also integrate with third party controls like Telerik, Infragistics etc. Provides platforms, tools, and a programming environment for addressing the design and overall management of distributed and multi-tiered applications. It offers immeasurable benefits for various issues like memory management, security, and exceptional handling, a developer may face.

.NET is not suited in case of multi-platform requirement. There isn't support available from MS and isn't available straight after installing Visual Studio. If that is a criteria for your business case then consider a different platform.
Also .NET is very easy to reverse engineer. If you do not obfuscate your code, you may as well publish the source code.
The footprint of your application can be huge if it requires a version of .NET, which is not already on the computer and therefore has to be installed first.

I use .NET to create custom applications to support my daily engineering tasks. We have a batch process that feeds into a continuous process. The data historian that we use is excellent for retrieving information about the continuous process but is very difficult to grab information about each batch. I used .NET to create a custom application to interface with our data historian and summarize all of the process parameters for each batch, providing charts, tables, and summaries. Additionally, the user is able to overlay process parameters from several batches, to see if the process is changing over time.

.NET is extremely well suited for creating any custom application on nearly any platform. It does not matter if you are creating a word processing application, a graphics editor, or a calculator. However, applications that work in 3D are a little hampered in the .NET environment. There are packages available to provide classes and interfaces with the graphics hardware, but they are not as polished and easy to work with as the standard .NET interface.