https://github.com/pableess/dotnet-localization-ex
Dependency Injection support for aspnetcore culture providers. Also, a port of AspNetCore localization middleware to owin middleware for use in AspNet and Owin applications
https://github.com/pableess/dotnet-localization-ex
aspnetcore dependency-injection dotnet localization owin web
Last synced: 6 months ago
JSON representation
Dependency Injection support for aspnetcore culture providers. Also, a port of AspNetCore localization middleware to owin middleware for use in AspNet and Owin applications
- Host: GitHub
- URL: https://github.com/pableess/dotnet-localization-ex
- Owner: pableess
- License: apache-2.0
- Created: 2020-07-09T02:29:22.000Z (about 5 years ago)
- Default Branch: master
- Last Pushed: 2023-09-30T02:42:57.000Z (about 2 years ago)
- Last Synced: 2025-04-11T03:07:04.930Z (6 months ago)
- Topics: aspnetcore, dependency-injection, dotnet, localization, owin, web
- Language: C#
- Homepage:
- Size: 1.14 MB
- Stars: 1
- Watchers: 1
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# dotnet localization ex
This project contains the following localization enhancements for .NET web applications.
1. Adds dependency injection support for IRequestCultureProviders in AspNetCore
- Why? The AspNetCore Localization middleware allows only the addition of Provider instances to the RequestCultureOptions. For simple providers this is not a problem because the culture can be determined from information on the request. However, more complex custom providers may use external systems like databases, web services, distributed caches etc. This allows the providers to be injected per request, which allows these dependencies to work much better with other Dependency Injection oriented services.
2. Provides a port of AspNetCore localization middleware (Microsoft.AspNetCore.Localization) to owin middleware.
- This allows a similar programming model as AspNetCore localization request providers making it much eaiser to write custom providers that multi-target both Owin and AspNetCore. This support also contains support for dependency injection of the providers.
See https://github.com/dotnet/aspnetcore/tree/master/src/Middleware/Localization for details and documentation.
### Packages
This project provides the following packages:
+ AspNetCore.Localization.DependencyInjection
- Dependency injection support for AspNetCore localization middleware culture providers
+ Owin.Localization
- Port of Microsoft.AspNetCore.Localization middleware to OWIN middleware. Also adds dependency injection support
+ Owin.Localization.Autofac
- Autofac container integration
+ Owin.Localization.Unity
- Unity container integration
### Installing
The packages are available via NuGet.
AspNetCore packages
```
dotnet add package AspNetCore.Localization.DependencyInjection
```
OWIN packages
```
Install-Package Owin.Localization
Install-Package Owin.Localization.Autofac
Install-Package Owin.Localization.Unity
```
# Usage
## AspNetCore
```csharp
// in ConfigureServices
services.AddScoped();
...
// in RequestLocalizationOptions configuration
RequestLocalizationOptions options = new RequestLocalizationOptions().AddInitialInjectedProvider();
```
## OWIN
The owin usage is pretty much the same as using AspNetCore localization middleware. See https://github.com/dotnet/aspnetcore/tree/master/src/Middleware/Localization for details and documentation.
### Dependency Injection with Owin
The dependency injection support with OWIN requires an addition extension method is called on the RequestCultureOptions before calling .AddInjectedProvider() or .AddInitialInjectedProvider()
```csharp
var options = new RequestLocalizationOptions().UseUnityInjection(UnityConfig.Container);
or
var options = new RequestLocalizationOptions().UseAutofacInjection();
```
* the providers also need to be registred as scoped services with the container
### AspNet MVC projects
AspNet MVC projects require a small amount of additonal code to ensure that the assigned culture flows accross from the OWIN middleware to the AspNet request MVC pipeline, because of the way AspNet handles async Owin middleware.
For an AspNet Mvc (.NET Framework 4.7.1 or higher) project, override the Init() of the HttpApplication class as follows:
```csharp
public override void Init()
{
base.Init();
// flow owin culture to every aspnet step
this.OnExecuteRequestStep((ctx, step) =>
{
if (ctx.Items.Contains(RequestLocalizationMiddleware.OwinEnvironmentKey))
ctx.GetOwinContext()?.RestoreCulture();
});
}
```