While this topic dives into some of the more general options available in
JasperRegistry, check out these topics for deeper
discussions of setting up Jasper applications:
- <[linkto:documentation/bootstrapping/configuration]> for integrating with Configuration in .Net Core and Jasper's strong-typed configuration Settings model
- <[linkto:documentation/bootstrapping/aspnetcore]> to make Jasper act as just a citizen in the greater ASP.Net Core ecosystem
- <[linkto:documentation/http]> for information on configuring ASP.Net Core middleware and customizing Jasper's HTTP service support
- <[linkto:documentation/messaging]> for setting up messaging receivers, subscriptions, and publishing in your application
By default, Jasper derives a descriptive ServiceName for your application by taking the class name of your
JasperRegistry and stripping off
any "JasperRegistry" or "Registry" suffix. For diagnostic purposes you may want to override the service name like so:
Jasper exposes the ASP.Net Core Environment name with this usage:
You can use the
EnvironmentName property within the constructor function of your
JasperRegistry to do conditional configuration based on environment just like you would in an ASP.Net Core application:
You can also access the current application directory and other information from the
IHostedEnvironment property on the context object in both signatures.
Like most application frameworks in .Net, Jasper uses an IoC container to do basic composition within its runtime pipeline. You can add your own registrations to the application container directly in your
See <[linkto:documentation/ioc]> for a lot more information about how Jasper uses an IoC container.
Jasper comes with its own extensibility model based on an interface called
IJasperExtension. A custom extension
might look something like this:
The syntax in
JasperRegistry to apply that extension is shown below:
See <[linkto:documentation/extensions]> for more information on building, using, and auto-discovering Jasper extensions.