.NET

Solid foundation

Good support from Microsoft and the community

C# is an excellent language to use, it is well designed and likable

Fairly performant

Integrates well with SQL Server

Integrates well with IIS

Convoluted and complex class hierachy

Feels a bit dated (it comes from the Java era after all)

Microsoft has started ending support for older versions of the framework

Can be slow to develop with initially, as setting up the required scaffolding takes time

Documentation can be a bit hit and miss nowadays

Feels a bit boring and uncool when compared to newer tech

Multi-threading.

Robust development.

Linq.

Object oriented development.

Garbage collection.

It's not lightweight.

Needs special tools to execute.

Quick deprecation of older versions.

Provides a modern memory managed multi-language platform and framework for software development

Supports modern web and mobile application development

Provides performance approaching that of a compiled ahead of time language

The .NET framework class hierarchy is incredibly large and complex

Performance is slow on first use due to just in time compilation

Memory use is high and non-deterministic due to garbage collection

Power

Versatility

Community

Cross-Platform

Documentation

Desktop Support

Compiles the code so users cannot see the source code, and we can keep our IP protected.

Works well with JavaScript, CSS, HTML, and other code languages.

Can be hosted on powerful servers and process very large data sets

It could use more responsive UI components, to allow UI components to work well on multiple device types with different resolution.

Has many methods, allowing for easy programming.

Is regularly updated to ensure security.

Is very widely used and has lots of information readily available online.

It is quite a big package.

When using it to build a program, it requires the package to be installed in order for the software to work.

It has a large community of developers who are always contributing to it.

It has great customer service.

It is intuitive to use and makes it easy to create new projects.

The pricing can be high depending on the project requirements.

May require the installation of the entire framework to run.

Sometimes has dependency issues with other software.

Pure [object-oriented] programming

Super fast in developing time

Robustness

Reusability of code

Access windows API easily

Database accessing could be easier

Interfaces

Web services are confusing (at least classic .NET ones)

Cloud Integration with Azure and AWS

Xamrarin Forms Cross-Platform Mobile Development

.NET Core Server-side Implementations.

Front End Web Development

Speed of development - Visual Studio takes care of all the boilerplate

Cross-platform compilation - develop for any platform

Easy GUI design for even the least frontend-inclined developers

Code can be slower and heavier than writing it natively

Version and dependency upgrades can cause hard-to-find bugs

Memory leakage from managed code is possible

Powerful IDE( Visual Studio)

Developer Friendly

C# Language

Performance

Stability of New Releases

Licensing Cost

Visual Studio is one of the best IDEs and .NET is the best framework to use with Visual Studio.

There is a large network of support for the .NET framework.

The .NET framework encompasses a very large area of the programming stack.

The .NET framework is flexible and can be used for desktop applications or web development.

Sometimes, the .NET framework overcomplicates simple things.

The .NET framework is not the most popular framework and thus other frameworks may provide access to more tools and libraries.

The .NET framework requires licensing.

Comes bundled with Visual Studio, which is one of the best and lightest IDEs in the market.

Easy to learn, with a lot of online resources and open source codes to support.

Heavily supported by Microsoft, and integrates well with Windows especially with network user authentication.

Supports multiple languages and allows for easy cross-projects integration.

.NET is heavily Microsoft Windows oriented, and while .NET core tried to resolve that with MacOS and Linux support, .NET Core is still waiting for wider adoption.

While free for small projects, additional features for big projects can be a little expensive.

Can be resource-heavy upon deployment. We continuously have our more senior staff optimize the code of our junior developers for performance. Other languages are a little bit more forgiving in comparison.

.Net accelerates development by focusing on business features rather than low-level development.

There is a very large and active community for support should you run into problems.

The latest .NET core runs on linux servers, which can reduce hosting costs.

.Net development using visual studio is better than any other development platform.

UWP development using .NET can be challenging because there's a smaller community behind it.

If you do very unique development in .NET, you may come across some very low-level bugs that extend beyond the development community.

.Net Framework, .NET Core, and .NET standard can be confusing at times. The upcoming .NET 5 will hopefully clear this up.

