How to fix “namespace x already contains a definit

Question

Specifically the error occurs in the Resources.Designer.cs:

Error 2 The namespace 'ModulusFE' already contains a definition for 'StockChartX' Resources.Designer.cs 11 21 ModulusFE.StockChartX

I've googled this and am still quite confused. Does anyone know anything I might try?

I have tried rebuilding and cleaning, as well as renaming the Resources.Designer.cs file in hopes that it would rebuild, but no luck.

The top of the code says this:

// <auto-generated>
//     This code was generated by a tool.
//     Runtime Version:4.0.30319.225
//
//     Changes to this file may cause incorrect behavior and will be lost if
//     the code is regenerated.
// </auto-generated>

Any ideas whatsoever would be appreciated.

Answer 1

I had something similar to this happen in my WPF application. It arose when I was trying to do some cleanup by declaring a namespace that was more descriptive. The problem arose because I had named the namespace in the code-behind (or cs) the same as the Window class. The namespace in the code-behind should have the last section stripped (after the rightmost dot) and used to declare the class and instantiate it. Notice Win below:

xaml

<Window x:Class="FrameApp.UI.Invoice.Win" ...>

code-behind

namespace FrameApp.UI.Invoice
{
    public partial class Win : Window
    {
        public Win()
    }
}

An obvious oversight but it set me back at least an hour with all the errors that appeared.

Answer 2

I had this happen to me about a year ago and I don't remember exactly what the root cause was, but there are two things you might try:

1. If it's an auto-generated file (as 'Resources.Designer.cs' tend to be), try deleting it and letting VS re-generate it.
2. Either separately or in conjunction with #1, select Show All Files in the Solution Explorer or open the solution folder in Windows Explorer - it could be that a version of the file somehow got excluded from the project and is therefor 'invisible' to VS but still makes it angry...

Answer 3

I think this issue is because you have added for a single table, 2 DAL classes. If this table is included in a relation, then remove the table_name.dbml for it, and keep that for the related tables. You must use one of them.

Answer 4

I had a similar problem and resolved it by removing any copies/backups of the .cs file from the directory.

Answer 5

This may be a bit of an edge case, but we've run across this in our development environment from time to time. We had to setup a custom culture in Windows to support en-HK. Windows 8.1 now supports this culture natively as does Windows 2012 R2, but older machines need to have the culture created. Any machine that does not have this culture setup will get this error reported. The solution is to create the culture on the machine (We have a console app created for this purpose) and everything starts working again.

Answer 6

This just happened to me. What happened was that I duplicated a project that was originally under source control. Although I properly renamed everything, the file permissions on all the files were still set to read-only. When I started modifying some form controls, Visual Studio automatically created a Resource1 file because the original Resource file was read-only.

What I did to fix this was as follows:

1. allow write permissions on the project files.
2. deleted the original Resource file
3. Ctrl-A for all form elements, then Ctrl-X to cut them.
4. Save the form.
5. Ctrl-V to paste them all back.
6. Save the form.

I had to do this because the auto-generated code wasn't updating on it's own, so I "forced" it to update by making a change to the form. Not doing this left a bunch of code from form elements that no longer existed prior to changing the file permissions.