Session-Materialien von der BASTA! Spring 2015

Hier sind die Folien zu meinen Sessions auf der BASTA! Spring 2015 in Darmstadt:


Vielen lieben Dank an alle Teilnehmer und an die Organisation der Konferenz!

Bis zum nächsten Mal Smile

Running Thinktecture Identity Server v3 with ASP.NET vNext on Ubuntu

Thinktecture was at the MVP Summit 2014 ASP.NET Hackathon: after Dominick and Brock had Identity Server running on ASP.NET vNext, I took a stab at getting that code working on Linux/Ubuntu.

For this I needed to clone and build Mono as there are a couple of necessary patches which are not yet in any released Mono build (see this blog post for details).

This is a very easy thing to do on Ubuntu:

git clone git://
cd mono
./ --prefix=/usr/local
sudo make install

After this executed successfully – bring … some… time! – we have the latest Mono version:


Next thing to do is bringing Kestrel as the HTTP server into the picture:

    "webroot": "wwwroot",
    "version": "1.0.0-*",
    "exclude": [
    "packExclude": [
    "dependencies": {
       "Kestrel": "1.0.0-*",
        "Microsoft.AspNet.Server.IIS": "1.0.0-beta1",
        "Microsoft.AspNet.Owin": "1.0.0-beta1",
        "Microsoft.AspNet.Diagnostics": "1.0.0-beta1",
        "Microsoft.AspNet.WebApi.Owin": "5.2.2",
        "Microsoft.Owin": "3.0.0",
        "Thinktecture.IdentityServer.v3": "1.0.0-beta3-1",
        "Thinktecture.IdentityModel.Core": "1.2.0",
        "Microsoft.Owin.Security": "3.0.0",
        "Microsoft.Owin.Security.Google": "3.0.0",
        "Microsoft.Owin.Security.OpenIdConnect": "3.0.0"
    "commands": {
        "Kestrel": "Microsoft.AspNet.Hosting --server Kestrel --server.urls http://localhost:5005",
    "frameworks" : {
        "aspnet50" : { }

As Identity Server comes with its own Test X509 certificate it is necessary to import this cert into the Mono certificate store – like this:

certmgr -add -c -p idsrv3test -m My idsrv3test.pfx

One thing that was left to get IdSrv finally running successfully was working around a bug in the ASP.NET vNext HTTP abstractions (GitHub issue – it has already been fixed Smile).

Once that was sorted out – tadaa!


Hope that helps.

Installing & Running ASP.NET vNext (Alpha 3) on Ubuntu Linux with Mono 3.8–for real

Yesterday I thought I would try and prove Microsoft’s promise that the new and overall cool ASP.NET vNext would run on many platforms, including Windows, MacOS X, and Linux.

My target platform for this experiment was Linux. First thing to do in this case is check out of of the myriads of Linux distros. After a bit of investigating I chose the Ubuntu-based Xubuntu. Very slick!

After installing Xubunutu (it took only a few minutes, literally) in a Parallels VM on my MacBook Pro, I went ahead to get Mono running. Turns out the the most reliable way to get recent versions of Mono running on stable Linux distros these days is to suck down the source code and compile it.
So here we go with some simple steps (may take a couple of minutes to get through, though):

sudo apt-get install build-essential
tar -xvf mono-3.8.0.tar.bz2
cd mono-3.8.0/
./configure --prefix=/usr/local
sudo make install

This gives us the Mono 3.8.0 CLI:


According to the ASP.NET vNext Home repo on GitHub this should be all we need to get started with the samples. NOT. When we build the source of the samples we get a network-related exception showing up.

The issue is the certificates used for the package sources. The .NET Framework on Windows uses the Windows Certificates store to check whether to accept an SSL certificate from a remote site. In Mono, there is no Windows Certificate store, it has its own store. By default, it is empty and we need to manage the entries ourselves.

sudo $CERTMGR -ssl -m
sudo $CERTMGR -ssl -m
sudo $CERTMGR -ssl -m
sudo $CERTMGR -ssl -m

mozroots --import --sync

After these steps we should be able to build the samples from the ASP.NET vNext Home repo successfully, e.g. the HelloMvc sample.

Running kpm restore looks promising, at least:


When we then try to run the sample with k kestrel (Kestrel is the current dev web server in vNext) we get a wonderfully familiar error:

Object reference not set to an instance of an object.

Hooray!!! Sad smile

After some Googling I found out that the underlying libuv (yes, that same libuv used in node.js) seems to be the problem here. A quick chat with the ASP.NET vNext team reveals it seems like this will be fixed in the future, but there are some more important things to get done by now.

Anyway, I got it finally to work by replacing libuv as suggested here:

ln -sf /usr/lib/ native/darwin/universal/libuv.dylib


When I now run k kestrel again everything is fine:


By default, Kestrel runs on port 5004 – thus opening our browser of choice with http://localhost:5004 gives us the desired result:


Mission accomplished.
Thanks for listening.

BASTA! Spring 2014: Unterlagen

Die BASTA! Spring ist rum, und wieder einmal war es super. Danke an die Organisierer und natürlich an die Teilnehmer!

Hier sind die Folien zu meinen Vorträgen:

Zu den Ganztages-Workshops am Montag und Freitag gibt es naturgemäß keine Folien Winking smile

Für den Freitags-Workshop “End-to-End-Implementierung einer Cross-Platform Modern Business Application” gibt es hier das “laufende” GitHub-Repository, in das Ingo Rammer und ich während des Tages immer hinein ge-psuhed haben.


Viel Spaß!

Hands-On Course: "ASP.NET Web API & SignalR: lightweight web-based architectures for you!"

Come and join me Oct 30-31, 2013 in Oslo for a two days hands-on course organized by ProgramUtvikling.

ASP.NET Web API & SignalR: lightweight web-based architectures for you!"

Time for change: whether it is a classic desktop application, a public or internal web site or a variety of mobile apps - customers and end-users long for multiple ways to access and work with data and processes. Web-based architectures, patterns and techniques can make the life of software architects and developers considerably easier in the face of these requirements.

Let's face it! The current trends and developments especially in the area of mobile platforms & devices and cloud computing will cause a re-thinking in architectural aspects for many software projects and products. If you ignore this today you may be in big trouble tomorrow. How can I reach a plethora of users and client devices? How can I integrate my systems and application parts in a lightweight and interoperable manner? How am I able to push data in near-real-time fashion from my services to my clients?
This course tries to answer these and more questions. Christian Weyer will show you in a pragmatic way how to face the new challenges. See all of this coming to life by using technologies and frameworks like ASP.NET Web API, SignalR, .NET- and HTML5/JavaScript-based clients - mobile or not.


More information at the ProgramUtvikling web site.
See you there!


New ebook chapter published: Properly integrating SignalR hubs with your AngularJS applications

Ingo and I just published a new book chapter of our online (continuously deployed) ebook.
The topic this time is about properly integrating SignalR hubs with your AngularJS applications to realize near realtime push communication. For web browser, desktop or mobile apps.

"Pushing Data: Integrating With ASP.NET SignalR Hubs"

In modern applications the end users want to get their data. They want it now, they want it up-to date. In fact it does not matter whether these are pure web application, native desktop installations or mobile apps: everybody wants his data now!

For .NET-minded developers there are a numbers of options to implement near-real-time push style communication from the server/the services to the clients/consumers. You can choose plain HTTP or the super-new WebSockets features available in .NET 4.5 together with Windows 8 and Windows Server 2012. But the coolest and increasingly popular approach is to use a new framework: ASP.NET SignalR.

While it is not intended- and surely beyond the scope of this ebook - to give an introduction or even deep dive into SignalR, we need to have a look at some concepts and code in order to realize a smooth integration of SignalR and AngularJS.

The final goal of this chapter is to have an AngularJS-style integration of calling and listening to server-side SignalR push services.



Infos zu meinen Sessions & dem Workshop auf der BASTA! Spring 2013

Erst einmal nochmals vielen lieben Dank an alle, die in meine beiden Breakout Sessions und meinen Ganztages-Workshop in Darmstadt gekommen sind!

Da ich ja in meinen beiden Sessions keine "wirklichen" Foliensätze verwendet hatte sondern Demos und Code gezeigt habe, gibt es dieses Mal nix zum Downloaden ;) Beim Workshop war es ja genauso - interaktiv!

Hier aber die versprochenen Links zum Code & den Demos:

Danke und bis bald.


Ain’t no IIS: Self-hosting thinktecture IdentityServer v2 – a simple proof-of-concept

There have been a couple of people asking for a sample how to host the ‚non-visual' parts of thinktecture IdentityServer v2 outside of IIS & ASP.NET. E.g. in a Windows or a Console (no, not really…) application.

Here on GitHub you will find a very simple simple PoC which hosts the OAuth2 token endpoint. That said, it is obviously by no means feature complete.
This endpoint uses ASP.NET Web API and thus self-hosting is kinda piece of cake.

namespace SelfHostConsoleHost
    internal class SelfHostServer
        private HttpSelfHostServer selfHost;

        public IConfigurationRepository ConfigurationRepository { get; set; }

        public async void Start(string baseAddress)
            var httpConfig = new HttpSelfHostConfiguration(baseAddress);

            Database.SetInitializer(new ConfigurationDatabaseInitializer());

            Container.Current = new CompositionContainer(new RepositoryExportProvider());

            ProtocolConfig.RegisterProtocols(httpConfig, ConfigurationRepository);

            selfHost = new HttpSelfHostServer(httpConfig);

            await selfHost.OpenAsync();

        public async void Stop()
            if (selfHost != null)
                await selfHost.CloseAsync();

As said, it just offers one endpoint:

namespace SelfHostConsoleHost
    public class ProtocolConfig
        public static void RegisterProtocols(HttpConfiguration httpConfiguration, IConfigurationRepository configuration)
            // necessary hack for now - until the DI implementation has been changed
            var a = Assembly.Load("Thinktecture.IdentityServer.Protocols");
            var clientAuthConfig = CreateClientAuthConfig();

            httpConfiguration.MessageHandlers.Add(new RequireHttpsHandler());

            if (configuration.OAuth2.Enabled)
                    name: "oauth2token",
                    routeTemplate: Thinktecture.IdentityServer.Endpoints.Paths.OAuth2Token,
                    defaults: new { controller = "OAuth2Token" },
                    constraints: null,
                    handler: new AuthenticationHandler(clientAuthConfig, httpConfiguration)
        public static AuthenticationConfiguration CreateClientAuthConfig()
            var authConfig = new AuthenticationConfiguration
                InheritHostClientIdentity = false,
                DefaultAuthenticationScheme = "Basic",

            // accept arbitrary credentials on basic auth header,
            // validation will be done in the protocol endpoint
            authConfig.AddBasicAuthentication((id, secret) => true, retainPassword: true);
            return authConfig;

Again: the code is here: Self-Hosted IdentityServer v2 PoC

Hope this helps.