This repository has been archived by the owner on Jan 24, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Statement on strong naming
phillip-haydon edited this page Oct 9, 2014
·
2 revisions
Nancy is not currently signed with a strong name and it never will be.
The topic of strong naming in .NET OSS has been fully debated elsewhere so arguments for and against are not going to be rehashed here.
The fact that the upcoming AspNet vNext / CoreCLR from Microsoft doesn't support nor use strong naming means that strong naming is effectively dead for server side .NET development.
If you really require strong naming, Nancy is available with a very permissive licence so you are free to sign your own clone / fork.
- 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