Skip to content

Resource sattelite assemblies are not generated when using dotnet cli #25632

New issue
New issue
Closed
Closed
Resource sattelite assemblies are not generated when using dotnet cli#25632
Assignees
joeloff
@orjandh

Description

@orjandh
orjandh
opened on May 25, 2022

Describe the bug

When using the dotnet cli to build or publish a project, the resource sattelite assembly is not produced for the localization resources. However, when building or publishing using Visual Studio, these assemblies are correctly generated.

It may be that something needs to be added to the csproj file for this to work, but in that case it is not documented on https://docs.microsoft.com/en-us/aspnet/core/fundamentals/localization?view=aspnetcore-6.0.

To Reproduce

  1. Create new Asp.Net Core project.
  2. Add Resources/Test.resx and Resources/Test.no.resx files.
  3. Run dotnet build or dotnet publish.
  4. Observe there is no /net6.0/no/project.resources.dll file produced.

Note that this is a minimal reproducible example and this also happens in a project with proper localization setup.

Exceptions (if any)

Further technical details

  • Include the output of dotnet --info
.NET SDK (reflecting any global.json):
 Version:   6.0.300
 Commit:    8473146e7d

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.22000
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\6.0.300\

Host (useful for support):
  Version: 6.0.5
  Commit:  70ae3df4a6

.NET SDKs installed:
  6.1.405 [C:\Program Files\dotnet\sdk]
  7.0.400 [C:\Program Files\dotnet\sdk]
  5.0.408 [C:\Program Files\dotnet\sdk]
  8.0.300 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.All 2.1.30 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.30 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.1.11 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 3.1.25 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 2.1.30 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.1.11 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 3.1.25 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.WindowsDesktop.App 3.1.11 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 3.1.25 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  Microsoft.WindowsDesktop.App 6.0.5 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
  • Visual Studio version: 17.2.2

I used Process Monitor to look into what happens under the hood and it seems that Visual Studio also invoked MSBuild with the following arguments.

/culture:no /out:obj\Release\net6.0\no\project.resources.dll /template:obj\Release\net6.0\project.dll /embed:obj\Release\net6.0\project.Test.no.resources

This did not seem to happen using dotnet build/publish.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions