Resource Editor Warning RC4005 on toolset "Visual Studio 2012 - Windows XP (v110_xp)" - by BOFHRAF

Status : 


Sign in
to vote
ID 789965 Comments
Status Closed Workarounds
Type Bug Repros 6
Opened 6/12/2013 2:05:53 AM
Access Restriction Public


if a resource file (.rc) is opened for editing, two warnings:

warning RC4005: '__useHeader': redefinition


warning RC4005: '__on_failure': redefinition

are popped up if the platform toolset is set to 'Visual Studio 2012 - Windows XP (v110_xp)'
Sign in to post a comment.
Posted by Deon [MSFT] on 4/29/2014 at 12:30 PM
Thank you for reporting this issue. This issue has been fixed in Visual Studio 2013. You can install a trial version of Visual Studio 2013 with the fix from:
Posted by oopdeveloper on 8/21/2013 at 11:24 AM
Why close this issue? It is still a valid issue even with Visual Studio 2003 Update 3. It seems that all 3 issues I've had today while migrating a VS2010 solution to VS2012 have bugs "closed" by MS, without any resolvement or workarounds. Is the VS team incapable of reproducing issues that people find and report, or are we just getting the run around due to the VS team's relucantance to address, recreate or fix any issues?
Posted by BOFHRAF on 7/19/2013 at 12:25 AM

The problem is not severe, just annoying. If you think it is ok to let us work with an annoying Visual Studio every day for the next years, I have to accept this.
Posted by Microsoft on 7/18/2013 at 10:47 AM

Thank you for taking the time to report this issue to us. After reviewing the reported issue, in the context of all the issues reported to us, we have decided not to take any action on backporting the fix for this issue to Visual Studio 2012 at this time.

If this issue is severe, causing critical business situations or blocking your product development or deployment, please go to or call 1-800-MICROSOFT for assistance.
For Microsoft premier customers, please contact your administrator, your Technical Account Manager, or your Microsoft premier account representative.

Pete Steijn
VC++ Team
Posted by BOFHRAF on 7/10/2013 at 1:15 AM
Thanks for the info. But we have upgraded just now to Visual Studio 2012 and will keep it for the next years. Please provide a fix for Visual Studio 2012.

Thank you
Posted by Jason [MSFT] on 7/9/2013 at 11:14 PM
This problem will be fixed in VS 2013 by now passing most of the /D options specified in the project to the "design time" resource compile for the resource editor (the .aps file generation step). The key is that there is a special define symbol that prevents the warnings when building with the XP toolset.

This not passing of /D options was suppressed many years ago apparently to make sure the resource editor shows all language resources. To preserve that behavior, not all /D options are passed in. The ones skipped are "AFX_RESOURCE_DLL" and any "AFX_TARG_*" symbols which are the symbols surrounding language specific resources and by skipping these will allow the resource editor to see all the resources.
Posted by BOFHRAF on 7/4/2013 at 7:35 AM
The problem still exists in Update 3!

Any news? It's annoying...
Posted by G M Sanders on 6/20/2013 at 6:21 AM
One thing that I have observed is that once the APS file has been generated, the errors no longer occur. To make the error occur again, delete the project APS file that is generated on first opening of the resource file in resource view, then reopen the resource file in resource view. This suggests that the error occurs during APS file generation.

This issue appears to be a duplicate of, which has been closed with no resolution, despite users still experiencing the problem. Please reference that report for further information.
Posted by Microsoft on 6/12/2013 at 8:12 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Microsoft on 6/12/2013 at 2:50 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(