When upgrading a VB project to .NET, upgrad wizard fails due to missing design time license for CommonDialog control

I recently installed VisualStudio.Net Enterprise architect on my PC.

When attempting to load the SQLXMLBulkLoadGUI.vbp project into VS, the upgrade wizard runs, and attempts to convert the project to a .NET project.  The vbp file I'm referring to is the topic of a white paper associated with the Demos supplied with the SQLXML 3.0 download (part of SQL Server 2000 Web Services Toolkit).

It errors out in the middle of the upgrade with the following error:

Upgrad Failed:  Exception Occurred:  The referenced component CommonDialog is missing a design time license.

I've done a lot of research on this problem (I encountered it in Access 2000 as well in a previous endeavor), but thought that in installing VS, the license would have been provided.  I've seen a number of solutions that recommend unregistering and deleting the file (or renaming it) and reinstalling the component.  I assume I have to do this b/c I have the regular (not developer) edition of Office installed which seems to be the problem.

So... is this the right thing to do, and if so, how does one go about unregistering the component, and reinstalling it without having to reinstall the VS suite?

Other basics on my config:  Office 2003 (Professional), Windows XP Pro.

500 points for a step-by-step solution that will allow me to continue with an urgent XMLBulkLoad project.

Thanks Very Much.

Who is Participating?
Trying to use the Upgrade wizard for .NET 1.0 or 1.1, with a VB 6 project that is any more complicated than "Hello World", is an open invitation to DISASTER.  You will almost invariably spend more time trying to correct the indicated upgrade 'errors' and 'warnings' generated by the Upgrade Wizard than you would learning how to build the APP from scratch, in VB.NET - trust me, this I will almost 100% guarantee.  

Do NOT waste your time trying to use the Upgrade wizard. And I don't care what your experience level is with .NET - it doesn't matter.  Unless the VB 6 application was PERFECTLY designed and implemented using as close to PURE OO techniques as was possible with VB 6, the upgrade wizard will fail horribly.

Sorry to be so blunt, but those are the facts of life.  

Mike TomlinsonMiddle School Assistant TeacherCommented:
I have never seen a post that describes a wonderful success story involving the upgrade wizard on any reasonably complex application.

My recommendation is to build the app over from scratch in .Net.

Probably not the answer you wanted to hear but I'm betting I won't be the only one with this recommendation.
jerrylewisinsfAuthor Commented:
Unfortunately, that is not an option for me, as I did not build this project in the first place.  Rebuilding it in .Net from scratch is, at the moment, beyond my means.

Thanks for the tip, however.
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

I agree with Idle_Mind and Arthur_Wood.  The upgade wizard is a joke and VB and VB.NET are not as close as most people think.

<OT> Idle_Mind - I see you were born in San Diego.  Where, precisely, as I was born and raised in La Jolla, and went to school, through High School in San Diego - though I suspect many moons before you first saw the light of day - I graduated from HS in 1962!!  </OT>

Mike TomlinsonMiddle School Assistant TeacherCommented:

I grew up in an area called "El Cerritos" which is south of the San Diego State area.  It is between College avenue and 56th Street, just south of El Cajon Blvd.  My parents still live there so I visit every now and then.  I always forget how the weather doesn't change much compared to other parts of the country and world.

I graduated from Will C. Crawford High School in 1991.  (Don't start in with the "young pup" jokes...)


jerrylewisinsfAuthor Commented:
Ok everyone.

A new tack then.

As a complete neophyte in VS.Net, I'll have quite a bit of learning to do to build this project, but am sure I can pull it off.  I'll give the points to someone who can give me a quick lesson on how to from scratch implement the following code snippet...

(this is the minimum requried code to implement an XML bulk load)

Dim BulkLoadObj As New SQLXMLBulkLoad3
BulkLoadObj.ConnectionString = "<OLE DB Connection string for the target SQL Server 2000 database>"
BulkLoadObj.Execute "<Path to annotated mapping schema>","<Path to source XML data document>"
Set BulkLoadObj = Nothing

I can substitue all the relevant details (e.g. the name of my xml schema and data file, the connection string, etc).

But (and here is the dumb part of the question)...

How do I run / debug the code?  Do I have to compile it and then execute it from a command prompt or something?  I've done a bit of coding in VAJava and am generally familiar with IDEs, but VS.Net is just foreign to me.

Anyway, I realize that I can figure this out myself, it's just that I have a tight deadline and this is one of many many projects I'm working on, and a head start would be much appreciated.


Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.