CODEWITHSUNDEEP
visual-studio-2010
Casper Leon Nielsen
Casper Leon Nielsen

Reputation: 2566

How can this Visual studio Resource warning be resolved or removed?

Anyone can help us here - we have been having this error for several months and had many a stab to remove it, but we still havnt figured out why its there or how to remove it. How is this warning resolved or removed?

Warning 351 A custom tool 'GlobalResourceProxyGenerator' is associated with file 'App_GlobalResources\GridLocalization.bg-BG.resx', but the output of the custom tool was not found in the project. You may try re-running the custom tool by right-clicking on the file in the Solution Explorer and choosing Run Custom Tool.

Upvotes: 15

Views: 10035

Answers (4)

mtm
mtm

Reputation: 1

In VS 2019, I also fixed the error:

Warning A custom tool 'ResXFileCodeGenerator' is associated with file , but the output of the custom tool was not found in the project.

By removing the reference to ResXFileCodeGenerator found within the project's " .csproj" file!

Upvotes: 0

ilves
ilves

Reputation: 397

In my case this was caused by a <LastGenOutput> entry in the csproj file that referred to a non-existent file. Removing that line got rid of the warning.

Upvotes: 7

Ralph Willgoss
Ralph Willgoss

Reputation: 12163

In Visual Studio 2017 I had the same issue with the following error

Warning A custom tool 'ResXFileCodeGenerator' is associated with file <snip name>, but the output of the custom tool was not found in the project.

Removing the reference to <Generator>ResXFileCodeGenerator</Generator> within the resource file declaration, fixed the issue.

Upvotes: 1

Casper Leon Nielsen
Casper Leon Nielsen

Reputation: 2566

After checking out the csproj file and discussing it in the group, we came up with the following answer:

When the resources were added to the project they were added using the wizard. This wizard added the designer files also, so for each reasource file there was also a .designer file.

This was seen as something that was not needed for the language specific resources and the designer files were deleted.

However the csproj files maintained the custom tool reference.

Deleting this reference (to "GlobalResourceProxyGenerator") for each of these resource files removed the issue.

The issue is that Visual Studio 2010 does not automatically remove this tool reference when the designer files are removed manually, creating this warning.

Upvotes: 18

Related Questions