Asp.Net Core localization not working using VSCode

Question

I'm using VSCode to create an Asp.Net Core API. I'm trying all day to figure out how to make localization to work but with no results. When I do the exact same thing in Visual Studio 2015 Community Edition everything works fine. But not with VSCode...

So I created the following super simple project with the simplest structure in VSCode:

I'm using Postman to send an Http Get on http://localhost:5000/app. The result json is this:

{
  "name": "test_value",
  "value": "test_value",
  "resourceNotFound": true
}

The VS Community project is simillar:

The result json is this (the right one):

{
  "name": "test_value",
  "value": "This is the test value!",
  "resourceNotFound": false
}

Could anyone figure out why this is not working inside from VSCode? In both cases I am running Kestrel, both projects complile fine, both have the exact same following source code. The problem is there in a windows and also in a linux development enviroment. This drives me crazy!

project.json

{
  "dependencies": {
    "Microsoft.NETCore.App": {
      "version": "1.0.1",
      "type": "platform"
    },
    "Microsoft.AspNetCore.Server.Kestrel": "1.0.1",
    "Microsoft.AspNetCore.Mvc": "1.0.1"
  },
  "frameworks": {
    "netcoreapp1.0": {
      "imports": [
        "dotnet5.6"
      ]
    }
  },
  "buildOptions": {
    "emitEntryPoint": true,
    "preserveCompilationContext": true
  },
  "runtimeOptions": {
    "configProperties": {
      "System.GC.Server": true
    }
  },
  "tooling": {
    "defaultNamespace": "Trans"
  }
}

Program.cs

using System.IO;
using Microsoft.AspNetCore.Hosting;

namespace Trans
{
    public class Program
    {
        public static void Main(string[] args)
        {
            var host = new WebHostBuilder()
                .UseKestrel()
                .UseContentRoot(Directory.GetCurrentDirectory())
                .UseStartup()
                .Build();

            host.Run();
        }
    }
}

Startup.cs

using Microsoft.AspNetCore.Builder;
using Microsoft.Extensions.DependencyInjection;

namespace Trans
{
    public class Startup
    {
        public void ConfigureServices(IServiceCollection services)
        {
            services.AddLocalization(options => options.ResourcesPath = "Resources");
            services.AddMvc();
        }

        public void Configure(IApplicationBuilder app)
        {
            app.UseMvc();
        }
    }
}

AppController.cs

using Microsoft.AspNetCore.Mvc;
using Microsoft.Extensions.Localization;

namespace Trans.Controllers
{
    [Route("app")]
    public class AppController : Controller
    {
        IStringLocalizer _localizer;

        public AppController(IStringLocalizer localizer)
        {
            _localizer = localizer;
        }

        [HttpGet]
        public IActionResult Get()
        {
            return Json(_localizer["test_value"]);
        }
    }
}

Controllers.AppController.resx



  
  
    
    
      
        
          
            
              
                
              
              
              
              
              
            
          
          
            
              
              
            
          
          
            
              
                
                
              
              
              
              
              
            
          
          
            
              
                
              
              
            
          
        
      
    
  
  
    text/microsoft-resx
  
  
    2.0
  
  
    System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
  
  
    System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
  
  
    This is the test value!

pavlospap · Accepted Answer

I finally figured this out!

The problem was that the name of the project's folder was different than the root namespace! The project's folder name was something like my-app. That was the name I picked for my Github repository. So my-app was the name of the project's folder that was created when I cloned the repository and, also, the name of the produced assembly (my-app.dll) which inherits it's name from the project folder. However, the root namespace that I picked was MyApp.

The reason I had no problem with VS Community was that when I created the project I picked for the solution the name MyApp and so that was the project's folder name and the root namespace too!

I am not sure if the actual problem is the folder's name or the name of the produced assembly. I guess it's the assembly name.

So, bottomline, for the localization to work the project's folder name (that is the name of the produced assembly too) must be the same with the root namespace!

Asp.Net Core localization not working using VSCode

Answers (1)

Related Questions