Could not find any resources appropriate for the specified culture or the neutral culture

Question

I have two ASP.NET Web projects (ProjectA and ProjectB). When class in ProjectA is instantiating a class of ProjectB which uses a resource file Blah.resx, I get this error:

An exception of type 'System.Resources.MissingManifestResourceException' occurred in mscorlib.dll but was not handled in user code.

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

Whats causing this?

There is an article on Microsoft's site about this http://support.microsoft.com/kb/318603 which suggests:

To resolve this problem, move all of the other class definitions so that they appear after the form's class definition.

This is a solution for Windows Forms project, I'm not sure if that also applies to Web projects.

What type of projects are these? 2 websites? 1 website, 1 class library? — Ruddy, Jan 26 '10 at 01:58
This [answer](http://stackoverflow.com/a/11384535/1257607) solved the problem for me! `GetGlobalResourceObject` — DanielV, Apr 20 '15 at 19:47

CFinck · Answer 1 · 2023-05-26T19:09:07.533

282

I just hit this same exception in a WPF project. The issue occurred within an assembly that we recently moved to another namespace (ProblemAssembly.Support to ProblemAssembly.Controls). The exception was happening when trying to access resources from a second resource file that exists in the assembly.

Turns out the additional resource file did not properly move references from the old namespace name to the new namespace name.

In the designer.cs for the resource file, there is a static property to get the ResourceManager. Within that getter, the string was still referring the old namespace. Once correcting it to the new namespace, the problem was resolved:

global::System.Resources.ResourceManager temp = 
     new global::System.Resources.ResourceManager(
          "ProblemAssembly.Support.Properties.Stuff", typeof(Stuff).Assembly);

last line should have been:

global::System.Resources.ResourceManager temp = 
     new global::System.Resources.ResourceManager(
          "ProblemAssembly.Controls.Properties.Stuff", typeof(Stuff).Assembly);

edited May 26 '23 at 19:09

answered May 11 '11 at 19:06

CFinck

3,171
1
16
10

1

link: MSDN documentation for the [ResourceManager](http://msdn.microsoft.com/en-us/library/system.resources.resourcemanager.aspx) class. – Boinst Jul 26 '12 at 02:29
4

Thanks it helped me solve this issue. One can also delete the designer file, then open then save the resx file to regenerate the designer file correctly. – Serge Oct 28 '13 at 08:53
1

I had the same issue and this was the answer I was looking for. Sadly it doesn't appear at compile time :-( Thanks – 0xC0DED00D Jan 11 '14 at 21:16
1

One more thing to note: this temp string does not get updated if you set a custom namespace to use under resource file properties (that's where you also choose a custom tool) – mare Sep 07 '14 at 11:03
One last thing to note: Resharper will not update this namespace reference when using it's 'Adjust Namespaces' command on a resx file (at least as of 8.2.1000) – Robert Petz Oct 15 '14 at 18:01
I have the same problem but cant fix it :( http://stackoverflow.com/questions/29490866/global-resource-file-asp-net – Waqar Ahmed Apr 08 '15 at 04:32
2

thanks had this problem too but it was because I added a subfolder with the same name as the last part of the namespace of the project so it was looking for project.folder.folder.class instead of project.folder.class. I moved it to the root and now it lines up and works! – SelAromDotNet Aug 21 '15 at 22:37
In my case it was an icon which wasn't handled correctly, but this answer gave me enough clues to know what to look for and find the issue. I just removed the icon and added it back. Not sure how to actually fix it. – Owen Ivory Sep 19 '16 at 17:43
By change in namespace it works, Thank you – Milind Morey Dec 07 '22 at 09:05

score 127 · Answer 2 · edited Aug 09 '22 at 08:36

127

I solved the problem like this:

Right click on your ResourceFile and then "Properties"
Change the "Build Action" property Compile to "Embedded Resource"
Then build and run

It works perfectly.

edited Aug 09 '22 at 08:36

Majid Basirati

2,665
3
24
46

answered Aug 08 '12 at 12:42

Sibi Elango

1,287
1
8
2

@sibi Elango I right click on my ResourceFile but can't find the Build Action part. – S5498658 Jun 23 '15 at 17:22
1

@S5498658 If you don't see this in the context menu (right click), look in the Properties panel (usually located below the solution explorer). – defines Aug 07 '15 at 16:56
Its build action but still not working. Also I checked the directory and directory is the same under properties. – albatross Nov 24 '15 at 08:28
6

It would be great if the answer explains why this solution works. – Luis Teijon Jun 30 '17 at 18:30
For me I just did a rebuild and that fixed my issue. But I also r-clicked on my resource file --> Properties and verified "Build Action" to show "Embedded Resource". Worked fine. – John Waclawski Aug 14 '18 at 17:22
For me, the issue was my ResourceFile wasn't being included in the project (imported form). This works because the second half of this error message says "Make sure "Form1.resources" was correctly embedded or linked into assembly "ProjectA" at compile time, or that all the satellite assemblies required are loadable and fully signed." and these resource files weren't being embedded because their build action didn't say to embed them (or in my case, to include them). – Amanda Jan 28 '21 at 23:48

Mark Lakata · Answer 3 · 2015-02-03T18:49:23.833

When I tried sharing a resource.resx file from one C# project with another C# project, I got this problem. The suggestion on moving the Form class to the beginning of its file wasn't appropriate. This is how I solved it. You essentially use a link from the second project to the first, then enable regeneration of the resource.designer.cs file.

Delete the second project's Properties/Resources.resx file
Add the first project's Properties/Resources.resx file as a LINK to the Properties folder in the second project. Don't add it to the root level of the project.
Don't add the first project's Properties/Resources.designer.cs!
On the properties of the second project's Resources.resx, add ResXFileCodeGenerator as the CustomTool
Right click on the Resources.resx and select "Run Custom Tool". This will generate a new designer.cs file.

Note: I would avoid editing the resource.designer.cs file, as this is autogenerated.

This only works if you do not have a Resources.resx file already in the target/second project that you want to keep. — Joniale, Mar 07 '23 at 13:24

score 18 · Answer 4 · answered Apr 07 '16 at 18:20

18

In my case a series of badly thought global text replacements had inadvertently changed this line in the resource designer cs file.

Since the namespace in that argument did not match the namespace of the class anymore, the application got confused at run time.

Check that the namespace of the designer matches the string argument in that line.

answered Apr 07 '16 at 18:20

cockypup

1,013
1
10
24

Same here: it happened after migrating from PCL to .NET Standard, when i created a temporary project and namespace, into which i copied all portable files, removed the portable project and reverted the namespace back to the original, this line still contained the temporary namespace from the migration process. – Zerga Oct 02 '18 at 08:09
1

my case: I create .resx file with Rider with '.' (dot) in name, generator autoreplace '.' to '_' in RecourceManager parameter. 'Could not find the resource' as a result – barsmaga May 27 '21 at 16:54
Had same issue using Rider – Korfu Jul 01 '22 at 09:58

Soheil Alizadeh · Answer 5 · 2022-04-04T08:57:57.533

16

For users who facing this isssue in .NET Core 3.0, this could be related to a breaking change that made in .NET Core 3.0, to resolve it just set EmbeddedResourceUseDependentUponConvention to false in your project csproj:

<PropertyGroup>
  <EmbeddedResourceUseDependentUponConvention>true</EmbeddedResourceUseDependentUponConvention>
</PropertyGroup>

edited Apr 04 '22 at 08:57

answered May 19 '20 at 12:36

Soheil Alizadeh

2,936
11
29
56

4

This was the solution for me, except my problem was with a Winforms project that I'd ported to an SDK-style project. In this case, I had to set `EmbeddedResourceUseDependentUponConvention` to **`true`** rather than `false`. – Matthew Watson Jun 11 '21 at 14:16
@MatthewWatson Thank you! That was the solution! – Shahin Dohan Mar 31 '22 at 17:01
This solved the problem for me when referencing a private NuGet package containing a project in the SDK style. It seems that the resources are named according to the filename instead of the class name when it is an SDK-style project where as in the old format only the class name and namespace gets used. – Jonas Marty Feb 15 '23 at 14:07

score 15 · Answer 6 · edited Dec 09 '16 at 11:46

15

It happens because the *.resх is excluded from migration.

Right click on your ResourceFile
Click on the menu item "Include in project"

edited Dec 09 '16 at 11:46

Matteo Baldi

5,613
10
39
51

answered Dec 09 '16 at 11:25

user1919359

161
1
4

2

This fixed it for me. Normally the resx file is added automatically. I did a merge where I had to change the project file and add the migrations manually, so maybe that had something to do with it – smarty Feb 20 '18 at 15:22
Worked for me. I have to add all *.resx files of each migration. Thanks – m.rufca Apr 08 '19 at 00:37

score 11 · Answer 7 · answered Sep 30 '13 at 22:45

11

I found that deleting the designer.cs file, excluding the resx file from the project and then re-including it often fixed this kind of issue, following a namespace refactoring (as per CFinck's answer)

answered Sep 30 '13 at 22:45

Stephen Drew

1,415
19
31

This is what did it for me! (tried CFinck's answer as it seemed relevant, but it didn't work) – winwaed Jan 11 '15 at 20:48
Indeed one of the fastest solutions – Lorenz Lo Sauer Jun 24 '16 at 07:45

score 11 · Answer 8 · answered Aug 17 '18 at 11:33

No-one seems to have mentioned this solution. Obvious really - but tripped me over for a moment...

The default access modifier for a new resources file is Internal (or Friend in VB.Net.) Make sure you change this to Public

(in the resx designer there is a dropdown at the top for the access modifier)

score 7 · Answer 9 · answered Apr 28 '18 at 17:53

I resolved this by going to the project where my resources file was saved, scrolling down to its ItemGroup and adding a logical name that corresponded to the path the compiler expected.

My EmbeddedResource looked like this:

   <ItemGroup>
    <EmbeddedResource Update="Properties\TextResources.resx">
      <Generator>PublicResXFileCodeGenerator</Generator>
      <LastGenOutput>TextResources.Designer.cs</LastGenOutput>
    </EmbeddedResource>
  </ItemGroup>

Now it looks like this

  <ItemGroup>
    <EmbeddedResource Update="Properties\TextResources.resx">
      <Generator>PublicResXFileCodeGenerator</Generator>
      <LastGenOutput>TextResources.Designer.cs</LastGenOutput>
      <LogicalName>MyProject.Properties.Resources.resources</LogicalName>
    </EmbeddedResource>
  </ItemGroup>

score 5 · Answer 10 · edited Dec 05 '20 at 11:49

5

Sibi Elangos's answer alone was not sufficient for me, so I had to:

Right click on your ResourceFile
Change the "Build Action" property
Compile to "Embedded Resource"
Build and deploy

This will generate an App_GlobalResources in your /bin folder, now copy that folder also to the root of the web application

edited Dec 05 '20 at 11:49

Cody Gray - on strike

239,200
50
490
574

answered Aug 05 '16 at 17:06

AlexanderD

596
2
10
22

score 5 · Answer 11 · edited Dec 05 '20 at 11:51

5

In my case, the issue caused by the wrong order of class definitions. For example, I had added another class definition before my Form class:

namespace MyBuggyWorld
{
    public class BackendObject //This hack broke the VS 2017 winform designer and resources linker!
    {
        public TcpClient ActiveClient { get; set; }
        public BackgroundWorker ActiveWorker { get; set; }
    }

    public partial class FormMain : Form
    {
    }
}

After moving BackendObject to the end of the file (better yet would be to move it to a separate file), doing project clean + rebuild resolved the issue.

edited Dec 05 '20 at 11:51

Cody Gray - on strike

239,200
50
490
574

answered Feb 08 '18 at 03:36

Jawad Al Shaikh

2,475
2
28
41

2

Wow, I was not aware that having the wrong class at the start of the file would break things so badly. – BrainStorm.exe Feb 13 '20 at 17:36

score 4 · Answer 12 · answered Dec 18 '14 at 08:52

4

As far as this case is concerned check if the assembly containing resources has the default namespace set to the same text (Project->Properties->Default namespace; in VS) Check as well if the resx file has a property BuildAction set to "Embedded resource" Enjoy... ;)

answered Dec 18 '14 at 08:52

Mohammad Fazeli

648
10
13

1

Hi, do you mean that the default namespace (xxx) text should be the same as in the code: `Assembly localisationAssembly = Assembly.Load("xxx"); ResourceManager resourceManager = new ResourceManager("xxx", localisationAssembly);` – DanielV Apr 20 '15 at 15:46

score 3 · Answer 13 · answered Feb 08 '10 at 11:34

3

One approach would be to put the shared classes/resources in a separate class library project and refer them in both the web sites.

answered Feb 08 '10 at 11:34

Subbu

254
2
3

2

Surely this is the same problem then, isn't it? – Brett Rigby Apr 19 '12 at 09:57

score 3 · Answer 14 · answered Aug 09 '19 at 08:21

Just another case. I copied a solution with two projects and renamed them partially in the Windows explorer (folder names, .sln and .csproj file names) and partially with a massive Find & Replace action in Visual Studio (namespaces etc.). Nevertheless the exception stated by the OP still occurred. I found out that the Assembly and Namespace names were still old.

Although the project and everything else was already named OfficeStyle the Assembly name and Default namespace were still named Linckus.

After this correction everything worked fine again, compile and run time :)

score 3 · Answer 15 · answered Nov 11 '11 at 19:23

Thanks @CFinck ! Just to add a tip to others : I changed the ResourceManager line with this :

New Global.System.Resources.ResourceManager(Reflection.Assembly.GetCallingAssembly.GetName.Name & ".CommonNameOf.Resources", Reflection.Assembly.GetCallingAssembly())

I'm in vb.net but I think in C# the only difference would be + instead of & to concatenate strings.

This way I can use the same linked assembly files in two similar projects that share the resources.

score 2 · Answer 16 · answered Sep 20 '12 at 20:31

2

This error is also raised by Dotfuscation, since a resx designer file relies on reflection. If you are using Dotfuscator it will break your resx files. You must always add them as an exclusion from the obfuscation process.

answered Sep 20 '12 at 20:31

Trevor Elliott

11,292
11
63
102

score 2 · Answer 17 · answered May 30 '13 at 17:55

2

When we were using

HttpContext.GetGlobalResourceObject()

It would generate that error unless we wrapped that call inside a try/catch statement.

answered May 30 '13 at 17:55

jmb_coder

41
2

score 2 · Answer 18 · answered Apr 01 '15 at 09:27

For me the problem was copying .resx files and associated .cs files from one project to another. Both projects had the same namespace so that wasn't the problem.

Finally solved it when I noticed in Solution Explorer that in the original project the .resx files were dependent on the .cs files:

MyResource.cs
|_ MyResource.resx

While in the copied project the .cs files was dependent on the .resx files:

MyResource.resx
|_ MyResource.cs

It turned out that in the second project somehow the .resx files had been set to auto-generate the .cs files. The auto-generated .cs files were overwriting the .cs files copied from the original project.

To fix the problem edit the properties of each .resx file in the copied project. The Custom Tool property will be set to something like ResXFileCodeGenerator. Clear the Custom Tool property of the .resx file. You will need to re-copy the .cs file from the original project as it will have been overwritten by the auto-generated file.

Poikilos · Answer 19 · 2017-11-30T22:48:06.807

This can be caused by mismatched namespaces. The second from top answer (Sibi Elango's) says to right-click the resx file, and change Build option to EmbeddedResource, but I had already done that and still had the error. The top answer (CFinck's) notes a way of fixing this via manually editing files, however, I had this problem in MonoDevelop, and had to set the default namespace to the same as the cs file which was calling for the resource (the file which contained code such as the code below)...

this.Icon = ((System.Drawing.Icon)(resources.GetObject("$this.Icon")));

After setting the default namespace via the GUI, the line above no longer caused an exception.

score 1 · Answer 20 · answered Jun 10 '14 at 20:49

I have a WinForms application with a single project in the solution.
Targeting .NET Framework 4.0
Using SharpDevelop 4.3 as my IDE

Sounds silly, but I happened to have the Logical Name property set to "Resources" on my "Resources.resx" file. Once I cleared that property, all works hunky-dory.

Normally, when you add random files as EmbeddedResource, you generally want to set the Logical Name to something reasonable, for some reason, I did the same on the Resources.resx file and that screwed it all up...

Hope this helps someone.

score 1 · Answer 21 · answered Sep 15 '14 at 19:20

In my case these lines of code added to Web.config helped a lot:

<system.web>
     ...
    <globalization uiCulture="cs" culture="cs-CZ" />
     ...
<system.web>

Together with Build action: Embedded Resource and Custom Tool: PublicResXFileCodeGenerator.

score 1 · Answer 22 · answered Feb 09 '19 at 19:25

1

Yet another cause: if your namespace has a hyphen ("-"), then it will build and run correctly, but the resource won't be accessible. Namespaces (identifiers) aren't supposed to have hyphens, but this doesn't appear to be enforced anywhere except in loading resources. This has burned me twice over the decade.

answered Feb 09 '19 at 19:25

beanmf

493
5
7

It would appear that '_' also causes the problem – Geoff Scott Dec 04 '22 at 06:23

score 1 · Answer 23 · answered Jan 03 '20 at 14:49

I faced this issue for running Migration command.Update-Database in Package Manager console.

Accepted answer didn't solve my problem.

I had to change Build Action from Compile to Embedded Resource and It worked for me.

You can do the same using below steps:

Right click on migration.
Change the "Build Action" property "Compile" to "Embedded Resource"
Run Update-Database command.

score 1 · Answer 24 · answered Aug 09 '21 at 09:10

1

In my case I was trying to migrate a Form from one project to another. It turns out I only forget to add Form.resx to the new project. In the form I was using some icons so it was dependent to resources.

answered Aug 09 '21 at 09:10

F.zehra

87
8

score 1 · Answer 25 · answered May 05 '22 at 15:07

For me it was the following. In the MyStrings.Designer.cs file:

global::System.Resources.ResourceManager temp = 
    new global::System.Resources.ResourceManager(
      "MyApplication.MyProject", typeof(MyStrings).Assembly);

I had assumed that MyApplication.MyProject referred to the Namespace of the class rather than the directory of the file. I had placed the files in a subdirectory called Resources but the namespace didn't reflect that.

I changed it to

global::System.Resources.ResourceManager temp = 
    new global::System.Resources.ResourceManager(
      "MyApplication.MyProject.Resources", typeof(MyStrings).Assembly);

And it worked! (I didn't even have to update the namespace!)

score 0 · Answer 26 · answered Feb 28 '18 at 12:56

I was also facing the same issue, tried all the solutions mentioned in the answer but none seemed to work. Turned out that during the checkin of code to TFS. TFS did not checkin the Resx file it only checked in the designer file. So all other developers were facing this issue while running on their machines. Checking in the resx file manually did the trick

score 0 · Answer 27 · answered May 24 '19 at 19:53

Another thing to check is if you have LogicalName or ManifestResourceName defined on the EmbeddedResource. Make sure those are defined appropriately if your project file is using them as they can cause the resources to live under a name you are not expecting.

score 0 · Answer 28 · answered Feb 17 '21 at 13:18

I had the same issue when trying to run an update-database command on EF. Turns out the migration that was throwing the exception had the .resx file excluded from the project. I just right-clicked the .resx file and clicked "Include In Project". Problem solved.

score 0 · Answer 29 · answered Feb 18 '21 at 17:01

In my case, Build Action of the resource file was already Embedded Resource but every time I ran update-database, I got the same error, so i did the fellow steps and it's worked:

Change Build Action property to Compile
Build (got so many errors)
Change back Build Action property to Embedded Resource
update-database

And for some reason it's worked.

score 0 · Answer 30 · answered Jul 07 '21 at 19:30

Had a similar issue for a NetCore project and I noticed that after I added my migration (let's name it WhateverMigration), the .resx file reference as EmbeddedResource was not added to the .csproj even tho everything seemed fine. So I opened my .csproj file and I added:

<EmbeddedResource Update="Migrations\202107071914322_WhateverMigration.resx">
    <Generator></Generator>
    <DependentUpon>202107071914322_WhateverMigration.cs</DependentUpon>
</EmbeddedResource>

score 0 · Answer 31 · answered Sep 15 '21 at 01:58

You can also run into this exception when migrating a Windows Forms csproj to the new SDK-style project format. If you have any forms or user controls in subfolders, the *.resx files will generate using a namespace that includes the subfolder, which may not match the *.Designer.cs namespace. The solution is to add the following to the csproj:

<EmbeddedResourceUseDependentUponConvention>true</EmbeddedResourceUseDependentUponConvention>

score 0 · Answer 32 · answered Jan 14 '22 at 11:05

None of the other answers solved it for me. I had moved a number of forms and controls from one assembly to another, fixed all the namespaces and raN into this issue.

To keep the moved controls and forms separate from the rest I had put them in a subfolder. One resource reference was updated as suggested in one of the other answers. The IDE was warning me about the file path not matching the namespace with a blue squiggly but that is not an error so I initially ignored it.

When nothing appreared to fix it for me and I did not know anything better to try anymore I finally moved the controls and forms out of their subfolder (which was not expressed in the namespace) and the problem was gone.

Apperently there is still some hard dependency in WinForms on the folder structure.

score -1 · Answer 33 · answered Jan 28 '10 at 15:23

Just because you are referencing Project B's DLL doesn't mean that the Resource Manager of Project A is aware of Project B's App_GlobalResources directory.

Are you using web site projects or web application projects? In the latter, Visual Studio should allow you to link source code files (not sure about the former, I've never used them). This is a little-know but useful feature, which is described here. That way, you can link the Project B resource files into Project A.

Could not find any resources appropriate for the specified culture or the neutral culture

33 Answers33

Linked

Related