Meng LinFor whoever is still wondering who Nancy is or what Nancy does, here is a good place to start.
To jump staight into the project as usual, Visual Studio is the place we go. Since I am using Visual Studio 2013, there are some slight changes to the way web application frameworks are created.
Create a web project in Visual Studio 2013
The web forms, MVC and WebAPI frameworks are now in a sub category in Web Application. And I really don’t know what is Microsoft’s plan for this.
But we just need an empty web project to kick off.
The templates in web project
A clean slate is all we have and need, minimum references and a web.config.
The empty web project stucture
Next up, you need to pull in some packages, including ‘Nancy’ and the hosting strategy. Since IIS would still be the quickest way to proceed with this, I would be using it. But that should not stop you from choosing the right or coolest host, like OWIN.
Install-Package Nancy
Install-Package Nancy.Hosting.AspnetAnd then you will find some smurfs have already help you populate the web.config.
Web.config after Nancy is installed
Bear in mind, you will get into trouble if you don’t have the hosting handlers declared in the config.
Till now, you are all good to go. And what a useless blog, right? Hold your horses, where’s always something more…
There is a trap that can easily lure some self-declared smartass in. If you find yourself got shown the following error message, it means that you just created your project using ‘Nancy’, and that is not acceptable!
The bizarre error message
Because namespace clashes with Nancy package, JIT will confuse the object type you try to load is originated from the project you created, and of course it will not find anything!
Since some people just have to learn it the hard way, and googling is not much help in this case, I hope this helps someone out of his misery at least.