You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a project defines <EmbeddedResourceUseDependentUponConvention>true</EmbeddedResourceUseDependentUponConvention>, and a SomeName.cs file has a matching SomeName.resx file, one expects things to go smoothly.
It may occur that a type is added at the top of the SomeName.cs file, and the resource gets renamed by that fact.
res1111: project defines EmbeddedResourceUseDependentUponConvention, and file SomeName.cs and SomeName.resx were matched, although the first type defined in SomeName.cs doesn't match SomeName, the embedded resource may be generated under the wrong name.
The text was updated successfully, but these errors were encountered:
When a project defines
<EmbeddedResourceUseDependentUponConvention>true</EmbeddedResourceUseDependentUponConvention>
, and a SomeName.cs file has a matching SomeName.resx file, one expects things to go smoothly.It may occur that a type is added at the top of the SomeName.cs file, and the resource gets renamed by that fact.
I believe generating a warning in this case, pointing to the documentation (https://learn.microsoft.com/en-us/dotnet/core/project-sdk/msbuild-props#embeddedresourceusedependentuponconvention) would alleviate the troubleshooting steps.
Describe the solution you'd like
The text was updated successfully, but these errors were encountered: