Mike can you reduce your problematic project down to the absolute minimum that still reproduces the problem and post back?

Chris - re zh-Hans/zh-Hant. We have discussed the fact this breaks us, with the team in Windows that made this change to culture names in Vista. The good news is that they are planning to partially revert their change in Vista. The result is MSBuild should build zh-Hant/s and zh-Chs/t just fine on Vista (and on XP, too, if you install the extra culture pack). You can use just zh-Chs/t and resources should load fine on both Vista and XP. At some future point, Chs/t will likely be deprecated for Hans/t . I don't know what public Vista build this change will be in.

Dan

"This posting provided AS-IS, with no warranties"

We have encountered this same duplicate resource problem several times. From reading through this post and from other information there seems to be several reasons why this message can occur.

1. You could actually have a duplicate resource entry in your project file.

2. Your obj files could have become corrupt, you need to clear out your obj files (although I haven't seen this problem for a while in my team - it might be fixed in 2008).

3. If you are using a custom culture, perhaps with the .Net RegisterCulture method, ensure that the culture has been registered on yourcomputer. If you've reinstalled your OS and installed VS2008 and you can't builddue to this problem it could be because you need to register your custom cultures before you build. This error seems to be thrown when msbuild cannot find the culture.

Good luck.

This error can also occur if the contents of the \obj folder have become corrupted. I noticed project.VBProj.filelist.txt file that I was getting nested references to various files, the resources files among them.

To resolve the issue, I blew away the contents of the \obj folder and rebuilt the project. That fixed the issue.

I got the same error, but deleting the \obj folder didn't fix it. The error reads "The item "obj\Release\ProFlyingReport.frmOptionsDialog.resources" was specified more than once in the "Resources" parameter. Duplicate items are not supported by the "Resources" parameter."

I've tried everything I can think of, but a program that was running fine is all of a sudden broken. I can't find a way to fix it, and the error doesn't tell me where to go to "unmention" the form.

Any ideas?

Thanks,

Mike

Mike can you reduce your problematic project down to the absolute minimum that still reproduces the problem and post back?

Chris - re zh-Hans/zh-Hant. We have discussed the fact this breaks us, with the team in Windows that made this change to culture names in Vista. The good news is that they are planning to partially revert their change in Vista. The result is MSBuild should build zh-Hant/s and zh-Chs/t just fine on Vista (and on XP, too, if you install the extra culture pack). You can use just zh-Chs/t and resources should load fine on both Vista and XP. At some future point, Chs/t will likely be deprecated for Hans/t . I don't know what public Vista build this change will be in.

Dan

"This posting provided AS-IS, with no warranties"

I solved the problem by backing up the offending form file, deleting it from the project, rebuilding, and then adding the form back into the project. It appears that this forced VS to rebuild the resources for the form.

Mike

According to the above mentioned workaround to resolve the error "The item "obj\Debug\blabla\blabla" was specified more than once in the "Resources" parameter. Duplicate items are not supported by the "Resources" parameter", i like to mention that at my side this error popped up due to a - from my point of view - an omission in the refractoring tool. One way or the other just oneform was renamed by a suddenly popped up dialogbox doing a refractoring process. Refractoring processes apperently can develope unexpected events.

KWHJ

I had the same error after copy-and-pasting a form and then renaming the new version, when I clicked on the 'show all files' icon in the solution explorer I noticed thata second .resx file was present under the offending form named after the original form that I had copied. I deleted this 'spare' file and the error went away.

HTH

This worked for me as well. I needed to spilt a form into two files to separate business logic from presentation logic. I created a new form and changed its code to make it a partial of my original form, but encountered the same error. Performing a backup/Delete/Add Existing... did the trick.

The only thing I find odd is that the second form file I created to hold the business logic has a designer form of its own that isn't used.

I am experiencing the same problem I have added a partial class into my project and it created its own .resx file when i deleted this file the problem was gone. I know this is not a valid solution because it is created by wizard as soon as someone click that diakog box if anyone could suggest me with the better solution . Any kind of help would be appreciated.

It turns out that VS2005 has a problem with copy - paste - modify of a form. It bungles the new form with this problem and also modifies the original form with the modified name.

The easiest way to get out of this is to remove the new form from the project temporarily ... fix the old form name and attempt to recompile and then re-include the new form in the project and compile again.

The problem is not VS2005 it is your duplication of source files. I bet you that if you look at the file that is claiming it has duplicates and then if you search for another copy of it you will find an object with the same name in the same namespace. Now tell me, how is VS2005 responsible when you have duplicate objects at the same namespace that are not partial classes?

That's how I fixed it when I got the same error. It took about 90 seconds to fix. Try this:

If you look in the error message,Visual Studiotells you what Projectis affectedin the "Project" column.Find that project's .csproj file and open it in Notepad. (Be sure to make a backup copy!) For instance, if the Project is named "Roger", then the file you are looking for will be called "Roger.csproj".

Once you've opened the file, scroll through it until you see a bunch of tags that look like this (this is one tag):

<EmbeddedResource Include="MyGreatFrm.resx">
<SubType>Designer</SubType>
<DependentUpon>MyGreatFrm.cs</DependentUpon>
</EmbeddedResource>

Look for the duplicates. If there is a duplicate in there, delete it.Then rebuild and see if it works. If you deleted something you shouldn't have, at least you have a backup copy. ;)

This situation just happened to me (and that is why I have found myself here). I created the issue by doing the following:

1. Copied a form from the Solution Explorer

2. Pasted the form into the Solution Explorer

3. Clicked on the new form

4. Renamed the form

Then I started to get the error.

I found that VSIDE had renamed source forms designer.cs file and changed the name of the class (in the source code) to the new form's name (not the filename, but the reference in the source code). I edited the code myself and changed the name of the source form back.

Hope this helps.

A piece of advice when changing the Name property on the copied form: be sure to cancel the refactoring. Otherwise it will rename both forms, and any references you have in test projects, etc. It makes a real mess.

I have read every post in three threads on this subject. I renamed and refactored a class that creates a report. It has a design surface and therefore a res file. Initially I got the above error and the project failed to compile. I removed the offending class and the solution compiles again.

However, researching the file structure, I still find a reference to the resource file in /obj/debug. ie ...obj/debug/FinleyInfoSys.Applications.PathologyBillingSystem.UI.QuestInvoice.resources. There is no resource file at the location suggested by this file's name. There are also about four other orphans in this directory and they are recreated on every build.

I have thoroughly searched the project's csproj file for the orphans in any of the tags but to no avail.

I have deleted every unused, unnecessary file in the project directory, subdirectories and still have these orphans. Where and what pray tell, creates these .resources files? If I can correct the generation of them, the false compile error will go away.

I think you'll find that all your forms are made up of two partial classes - the main class, and a Designer class. That's the way that forms are generated by Visual Studio. It helps to keep the designer generated code away from your custom code. The only reason you get duplicate resource files is because the name set against your form is the same as the name of another form in the same project. Usually the name will be the same as the file name, but if you copy/paste, you can end up with a mismatch.

Hi all.

This thread has led me to the solution for this error (in my curcumstances) although none of the solutions presented here fixed it directly. Heres what worked for me....

My problem was that my project contained 2 resource files both called StringResources. Thes files were in different namespaces

with different custom tool namespaces. I renamed them StringResourcesA and StringResourcesB. and thatfixed it. I guess that even though they are in seperate namespaces the comiler tries to merge them somehow.

Thanks

Ben Reese

I got this message, too. It happened when I copied a form and renamed the file only. If you have done this, try opening the .cs file for the form you're having problems with and renaming the partial class' name and constructor method.

This worked for me, but then again, I'm quite a noob .

HTH!

-Kevin

This seems to occur when you copy an existing form/user control/etc and then paste it back into the project. If you open the "new" copy, you will see that it's class name is the same as the original. This is the source of the problem. Apparently whenStudio 2005copies and pastes a form, it changes the Solution Explorer label, but not the new form's class declaration.

For example, suppose you have MyForm and using the clipboard, copy and paste it back into your project. The solution explorer will show the "new" form to be named "Copy of MyForm". BUT, open the form's cs file and its designer.cs file and look at the class declaration. You will see that the new "Copy of MyForm" version is declared as class MyForm in both the cs and designer.cs files.

To fix, change the class declarations in Copy of MyForm.cs and Copy of MyForm.designer.cs from

public class MyForm

to

public class Copy of MyForm.

I think this will take care of it.

Encountered this message after copying and pasting the contents of one UserControl into another (I was reusing a number of custom controls and thought that this shortcut would work). I first renamed the namespace of the source files for the offending class. This worked. But this only helped me to isolate the problem. I had to recreate the new user control the old fashioned way, using drag and drop from the tool box.

In my scenario, I could not find any duplicates in the project file, resx files, source files etc. I have no idea where the actual duplication occurred.

Thanks for this post, it really helped me solve this very confusing bug.

Art

We have encountered this same duplicate resource problem several times. From reading through this post and from other information there seems to be several reasons why this message can occur.

1. You could actually have a duplicate resource entry in your project file.

2. Your obj files could have become corrupt, you need to clear out your obj files (although I haven't seen this problem for a while in my team - it might be fixed in 2008).

3. If you are using a custom culture, perhaps with the .Net RegisterCulture method, ensure that the culture has been registered on yourcomputer. If you've reinstalled your OS and installed VS2008 and you can't builddue to this problem it could be because you need to register your custom cultures before you build. This error seems to be thrown when msbuild cannot find the culture.

Good luck.

action:

select a form

copy

past

edit new form

change property (Name) to new name

problem:

C#2008 makes a QuickReplace of the old name

Changes the new files and the original files

This is not a programmers error

This is a bug in the scope of the replace code

C#2005 give a warning message

C#2008 Express just do it

Solution until the bug is fix: edit the new files by hand :-))

