This can be disabled in Project properties->Linker->Generate Manifest set to /MANIFEST:NO and then you can use your own supplied manifest file. The manifest file can be important for your application for instance to always request administrator rights. For more information see http://msdn.microsoft.com/en-us/library/ms235542.aspx[^]
> If you ever encounter this error while compiling (usually a downloaded project from internet), then remove the manifest file and remove the reference to the manifest file in the .rc file.
That says to blindly delete the manifest, and while it usually works, you’ve said nothing about why it is necessary. This is unlikely to be due to a dev manually adding two manifests on purpose, and more likely to happen when importing a project from an older version of Visual Studio to a newe one. Why would it have worked just fine before but no longer work once the project was migrated/updated?
This MSDN thread discusses this and Ted guesses that it’s because VC6 could not auto-generate a manifest, but newer versions do (in my case I imported a VS2003 project that had an auto-generated manifest and caused this error in VS2010—I have imported other VS2003 into VS2010 and did not have the error though…)
The error is often cause by two resources having the same resource ID
i.e. the same source resource (.rc) values in a (downloaded) library as in your main application.
This needs to be fixed by making sure any included resources (from a library) do not conflict with your main program resources. A quick edit of the ID numbers will fix the problem (don't forget to alter the next issue number at bottom to the resource file!),
For our own libraries we ensure they all use different ranges to the main application.
Last Visit: 31-Dec-99 19:00 Last Update: 19-Dec-14 18:49