Configure ASP.NET Core Sessions with NCache IDistributedCache Provider
You can also use ASP.NET Core sessions with NCache’s IDistributedCache
Provider. ASP.NET Core provides
the AddDistributedMemoryCache() method
to add a default implementation
of IDistributedCache.
However, to utilize NCache as a distributed cache to store ASP.NET Sessions,
NCache provides its own extension method, AddNCacheDistributedCache()
, which
adds NCache as the default distributed cache as an implementation
of IDistributedCache
.
Install NuGet Package
Important
For NCache Version 4.9 SP1 onwards, use ASP.NET Core version 2.1.
Install the NuGet package Alachisoft.NCache.SessionServices to your application by executing the following command in the Package Manager Console:
Install-Package Alachisoft.NCache.SessionServices
Include Namespaces
To utilize the APIs, include the following namespace in your application
in Startup.cs
of your application:
using Alachisoft.NCache.Web.SessionState;
You can configure NCache as a distributed cache for your ASP.NET Core application in two steps:
Configuring services
Adding middleware to the application
Step 1: Configure Services
NCache provides the AddNCacheDistributedCache()
extension method
on IServiceCollection
, which requires just a cache name in NCache and any
optional configurations to store the sessions. The configuration object is the
same as NCache ASP.NET Core Session Provider, which can be initialized
similarly. The configuration can be provided through IOptions initializer as
well.
There are two methods to specify configurations:
- Through your application as
IOptions
or - In JSON format in Appsettings.json of your application.
Method 1: Specifying Configurations In IOptions
The AddNCacheDistributedCache()
method is an extension of the
AddDistributedCache()
method provided by ASP.NET Core. This method takes configuration settings as IOptions
or reads them form the specified .JSON file.
public void ConfigureServices(IServiceCollection services)
{
//Add framework services
services.AddMvc();
services.AddNCacheDistributedCache(configuration =>
{
configuration.CacheName = "myDistributedCache";
configuration.EnableLogs = true;
configuration.ExceptionsEnabled = true;
});
}
Method 2: Specifying Configurations In Appsettings.json
You can either specify the configurations within your application through
IOptions
or in JSON format in Appsettings.json of your application.
{
"AppSettings": {
"SiteTitle": "ASP.NET MVC Music Store",
"CacheDbResults": true,
},
"NCacheSettings": {
"CacheName": "myDistributedCache",
"EnableLogs": "True",
"RequestTimeout": "90"
},
}
Using this method, you can refer to the configurations by providing the name of the section containing JSON format configurations in Appsettings.json:
public void ConfigureServices(IServiceCollection services)
{
//Add framework services
services.AddMvc();
//Add services to the container
services.AddNCacheDistributedCache(Configuration.GetSection("NCacheSettings"));
services.AddSession();
}
Step 2: Add Middleware to Application
Once the distributed cache has been added to the service, sessions can store the
data in NCache. UseSession()
extension method provided by ASP.NET Core will
add the default session middleware to the application but will utilize NCache as
its cache.
This is specific to ASP.NET Core.
Configurations specific to Distributed Caching are explained below:
Refer to the CacheInitParams API Documentation for more detail on properties of this class.
Member | Type | Description | Default Value |
---|---|---|---|
CacheName |
string (required) |
Specifies the name of the cache to be used for caching session. If no cache name is specified, a configuration exception will be thrown. | - |
EnableLogs |
bool (optional) |
If this flag is set, NCache logs all error information. The log files are created in %NCHOME%/log-files/SessionState . |
false |
EnableDetailLogs |
bool (optional) |
When this flag is set, NCache logs all debugging information. The log files are created in %NCHOME%/log-files/SessionState. |
false |
ExceptionsEnabled |
bool (optional) |
Specifies whether exceptions from cache API are propagated to the page output. Setting this flag is especially helpful during development phase of application, since exceptions provide more information about the specific causes of failure. | false |
WriteExceptionsToEventLog |
bool (optional) |
If this flag is set, all the exceptions from cache API are written to event logs. | false |