CODEWITHSUNDEEP
c#dynamics-crm-2011dynamics-crmdynamic-programmingworkflow-activity
hello B
hello B

Reputation: 963

The namespace '<global namespace>' already contains a definition for 'Workflow'

I'm working on a Custom workflow activity. I've created my own helper.cs (Early Bound Entity Classes) with the Code Generation Tool (CrmSvcUtil.exe)

When I try to compile the code, it returns the following error:

The namespace '' already contains a definition for 'Workflow'

From the Helper.cs file.

Does anyone know what this means?

Upvotes: 10

Views: 27752

Answers (3)

Dragos Bobolea
Dragos Bobolea

Reputation: 782

I suggest you put all the early bound classes in a namespace, so it won't mess up with your other classes. You can specify the namespace with the "/namespace:" parameter for CrmSvcUtil. I usually put the early bound classes in my DataAccess namespace, together with the crm connection classes (Service/ServiceContext wrappers).

That being said, naming your custom workflow step "Workflow" is not really the best thing to do (if that's what you did, at least so I understood). Try capturing the essence of what the step does into the name - like a title.

Upvotes: 5

SteveCav
SteveCav

Reputation: 6729

Just got this because I thought it would be a great idea to copy all the contents of App_Code into App_Code\bkup before deploying a change. Erm, no.

Upvotes: 2

codegasm
codegasm

Reputation: 726

I had two separate resource files in a same solution. Deleting one of them did the trick :P

Upvotes: 5

Related Questions