PallarelCoedr

The stream is the consistency (locking) boundary. Your first step it to get your model aligned with such boundaries. For example, your amazon shopping basket is independent of my basket. Then you chose your concurrency model - append to a stream with an expected version (pessimistic) or just append anyway (no expected version). Your amazon basket may be the later, your amazon payment and shipping checkout may be the former.

Locking across streams is an anti-pattern / smell. It can be done (as can anything) but it usually points to a modelling problem. Example: cancelling an amazon order is a _request_ that is in a race with the fulfillment system (boundary); it may or may not be successful.

Embrace eventual consistency. A good deal of collaborative domains (things involving human decisions) are naturally eventually consistent. Meat computers appear to be particularly good at resolving conflicts and compensating.

Perhaps look at HTTP Problem Details? https://tools.ietf.org/html/rfc7807

Forget about older ASP.NET and WCF on mono. The core of ASP.NET (System.Web assembly) doesn't feature in next version of ASP.NET. WCF hasn't seen any effective development in years.

The new stuff (ASP.NET vnext) will be highly mono compatible and like the current OWIN stuff, entirely decoupled from IIS.

It does, but internal abstractions have been rewritten. Webforms view engine won't be ported I reckon.

This reads like a standard list of a cocooned MS developer. With ServiceStack, NancyFX, NHibernate, Dapper, OrmLite, etc out there could you have just been making some bad choices?

And anyone who knew web, knew Silverlight didn't have a future from the very beginning.

It's 'Drawbridge'[0,1] in the windows world and it is on it's way apparently.

You can run mono in linux containers which means you can run this stuff too.

[0] http://www.zdnet.com/microsoft-to-offer-its-drawbridge-virtu... [1] https://research.microsoft.com/en-us/projects/drawbridge/

OWIN will give some of what you are looking for.

Three here: quora, w3schools and expertsexchange

They have open-sourced quite a lot (aspnet webstack, reactive extensions, etc). The problem is that a lot of their compiled binaries, delivered via nuget packages have been restricted to windows. This is slowly being undone ( http://blogs.msdn.com/b/dotnet/archive/2013/11/13/pcl-and-ne... ).

Another problem is that they don't run their open source projects in an open manner. Contributing requires a CLA and a signature from your boss. Issues and planning are often behind closed doors, but that seems to be slowing changing too (see KatanaProject / signalr).

If they really wanted to grow their ecosystem 10x, and give windows phone the possibility of a fighting chance, making VS Pro free would be the required.

Related to the launch of the Pirate Browser perhaps?

.NET folks don't particularly like him either.

Can I use a browser other than IE on it?

Too much space wasted across the top too. Looks promising though.

They probably didn't want them to stay around permanently, just long enough to complete knowledge transfer.

That's more geared towards web services, i.e. a WCF replacement (even though it supports razor view engine). Mentioned it in a comment below anyway :)

You will be, but not quite the way the author details. The OWIN [0] specification (which was solidified back in October 2012) was designed to completely separate .net web applications from their host (i.e. ASP.NET dependency on IIS). Similar to Ruby's Rack[1], it allows you to compose applications using one or more frameworks and/or middleware[2].

The KatanaProject [3], by MS, is a suite of projects for creating and hosting owin compatible web applications and is expected to see a v1 in the coming months. The ASP.NET (System.Web) host is already at v1[4](yes, asp.net can _host_ owin apps) and is used by SignalR [5,6] which is entirely OWIN based. Mono builds of KatanaProject are being worked on [7] (log on as guest). There are alternative non-MS hosts being developed, though not sure if any are serious projects yet.

A future version of ASP.NET MVC will support OWIN[8].

You can of course use .net alternate frameworks instead of ASP.NET, such as FubuMVC[9], Oak[10], NancyFX[11], ServiceStack[12]. I know that NancyFX and ServiceStack support mono (linux) as a first-class OT, concern.

OT, but you can even run node.js in-proc with OWIN based host.[13].

There is a lot going on in the .NET web app area!

[0] http://owin.org/

[1] http://rack.github.com/

[2] http://dhickey.ie/post/2012/12/16/How-I-am-using-OWIN.aspx

[3] http://katanaproject.codeplex.com/

[4] http://nuget.org/packages/Microsoft.AspNet.SignalR.SystemWeb...

[5] http://nuget.org/packages/Microsoft.AspNet.Signalr

[6] http://signalr.net/

[7] http://teamcity.codebetter.com/project.html?projectId=projec...

[8] http://aspnet.uservoice.com/forums/41199-general-asp-net/sug...

[9] http://mvc.fubu-project.org/

[10] http://amirrajan.github.com/Oak/

[11] http://nancyfx.org/

[12] http://www.servicestack.net/

[13] https://github.com/loudej/owin-js

Asp.Net Empty Web Application is the base project for an IIS hosted... asp.net app. It just contains the bare minimum web.config and project settings to get started. Though there are too many project references imho. All asp.net projects are based off this.

Asp.Net Web Forms Application is the original, and now derided, web framework. Consider it deprecated.

Asp.Net MVC Web Application is comparable to Rails / Django and the current version is 4.

The alternative to MS's MVC framework is FubuMVC [0] and is well respected.

Another alternative and is far more lightweight is NancyFX [1], .net's equivalent to ruby's sinatra [2].

[0] http://mvc.fubu-project.org/

[1] http://nancyfx.org/

[2] http://www.sinatrarb.com/

And it's a WPF one too.