Is namespace mandatory for xsd in order to use LinqToXsd?

Aug 12, 2011 at 11:57 AM


I've been trying to use LinqToXsd. I'm using VS2010. Since I could not install (find guide how to install custom tool for vs2010) i'm using LinqToXsd.exe from command line.

So, the problem is that if xsd has no name space the class generated by LinqToXsd doesn't seem to work.


Could anyone please confirm whether the namespace is mandatory or something I'm not doing right. I don't want to use name space as much as possible so that I don't need to dictate the third party clients using our XSD.


Thanks heaps.

Aug 12, 2011 at 11:58 PM

could anyone please confirm whether namespace is mandatory on XSD in order for Linq ToXSD to work?

Aug 13, 2011 at 10:56 PM

I've same issue as well and looks like the discussion for this project is desserted?

Aug 15, 2011 at 10:40 AM

Not deserted, just a bit slow.

I'm not sure about that one. I use V1 not V2 (we're on .net 3.5) and we always use namespaces.

What do you mean by doesn't work?

Also, here is the discussion on how to add linq to xsd to your project (again, we use VS2K8, ymmv):



Aug 16, 2011 at 5:53 PM
Edited Aug 16, 2011 at 5:54 PM

Linq To XSD is pretty much deserted by MS. Together with sergey I tried to get in touch with the MS-team responsible for LINQ to XSD, but they seem to have no interest into continuing it. We decided to start working on it together to fix bugs, but that also has a very slow start (due to lack of time etc.). The usages of namespaces is indeed mandatory due to a bug.

See: for the workitem related to your problem.

Aug 22, 2011 at 2:24 PM

Deserted, but not dead right? Just being written very slowly? :)

Aug 23, 2011 at 7:14 PM
roboj1m wrote:

Deserted, but not dead right? Just being written very slowly? :)