Skip to main content

Botwin offers an interesting alternative option for routing with ASP.NET Core

NancyFx is a great alternative to ASP.NET if you want to make elegant little web apis like this:

public class SampleModule : Nancy.NancyModule

{

    public SampleModule()

    {

        Get["/"] = _ => "Hello World!";

    }

}

However, it may be that you want a routing style - the way you define your routes - that is like NancyFx BUT you want to use ASP.NET. Botwin is a library that lets you do just that. They say:

This is not a framework, it simply builds on top of Microsoft.AspNetCore.Routing allowing you to have more elegant routing rather than have attribute routing, convention routing, ASP.Net Controllers or IRouteBuilder extensions.

You can plug Botwin into your existing ASP.NET Core application, or you can even add a basic started Botwin app to "dotnet new" like this:

C:\botwinexample> dotnet new -i BotwinTemplate

C:\botwinexample> dotnet new botwin -n MyBotwinApp

C:\botwinexample> dir

10/11/2017  10:14 PM               284 HomeModule.cs

10/11/2017  10:14 PM               470 MyBotwinApp.csproj

10/11/2017  10:14 PM               421 Program.cs

10/11/2017  10:14 PM               408 Startup.cs

               4 File(s)          1,583 bytes

You add Botwin as a service to your ASP.NET Core app:

public class Startup

{
    public void ConfigureServices(IServiceCollection services)
    {
        services.AddBotwin();
    }
        
    public void Configure(IApplicationBuilder app)
    {
        app.UseBotwin();
    }

}

And then add 'Modules' like this:

namespace MyBotwinApp
{
    using Botwin;
    using Microsoft.AspNetCore.Http;
    public class HomeModule : BotwinModule
    {
        public HomeModule()
        {
            Get("/", async(req, res, routeData) => await res.WriteAsync("Hello from Botwin!"));
        }
    }
}

That's a hello world. Let's try something more interesting. You can have Before and After hooks like this:

public class HooksModule : BotwinModule

{

    public HooksModule()

    {

        this.Before = async (ctx) =>

        {

            ctx.Response.StatusCode = 402;

            await ctx.Response.WriteAsync("Pay up you filthy animal");

            return false;

        };


        this.Get("/hooks", async (req, res, routeData) => await res.WriteAsync("Can't catch me here"));


        this.After = async (ctx) => await ctx.Response.WriteAsync("Don't forget you owe me big bucks!");

    }

}

Here's a more complex example. See how they do a BindAndValidate in the Post() where they check for a valid Actor before working with it.

public class ActorsModule : BotwinModule

{

    public ActorsModule(IActorProvider actorProvider)

    {

    this.Get("/actors", async (req, res, routeData) =>

    {

        var people = actorProvider.Get();

        await res.AsJson(people);

    });


    this.Get("/actors/{id:int}", async (req, res, routeData) =>

    {

        var person = actorProvider.Get(routeData.As<int>("id"));

        await res.Negotiate(person);

    });


    this.Put("/actors/{id:int}", async (req, res, routeData) =>

    {

        var result = req.BindAndValidate<Actor>();


        if (!result.ValidationResult.IsValid)

        {

            res.StatusCode = 422;

            await res.Negotiate(result.ValidationResult.GetFormattedErrors());

            return;

        }


        //Update the user in your database


        res.StatusCode = 204;

    });


    this.Post("/actors", async (req, res, routeData) =>

    {

        var result = req.BindAndValidate<Actor>();


        if (!result.ValidationResult.IsValid)

        {

            res.StatusCode = 422;

            await res.Negotiate(result.ValidationResult.GetFormattedErrors());

            return;

        }


        //Save the user in your database

        res.StatusCode = 201;

        await res.Negotiate(result.Data);

    });

}

What do you think about the choices you have with ASP.NET Core? Some people feel like the amount of plugability is overwhelming, but I find the flexibility heartening. Go check out Botwin and, hopefully, help out and contribute to open source!

Sponsor: Get the latest JetBrains Rider preview for .NET Core 2.0 support, Value Tracking and Call Tracking, MSTest runner, new code inspections and refactorings, and the Parallel Stacks view in debugger.


© 2017 Scott Hanselman. All rights reserved.
     


from Scott Hanselman's Blog http://feeds.hanselman.com/~/468631182/0/scotthanselman~Botwin-offers-an-interesting-alternative-option-for-routing-with-ASPNET-Core.aspx
Labels:

Comments

Post a Comment

Popular posts from this blog

Rail Fence Cipher Program in C and C++[Encryption & Decryption]

Here you will get rail fence cipher program in C and C++ for encryption and decryption. It is a kind of transposition cipher which is also known as zigzag cipher. Below is an example. Here Key = 3. For encryption we write the message diagonally in zigzag form in a matrix having total rows = key and total columns = message length. Then read the matrix row wise horizontally to get encrypted message. Rail Fence Cipher Program in C #include<stdio.h> #include<string.h> void encryptMsg(char msg[], int key){ int msgLen = strlen(msg), i, j, k = -1, row = 0, col = 0; char railMatrix[key][msgLen]; for(i = 0; i < key; ++i) for(j = 0; j < msgLen; ++j) railMatrix[i][j] = '\n'; for(i = 0; i < msgLen; ++i){ railMatrix[row][col++] = msg[i]; if(row == 0 || row == key-1) k= k * (-1); row = row + k; } printf("\nEncrypted Message: "); for(i = 0; i < key; ++i) f...
3 comments
Read more

Data Encryption Standard (DES) Algorithm

Data Encryption Standard is a symmetric-key algorithm for the encrypting the data. It comes under block cipher algorithm which follows Feistel structure. Here is the block diagram of Data Encryption Standard. Fig1: DES Algorithm Block Diagram [Image Source: Cryptography and Network Security Principles and Practices 4 th Ed by William Stallings] Explanation for above diagram: Each character of plain text converted into binary format. Every time we take 64 bits from that and give as input to DES algorithm, then it processed through 16 rounds and then converted to cipher text. Initial Permutation: 64 bit plain text goes under initial permutation and then given to round 1. Since initial permutation step receiving 64 bits, it contains an 1×64 matrix which contains numbers from 1 to 64 but in shuffled order. After that, we arrange our original 64 bit text in the order mentioned in that matrix. [You can see the matrix in below code] After initial permutation, 64 bit text passed throug...
Post a Comment
Read more

Experimental: Reducing the size of .NET Core applications with Mono's Linker

The .NET team has built a linker to reduce the size of .NET Core applications. It is built on top of the excellent and battle-tested mono linker . The Xamarin tools also use this linker so it makes sense to try it out and perhaps use it everywhere! "In trivial cases, the linker can reduce the size of applications by 50%. The size wins may be more favorable or more moderate for larger applications. The linker removes code in your application and dependent libraries that are not reached by any code paths. It is effectively an application-specific dead code analysis ." - Using the .NET IL Linker I recently updated a 15 year old .NET 1.1 application to cross-platform .NET Core 2.0 so I thought I'd try this experimental linker on it and see the results. The linker is a tool one can use to only ship the minimal possible IL code and metadata that a set of programs might require to run as opposed to the full libraries. It is used by the various Xamarin products to extract...
Post a Comment
Read more