Below I show how to integrate the WIF authentication setup with your Nancy application - It doesn't take much, but lets
We've all built applications that look like this:
There's a bit of a problem here. What does Exception Reporting have to do with Validation? Or the Home Page? Mostly nothing, other than these classes perform the same kind of function.
much, much nicer to have views, view models, validators, command/query handlers all adjacent together
— Jimmy Bogard (@jbogard) October 2, 2013
Wouldn't it be easier to organize everything by feature instead? Views, View Models, scripts, stylesheets, everything?
This is a cinch in Nancy. First thing you need to do is specify your own view location conventions:
protected override void ConfigureConventions(NancyConventions nancyConventions)
{There are many markdown blogging engines out there such as Calepin, Scriptogram and even WordPress allows you to write blog posts in Markdown but Sandra.Snow tries to add something different. Firstly, it is written in .Net and Nancy, secondly its a static blog generator and finally it supports Git deployment.
Even if you don't want to use Git deployment you can use FTP, its a great tool. To write your blog post in Markdown you need a custom header in your file so it knows some information about your post.
---
layout: post
category: Azure
title: Setting up a ServiceStack Service
---
It then parses this information along with your Markdown into its engine, uses a Markdown view engine to
I don't know about you but all I hear is "ASYNC ALL THE THINGS!", I think this is partly down to its new and shiny and us developers love "the shiny" and partly a lot of the things we do in our applications are I/O based whether that be database or file system.
The problem that comes with the new and shiny bandwagon is you need to understand what you're evangelising. Making asynchronous methods and executing them with no actual reason will not give your codebase any gains and could actually effect your application's performance. There is more depth to that argument but for simplicity just remember this, only use asynchronous methods if you are doing some sort of I/O.
It could also be
This is my second attempt. :)
About a year ago I made an attempt to wire Nancy together with RavenDB and failed miserably. Needed a break from businessy coding last night so I decided to work on something fun instead.
The ability to see what's going on in your application is so important when it comes to performance tuning. Yes, there's that old adage about premature optimization. IMO this phrase is taken out of context. To me 97% of the time means 97% of the code in your face, which is doing stuff in memory. The other 3% of your code is doing I/O of some sort. Minimizing the use of I/O will provide the biggest performance gains for most applications.
In fact having the profiler on here
The talk me writing some Nancy code, talking a lot about Nancy and at the end I have a simple todo application.
Enjoy!
In Part 1 of this series we looked at putting NancyFX as a simple http wrapper in front of YouTrack. Now we're going to make it more RESTful - i.e. we will display the error page to the user agent and include the exception report form on that page.
We will do this by leveraging Nancy's status code handling features. This will allow us to intercept any status code we want and modify the response. Let's start with the view to collect the bug report:
@inherits NancyRazorViewBase<Nancy.Extras.ExceptionReporting.ViewModels.ReportExceptionViewModel>
<!DOCTYPE html>
<html>
<!-- Views/50x.cshtml -->
<head>