Strongly Typed Resources Causing Problems?

Question

In the middle of some refactoring and I've moved a resources file from one project to another. I think I clicked a warning telling me to Strongly type the resource file at one point and now I'm getting:

Could not find any resources appropriate for the specified culture or the neutral culture. Make sure "MyProject.Common.ResourceManagement.resources" was correctly embedded or linked into assembly "MyProject.Common" at compile time, or that all the satellite assemblies required are loadable and fully signed.

Which is from a MissingManifestResourceException I beleive.

http://msdn.microsoft.com/en-us/library/system.resources.missingmanifestresourceexception.aspx

I've looked up a couple of the solutions:

But none of them seem relevant to my situation.

Any ideas? This has been bugging me for a few days now.

Am I doing something stupid?

What was your plan with the refactoring? Creating a common resource DLL with public resources to be referred to by other projects in your solution? — Alan
No, this has just happened as a side effect. A lot of the classes that used the resources file had moved into the Common project so I figured it made more sense there. — Rob Stevenson-Leggett

baretta baretta · Accepted Answer · 2008-11-06T11:08:08

Are you sure these resource files are embedded into the assembly? Maybe you've lost the "Embedded Resource" settings as you moved the files. Further, the resource names may have changed. The fully qualified name of a resource is AssemblyName + physical subfolder(s) + resource name

Strongly Typed Resources Causing Problems?

2 Answers