Why is it that in Visual Studio 2008, when I explicitly set my Dataset's "Custom Tool Namespace" to be something like, "DatasetFun", and then I use the new .NET 3.5 feature to separate the Dataset Schema from the Table Adapters by setting the new"Dataset Project" property, the Dataset Table Adapter namespaces are different than the Dataset Table schema namespaces?

So for instance, if I set my "Custom Tool Namespace" to "DatasetFun" and I set my "Dataset Project" to "ClassLibrary1" and the "ClassLibrary1" project's default namespace is also set to "ClassLibrary1", the Dataset strongly-typed class will be correctly placed in the "ClassLibrary1" PROJECT but will have the incorrect namespace of "ClassLibrary1" even though I explicitly set it to "DatasetFun" in the original *.xsd designer.

To me, this appears to be a bug in VS2008. (Or at least a legacy feature that MS overlooked when building the new Dataset features into VS2008.)

Chad W. Stoker

Hi Cstoker

Well, you are right. It’s a reported issue that has been recorded within Microsoft.

Please refer to the following report page for more information about this issue:

DataSet Project not using Custom Tool Namespace

As Visual Studio’s program manager has said in this report, this issue will be fixed in the next version of Visual Studio. Sorry for any inconvenience that we have brought for you.

Thanks for your report.

Best wishes

Jun Wang

Hi Cstoker

Well, you are right. It’s a reported issue that has been recorded within Microsoft.

Please refer to the following report page for more information about this issue:

DataSet Project not using Custom Tool Namespace

As Visual Studio’s program manager has said in this report, this issue will be fixed in the next version of Visual Studio. Sorry for any inconvenience that we have brought for you.

Thanks for your report.

Best wishes

Jun Wang