I have experienced same issue, but under different circumstances which others may find useful.

Just spent 3 hours attempting to set the DoubleBuffered property on three forms and two user controls...

Screens were taking some time to appear so thought I would try setting DoubleBuffered= True for each form and user control.This caused the creation of a resource file for each form and control, although as far as I can tell these files are pretty much empty. The problem occurred because the two user controls, although located in different namespaces,have identical names. Sowhen DoubleBuffered= False project compiles, but when DoubleBuffered = True, two resx files are created with same name, and although in different locations,cause the "Duplicate items..." error.

Having read this thread, the cause of the problem finally dawned on me...

Not sure how the user controls came to have identical names, may have been a corruption by the IDE. Needless to say, without these forums 3 hours could easily have turned into 3 days (or even3 weeks!).

Well the problem in my form was that I had two resx! I've fix this just deleting the useless one.

it's seems that if you've a form divided into different partial class you should do Design Time activities just in the main file!!

otherwise the IDE will add a new resx file to the partial file!

I resolved this after searching for the the named item in the code. I found that there were multiple test classes with identical names. I renamed, and in some cases removed, the class from the code behind.

DEBUG
public class CommentForm : UserControl
#else
public class CommentFormV2 : System.Windows.Forms.Form
#endif

changing the grayed code solved my proble.

Hope i cloud help someone