dotnet build fails to manage embedded resources
See original GitHub issueSteps to reproduce
Create a new class library project (under VS2017, last update) Add a Foo.resx file (with designer) Add a Foo.fr.resx file Go to the project directory Execute dotnet build
Expected behavior
The project must be built without error
Actual behavior
C:\Program Files\dotnet\sdk\1.0.0\Microsoft.Common.CurrentVersion.targets(4072,5): error MSB3030: Could not copy the file “obj\Debug\fr\ProjectName.resources.dll” because it was not found. [C:\Projects\SolutionName\ProjectName\ProjectName.csproj]
Environment data
dotnet --info
output:
Runtime Environment: OS Name: Windows OS Version: 10.0.14393 OS Platform: Windows RID: win10-x64 Base Path: C:\Program Files\dotnet\sdk\1.0.0 (tested with 1.0.1 as well)
Issue Analytics
- State:
- Created 7 years ago
- Reactions:4
- Comments:15 (3 by maintainers)
Top Results From Across the Web
dotnet build fails to manage embedded resources #7963
If you move your resource files to a class library with the new csproj format, this might be a viable workaround.
Read more >dotnet build fails to manage embedded resources
As Visual Studio build works ok, it appears that Visual Studio uses different build process then dotnet build. Firstly, execute msbuild for ...
Read more >MSBuild reference for .NET SDK projects
Reference for the MSBuild properties and items that are understood by the .NET SDK.
Read more >NET project SDK overview
The .NET SDK includes 'EmbeddedResource' items from your project directory by default. You can either remove these items from your project file, ...
Read more >Retrieve resources in .NET apps
Retrieve resources from assemblies. The ResourceManager class provides access to resources at run time. You use the ResourceManager.GetString ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The originally reported issue persists in dotnet 2.0.0. In our case, I’m stuck using the old csproj format because Telerik Reporting tools don’t yet support the new project file format.
I’d like to request that this issue be reopened.
@mbp what do you mean with this? Could you give me an example please?