bionmighty.blogg.se - .net core localizer view

.net core localizer view how to#
.net core localizer view code#

Use AppText app settings of example_app for ASP.NET Core request localization Create empty items in AppText for all keys that are not found The ID of the app that we created just before Add AppText implementation for ASP.NET Core localization Public IConfiguration Configuration, "en") Public Startup(IConfiguration configuration, IHostEnvironment env) We also inject IHostEnvironment via the constructor because we need it to resolve the physical folder where the AppText is running for its file storage: public class Startup Then change Startup.cs to enable AppText localization.

For ASP.NET Core localization we need the AppText.Localization package and we also need the AppText.AdminApp package enable management of the text resources.Īdd the NuGet packages: dotnet add package AppText.Localization dotnet add package AppText.AdminApp Just two NuGet packages and a little bit of configuration in the Startup.cs file.

Enable dynamic localization with AppTextĪdding AppText for localization is very easy. This is the main reason why AppText was created, to enable changing text resources in deployed applications without having to build and deploy new versions. There is no way to change resources in an already deployed application. Look here for more information.Ī major drawback of this localization method is that every little change requires a new build of your application. In this post, we won’t get into detail how this works. Adding these to Startup.cs fixes the error message: public void ConfigureServices(IServiceCollection services) This is because we didn’t register the localization services in Startup.cs yet. Now, when running the application again, we get an error message that IStringLocalizer can not be resolved: ViewData = _localizer īrand title in Views/Shared/_Layout.cshtml: IViewLocalizer - heading in Views/Home/Index.cshtml: IViewLocalizer about building Web apps with ASP.NET Core. Public HomeController(ILogger logger, IStringLocalizer localizer) Private readonly IStringLocalizer _localizer Page title in Controllers/HomeController.cs: public class HomeController : Controller The page title is localized via the controller with the IStringLocalizer and the website brand title and the page heading directly in the Razor view with the IViewLocalizer.

The website brand title (AspNetCoreMvcExample)ĪSP.NET Core has standard components for localization and in our example we’ll start with these standard components.

Highlighted above are three text resources that we’re going to localize: Opening the browser and navigating to shows the default home page of an ASP.NET Core MVC project: Let’s begin with the empty MVC app: dotnet new mvc We’re going to create an example ASP.NET Core MVC application and replace static text with localized resources from AppText. All feedback is very much appreciated! Setup example application

.net core localizer view code#

The final code for this post is also on GitHub in the /examples/AspNetCoreMvcExample folder.

.net core localizer view how to#

This post shows how to enable localization in ASP.NET Core applications with AppText. More information about AppText can be found at the web site ( ) and GitHub ( ).īecause it’s still early in its development, documentation is a bit sparse and we’re still figuring out some usage scenarios, but there is one area that already works great (I think) and that’s the integration with the ASP.NET Core Localization components.

It runs on the Microsoft ASP.NET Core platform where it’s installed as add-on to ASP.NET Core web applications via NuGet packages. AppText is a simple Open Source Content Management System (CMS) that I started as a side project to make it easier for our customers and ourselves to do small textual changes in applications without having to build and release new versions of the applications all the time.