Home/ Questions/Q 3313674
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-17T22:08:34+00:00

I generated an interface based off a WSDL definition file with wsdl.exe to use

  • 0

I generated an interface based off a WSDL definition file with wsdl.exe to use with a project. The resulting generated .cs file has the expected interface inside it, but the interface file doesn’t have a namespace – the interface definition is directly below the using statements.

I’ve never seen a source code file without an explicitly declared namespace, which leads me to wonder: what are the benefits and drawbacks of not explicitly declaring a namespace? Is this a common thing to do with generated code?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The benefits are, I guess, less time spent typing in a namespace… You are able to specify the namespace you want as a parameter with wsdl.exe, and you should do so:

    wsdl.exe /namespace:foo http://myreference/

    The drawback is that without a namespace, you’re that much more likely to have naming collisions with your objects. This problem gets more severe the more consumers there are of your class or interface. A namespace is definitely a good idea.

    • 0