The most helpful aspect of .NET is the large user community. I have on numerous occasions put out a question about a problem I was having and was helped by at least one .NET developer from the community.

With .NET Core becoming more mature, it has helped us build our applications to be able to run on any platform without doing too much extra work. Our internal customers have not asked for this but we anticipate that they will and .NET Core allows us to be ready for that.

As our applications develop over time and business needs change, .NET has proven that it remains stable for backwards compatibility.

We've found that depending on the type of application that you're developing, resource usage can be high at times. This is something that we've needed to keep in mind especially during peak usage of our applications.

We've found that dependency management can be an issue at times. This has messed up our builds once in a while.

Better and real-world online examples of new methods and classes would be beneficial.

Provide great solutions to solve software needs

It has a large community of developers

Is supported by Microsoft, a great and reliable company

It has extensive documentation and content over the internet

We think that it would be better to have another cross platform's initiatives, besides Xamarin.

Suitable for dynamic and complex processes.

.NET is a great technology for cross-device app development.

Managed code can be slower than native code.

Future development is solely dependent on Microsoft.

Backwards compatibility has been great.

IDE used are modern and up to date.

Documentation has been great.

We've spent hours improving and updating based on new features provided as part of the core libraries.

Resource usage can be very high.

Runtime will require Windows machine unless you use .NET.

Dependencies can be complicated.

Microsoft .NET is fairly universal coming pre-installed on Windows machines and servers

Microsoft .NET is a very stable technology that has been around for a long time with a lot of support.

Microsoft .NET has a very wide user base and is easy to get assistance.

Older versions of Microsoft .NET were plagued with security holes

Microsoft .NET can sometimes be painful to upgrade from one version to the next

Microsoft .NET is not the back end to .net core the way MS is going

Provides an extremely robust layer on top of the OS.

Allows for multiple languages to compile into equivalent intermediary language.

Incredible suite of methods and built in functionality for getting an application up and running.

Sometimes can be difficult traversing exceptions to find root causes.

Null references can sometimes feel annoying and unnecessary, although the latest .NET has improvements here.

General purpose development which makes it easy to create new projects

Powerful set of tools. Anything we need developed we can do it using .NET framework

Very fast execution. Well designed code can be as fast or faster than c code.

With the conversion to .NET core it is confusing what to do for New development. Also .NET core vs .NET standard. More confusion.

Prior to .NET core there was certainly a Microsoft only mindset. This limited adoption.

Asp.NET features like early binding, JIT compilation, caching services and native optimization supports gives your application the high level of performance.

All the Asp.NET applications are highly monitored and managed to help application available to handle requests.

The best part of .NET Framework is it has its own built-in caching features.

The content and the program logic are separated in the .NET Framework, thus reducing the program inconveniences.

Offers great security with the built-in Windows authentication and per-application configuration.

Limited object-relational (OR) support as it comes only with Entity Framework

Does not come with multi platform support from Microsoft, and is not available right after installing Visual Studio

The managed code can be slower than native code

Involves a vendor lock-in, and future development is solely dependent on Microsoft

Migrating applications to .NET can be expensive as involves whole lot of custom development

It allows the use of multiple languages. It has horizontal scalability.

.NET creates a unified environment that allows developers to create programs in C++, Java or Virtual Basic. All tools and IDEs have been pre-tested and are easily available in the Microsoft Developer Network.

UI best practices are more consistent.

Language integration is seamless, as you can call methods from C# to VB .NET.

You need to buy everything from Microsoft. The biggest con is that it is not free like Java. Migrating applications to .NET can be expensive.

Does not come with multi-platform support from Microsoft, and is not available right after installing Visual Studio.

Very much Windows OS dependent.

Most powerful framework that works well

Best integrated with the best code editor around, Visual Studio

Support for multiple modern programming languages like C#, and F#

.NET Core is still gaining adoption

EF Core does not support lazy loading yet, a feature we use a lot

A lot of the libraries we use are not planned to work on .NET Core yet

Memory Handling

Garbage Collection

Service Orientation

Extensive Framework

Image manipulation slow compared to C++.

Does not run on Mac/Linux - the newest .NET core does but presents only a subset of the framework.

May require the installation of the framework to run.