-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Nancy v2 Upgrade Notes
In Nancy 1.x you had the option to turn a route into async by setting the runAsync
property to true
. In 2.x all routes are now async, and as such the method signature has changed:
Get["/"] = (parameters, ct) => {
return <your async operation>
}
parameters
is, as before, a DynamicDictionary
instance that contains all route parameters. The new ct
parameter is a CancellationToken
.
ℹ️ To ease the transition, 2.0-alpha contains a class called
LegacyNancyModule
which exposes the same route declaration syntax as before. Inherit from this to help ease the transition to async routes. However, please note that this is marked as obsolete and will be removed in a later update (undecided which).
Most of the members in StaticConfiguration
have been moved out and migrated over to the new Configuration API.
The following settings have been migrated
- Json
- Xml
- View
- Tracing
- Routing
In the Nancy 1.x versions, Context.CurrentUser
was an IUserIdentity
, you could add properties to your implementation and then access these properties that were not on the interface by casting. E.g. var customerId = ((MyUser) Context.CurrentUser).CustomerId;
In v2.x of Nancy, Context.CurrentUser
is a ClaimsPrincipal
. By default this contains an list of claims that the user has. So to get a name value for example you would have do something like Context.CurrentUser.FindFirst(ClaimTypes.Name).Value
.
In Nancy v2.x there is a whole new configuration API. This is now handled in the bootstrapper by overriding the Configure
method. For diagnostics, you can use it like this:
public override void Configure(Nancy.Configuration.INancyEnvironment environment)
{
environment.Diagnostics(password: "pa55w0rd!");
}
This has a different signature but now takes in an ITypeCatalog
argument. If you are using the WithOverrides
API this should still work, you just need to change the method signature:
protected override Func<ITypeCatalog, NancyInternalConfiguration> InternalConfiguration
{
get
{
return NancyInternalConfiguration
.WithOverrides(x =>
x.ResponseProcessors = new[] { typeof(JsonProcessor) });
}
}
This namespace has been renamed to Nancy.Serialization.ServiceStack
.
One of the arguments was previously an array of ISerializer
, this is now an ISerializerFactory
.
As of 2.x, the Nancy.ViewEngines.Razor
engine uses Roslyn internally to compile views. Unfortunately the Nuget for Nancy.ViewEngines.Razor
(2.0-alpha) is missing a couple of dependencies which are needed to compile and render views. For the time being you will need to explicitly install these packages yourself (in the presented order):
Install-Package Microsoft.Net.Compilers -Versions 1.1.1
Install-Package Microsoft.CodeDom.Providers.DotNetCompilerPlatform -Version 1.0.1
Install-Package Microsoft.CodeAnalysis.CSharp -Version 1.1.1
If you get any runtime exceptions, please check your config file for any invalid assembly binding redirects.
- Introduction
- Exploring the Nancy module
- Routing
- Taking a look at the DynamicDictionary
- Async
- View Engines
- Using Models
- Managing static content
- Authentication
- Lifecycle of a Nancy Application
- Bootstrapper
- Adding a custom FavIcon
- Diagnostics
- Generating a custom error page
- Localization
- SSL Behind Proxy
- Testing your application
- The cryptography helpers
- Validation
- Hosting Nancy with ASP.NET
- Hosting Nancy with WCF
- Hosting Nancy with Azure
- Hosting Nancy with Suave.IO
- Hosting Nancy with OWIN
- Hosting Nancy with Umbraco
- Hosting Nancy with Nginx on Ubuntu
- Hosting Nancy with FastCgi
- Self Hosting Nancy
- Implementing a Host
- Accessing the client certificate when using SSL
- Running Nancy on your Raspberry Pi
- Running Nancy with ASP.NET Core 3.1