Home/ Questions/Q 133621
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T06:27:57+00:00

I’ve been upgrading our solutions from VS 2005 to VS 2008; still targeting the

  • 0

I’ve been upgrading our solutions from VS 2005 to VS 2008; still targeting the .net 2.0 framework. The conversion wizard is simple and I’ve never had a conversion failure. The only beef that I’ve had so far is that I can’t immediately compile after the upgrade because VS has changed some of my namespaces causing naming collisions.

For example, I have a DAL project (lets call it MyNameSpace) that has a ‘Clients’ folder with a dataset named ‘dsClient’.

Here is what the dataset designer class looks like before conversion:

namespace MyNameSpace {     public partial class dsClient : global::System.Data.DataSet     {     } }

During the conversion process, VS is changing my designer class and adding the folder name to the end of the namespace so now it looks like this:

namespace MyNameSpace.Clients {     public partial class dsClient : global::System.Data.DataSet     {     } }

The problem with this is that I have another class file in that folder with the same name:

namespace MyNameSpace {     public class Clients     {     } }

This causes a naming collision and I have to manually go fix the changes that VS made. In some cases, VS changes the namespace name to the name of the dataset rather than the name of the folder.

Is this a config thing in the conversion wizard? I’d like to have the wizard just update the project files and leave the code alone.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. You can fix this by providing the namespace the code should be generated in:

    Open the properties of the xsd file and put the namespace for the code next to ‘Custom Tool Namespace’. Then click right on your xsd file and select ‘Run Custom Tool’ and you’re done.

    • 0