title: ASP.NET Core resource files without a culture in the file name, why not?
body: <p>Quote from <a href="https://docs.microsoft.com/en-us/aspnet/core/fundamentals/localization?view=aspnetcore-2.1#generate-resource-files-with-visual-studio-1" rel="nofollow noreferrer">ASP.NET Microsoft Docs</a></p>
  <blockquote>
  <p>If you create a resource file in Visual Studio without a culture in
  the file name (for example, Welcome.resx), Visual Studio will create a
  C# class with a property for each string. <strong>That's usually not what you</strong>
  <strong>want with ASP.NET Core</strong>. You typically don't have a default .resx
  resource file (a .resx file without the culture name). We suggest you
  create the .resx file with a culture name (for example
  Welcome.fr.resx). When you create a .resx file with a culture name,
  Visual Studio won't generate the class file.</p>
  </blockquote>
  <p>IMO the doc doesn't explain clearly why having a C# class with property names is NOT what you want with ASP.NET Core. It seems more convenient to use a property in a static class than to have to inject IStringLocalizer everywhere. Can anyone please elaborate??</p>