Nuget not including RESX files in packages

Dec 14, 2011 at 11:51 PM
Edited Dec 14, 2011 at 11:52 PM

If we have two RESX files in our project, for instance Resources/Locals.resx and Resources/Locals.en-UK.resx with their corresponding resx.cs autogenerated files then when packaging Nuget will only pick up the Locals.resx and its code generated file and, as such, when including this package in other projects, only the resource strings from Locals.resx will be available to that project.

What can be done here, is this ever going to be supported? I've found another question on this topic having exact same issues.

Dec 15, 2011 at 3:33 AM

can you describe your project directory structure and what command you ran to create the package?

Dec 15, 2011 at 9:13 AM

Resources directory is at the root of the project that we are packaging. The RESX files are marked as Embedded Resource. As such, they work fine in this project but in the package they are missing - the default one (the one without the culture identifier) does get compiled and it is available to the package users but that of course is not everything we want. We want the alternate RESX files for other cultures included also.

the command is:

nuget pack -Prop Configuration=Release

Dec 16, 2011 at 1:10 AM

Can you create a bug and attach the zip of your project? Feel free to remove any proprietary information and just leave the resx files. Thanks