A Quick Tour of the XSD Migration Kit
By Stephan Meyn
Thursday, October 23, 2003
I have built a set of tables for a simple Issue Tracking solution in MS-Access. The following explains the steps to migrate to a prevalence solution:- In Visual Studio.NET set up a project with two applications (a Winforms app called Loader and a DLL called IssueTracker)
- In the Loader application project open the main form and bring up the server explorer
- In the server explorer connect to the ACCESS database
- drag and drop the tables of the database you want to convert onto the loader app mainform
- This step creates a db connection and a set of DataAdapters
- select any of the data adapters and click 'generate dataset'
- in the subsequent dialog select all the dataadapters
- Click ok and remember the type name of the data set
- Now start the Migration Kit application (called Bamboo Builder)
- Enter the following info
- Check InheritFrom MarshalByRefObject
- Namespace Name: the namespace you choose for the generated classes
- Root Name: The name of the class that will controll access to all instances. this is the root class
- Target Directory: where you want to have the generated classes saved
- Loader Dataset ClassName: when you generated Dataset in step 8 above you gave it a name.
- LoaderNameSpace: the namespace the loader uses. This and the previous are used to generate the fully qualified name for the loader class to access the strong data types that the compiled XSD provides. BambooBuilder requires the fully qualified typename(as in Namespace of the loader and the dataset type name) to build the loader correctly.
- Select File Save to save this definition
- Select generate
Once you have done this you will get a set of class files:
- a root class (called IssueTrackRoot.cs)
- a loader class (called IssueTrackRootLoader.cs)
- one class file for each table
-
- ActionItem.cs
- CodeSet.cs
- CodeSetValue.cs
- Issue.cs
- IssueArea.cs
- Person.cs
And there you have it. You can now augment the class files as you see fit, link the root and table objects into a dll and complete the loader application to transfer your application.