Stephen, When you export a form definition using .NET API - the exported definition includes the form, its vuis and all its fields. The underlying C API has an additional option to export a specific VUI alone (which can be mainly used for localization purpose - export out vui as XML, edit the xml for inputting localization strings, then import back the modified vui xml). The .NET API does not give this level of control, to export a specific VUI of interest. This enhancement can be added however.
.NET API export function does not have ability to indicate "all objects" of a given type (wildcards). So it is the responsibility of the caller to get a list of all objects first, then use the list to build export object list (which is an array of pairs of object type & name), finally call the export method with the built export object list as param. The said wild-card handling can be added as an enhancement to .NET API, but at this time, in the absence of such feature, client programs have to workaround probably as described above. Regards Appajee -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Heider, Stephen Sent: Monday, July 17, 2006 12:02 PM To: arslist@arslist.org Subject: Re: .Net API - Export DSO and VUI Appajee, If I understand correctly the export options within the .Net API can include *everything*, for example when you export a Form the VUIs associated with the forms are also included in the export. Correct? To put another way, if I exported all Forms (-f), Active Links (-a), Filters (-t), Escalations (-q), Menus (-m), Guides (-g), Filter Guides (-h), Applications (-n), Packing Lists (-k) and Web Services (-z) then everything would be exported. This would be the equivalent of selecting Add All in the Export Definitions dialog in the Admin Tool GUI. Correct? Stephen _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
