AnthonySteele

##Setup

Many people have the misconception that async and sync code are mutually exclusive. This is not the case. It's easier than it seems!

If you have a method on an interface for async use, then the implementation can have zero or more awaits, and the case with zero awaits covers synchronous implementations. The code below will make this clear.

We have the following example contract that models a processor of messages:

 public class Request

AnthonySteele

This document has moved to https://anthonysteele.github.io/AgileValues

I got a lot out of Nathan Gloyn's talk at DDDEA on "Agile: I do not think it means what you think it means".

The slides of the talk are here.

The talk is about where it all went wrong - the mainstream adoption of agile, the brand-name of it, the descent into a cargo cult and the conflict between the principles and the rules.

One thing on slide #29 struck me as odd at the time: Don't be bound by "the rules".

AnthonySteele

using System.Web.Mvc;

namespace FeatureTest
{
	public class FeatureRazorViewEngine : RazorViewEngine
	{
		private const string ViewsPathTemplate = "~/Features/%1/Views/{0}.cshtml";
		private const string LayoutPathTemplate = "~/Features/Layout/{0}.cshtml";

		public FeatureRazorViewEngine() 

AnthonySteele

/*
 * Example code for my blog post on function shims for NancyFx request handlers
 * Blog post is here: http://anthonysteele.co.uk/more-patterns-for-web-services-in-nancyfx
 */
 
using System;
using System.Collections.Generic;
using System.Threading.Tasks;

using Nancy;