.NET vs. Play vs. FuelPHP

Microsoft has done an incredible job of keeping the .NET Framework powerful and stable. It is well designed and keeps getting more robust with each release. It isn't the most popular technology in this space, but I think a good case can be made to use .NET in many new projects.

Mainly C# development, ASP.Net MVC, Web API

Frameworks: Signal-R, OWIN, etc.

windows service to access on-premises data

Openlink application architecture.

.Net is our primary stack.

WCF, WPF, ASP.NET Core, Entity Framework Core, XAML

As we started on Windows Phone we use C# and .NET for most of our apps and sites. Being a small team of 2, using .NET enables us to work on each part of the service without having to switch to different languages.

简单好用就用了

Server side development language and frameworks: ASP.Net MVC 4, Asp.Net WebApi 2, Razor View engine, Moq, Entity Frameworks, etc.

ASP.NETやVB.NETでの業務アプリ開発（そんな触ってない）

Main library that we use 98% of our backend code is in .net

To build apps.

Base platform to build the entire solution

some backend process. and Unity ( the game engine that roster plus base on) use C# and .Net Library.

F# (FSharp) environment

Backend framework

We have a .Net client library for the ThisData API

Used to create API for authentication with existing Active Directory server

Not by choice... (used it to build my master's portfolio and at various jobs)

TwinCore creates modern web and cloud applications based on .NET TwinCore supports legacy .NET applications

We use a combination of .NET Core and .NET Framework for our ASP.NET Core APIs.

I use .NET alongside with C# since my university studies, and I really enjoy it. Especially .NET Core, which is the best thing that happened to Microsoft since... ever.

Backend framework.

API server framework

REST API

Backend RESTful

Web framework

I used Play to build a configuration UI for the service, which let you create and manage the menus (a hierarchical tree of options and actions).

Play is a central framework/component/library (not sure what to call things these days) in Scala. We <3 Scala, and therefore we <3 Play.

Play is on of several frameworks we are prototyping and vetting for various public-facing websites, and may ultimately be the framework behind the main datapile.io website.

Moving some micro services to Play Framework with Scala

used play at talenthouse. uber powerful backend.