/* --- Script © 2005 EC Software --- */
var ua = navigator.userAgent;
var dom = (document.getElementById) ? true : false;
var ie4 = (document.all && !dom) ? true : false;
var ie5_5 = ((ua.indexOf("MSIE 5.5")>=0 || ua.indexOf("MSIE 6")>=0) && ua.indexOf("Opera")<0) ? true : false;
var ns4 = (document.layers && !dom) ? true : false;
var offsxy = 6;
function hmshowPopup(e, txt, stick) {
  var tip = '<table  border="1" cellpadding="6" cellspacing="0" bgcolor="#FFFFFF" style="{border-width:1px; border-color:#000000; border-collapse:collapse;}"><tr valign=top><td>'+ txt + '<\/td><\/tr><\/table>';
  var tooltip = atooltip();
  e = e?e:window.event;
  var mx = ns4 ? e.PageX : e.clientX;
  var my = ns4 ? e.PageY : e.clientY;
  var bodyl = (window.pageXOffset) ? window.pageXOffset : document.body.scrollLeft;
  var bodyt = (window.pageYOffset) ? window.pageYOffset : document.body.scrollTop;
  var bodyw = (window.innerWidth)  ? window.innerWidth  : document.body.offsetWidth;
  if (ns4) {
    tooltip.document.write(tip);
    tooltip.document.close();
    if ((mx + offsxy + bodyl + tooltip.width) > bodyw) { mx = bodyw - offsxy - bodyl - tooltip.width; if (mx < 0) mx = 0; }
    tooltip.left = mx + offsxy + bodyl;
    tooltip.top = my + offsxy + bodyt;
  }
  else {
    tooltip.innerHTML = tip;
    if (tooltip.offsetWidth) if ((mx + offsxy + bodyl + tooltip.offsetWidth) > bodyw) { mx = bodyw - offsxy - bodyl - tooltip.offsetWidth; if (mx < 0) mx = 0; }
    tooltip.style.left = (mx + offsxy + bodyl)+"px";
    tooltip.style.top  = (my + offsxy + bodyt)+"px";
  }
  with(tooltip) { ns4 ? visibility="show" : style.visibility="visible" }
  if (stick) document.onmouseup = hmhidePopup;
}
function hmhidePopup() {
  var tooltip = atooltip();
  ns4 ? tooltip.visibility="hide" : tooltip.style.visibility="hidden";
}
function atooltip(){
 return ns4 ? document.hmpopupDiv : ie4 ? document.all.hmpopupDiv : document.getElementById('hmpopupDiv')
}
popid_803635759="<p>VisualSetup 4.0 is a modern and sophisticated tool to create, manage and deploy setup projects. Powerful, complete, professional and easy to use, VisualSetup improves your development process, deploying software products, data files, or anything you want to distribute for Windows in a friendly and standard setup interface.<\/p>\n\r"
popid_851002366X="<p>Sometimes it is very interesting to allow the end-user choose the files that will be installed. Make the end-user choose each file that will be installed would be very boring task. The standard way to allow the end-user customize the files that will be installed by &nbsp;the setup program is to group files into components and let him\/her choose the components that will be installed.<\/p>\n\r<p>&nbsp;<\/p>\n\r<p>Components are group of files, shortcuts, registry\'s entries and INI files\' entries. If you think your end-user does not need to customize the files that will be installed, just does not use the components feature.<\/p>\n\r<p>You will define a component for each dependent part of your application. For instance, you can create a component named <span style=\"font-style: italic;\">Program Files<\/span> that contains all files necessary to run your application, a component <span style=\"font-style: italic;\">Help Files<\/span> that contains the documentation and a component <span style=\"font-style: italic;\">Samples<\/span> that contains files that example how to use your application.<\/p>\n\r<p>It is not good to separate parts that are dependent, for example a component named <span style=\"font-style: italic;\">Program Files<\/span> with all application files except for the runtime files and a component named <span style=\"font-style: italic;\">Runtime Files<\/span> with the runtime files. It is not a good idea because your application will not run without the runtime files, but there are some cases that you can separate files that are dependents.<\/p>\n\r<p>&nbsp;<\/p>\n\r<p>To define a component, open the Components\' editor (<span style=\"font-style: italic;\">Project &gt; Setup Components <\/span>menu command), and then select <span style=\"font-style: italic;\">Editor &gt; Add Component<\/span> menu command.<\/p>\n\r"
popid_732609024="<p>Windows Mobile components work analogously the Components. It is a way to group the Windows Mobile files, and allow the end-user choose which files to be installed.<\/p>\n\r<p>&nbsp;<\/p>\n\r<p>Each Windows Mobile component correspond to a set of Windows Mobile packages. The Default Windows Mobile component, defined in all VisualSetup projects, corresponds to the Windows Mobile packages generated by the device files, device shortcuts and device registry\'s entries that have the <span style=\"font-style: italic;\">Component<\/span> property empty. The <span style=\"font-style: italic;\">Component<\/span> property of device files, device shortcuts and device registry\'s entries refers to a Windows Mobile component. The <span style=\"font-style: italic;\">Component <\/span>property of all other project items, like desktop files, Palm files, desktop shortcuts, etc, refers to a <a href=\"components2.htm\">Component<\/a>.<\/p>\n\r<p>&nbsp;<\/p>\n\r<p>Actually, the end-user cannot choose directly the Windows Mobile components that will be installed. Each Windows Mobile component has the <span style=\"font-style: italic;\">Component<\/span> property that refers to a <a href=\"components2.htm\">Component<\/a>. The end-user can choose the components that will be installed, not the Windows Mobile components. If you create a <a href=\"components2.htm\">component<\/a> for each Windows Mobile component, and associate each Windows Mobile component with the component correspondent, you will allow the end-user choose which Windows Mobile components that will be installed.<\/p>\n\r<p>&nbsp;<\/p>\n\r<p>Another utility of Windows Mobile components is to workaround the Windows Mobile limitation of 998 files for each CAB file.Creating Windows mobile components, you can divide the files into different CAB files, and install all the files in the same installation. This will be a friendly solution for this limitation.<\/p>\n\r<p>&nbsp;<\/p>\n\r<p>To define a Windows Mobile component, open the Windows Mobile Components\' editor (<span style=\"font-style: italic;\">Windows Mobile &gt; Windows Mobile Components<\/span> menu command), and then select <span style=\"font-style: italic;\">Editor &gt; Add Windows Mobile Component <\/span>menu command.<\/p>\n\r"
popid_301699293="<p>Setup Types are sets of <a href=\"components2.htm\">Components<\/a>. When the end-user selects a setup type, actually he\/she is selecting a set of components. VisualSetup allows you define the setup types you want. So, setup types are the easiest and most abstract way to allow the end-user choose the files that will be installed.<\/p>\n\r<p>&nbsp;<\/p>\n\r<p>To define a Setup Type, open the Setup Types editor (<span style=\"font-style: italic;\">Project &gt; Setup Types<\/span> menu command), and then select <span style=\"font-style: italic;\">Editor &gt; Add Setup Type<\/span> menu command. For each Setup Type you include in the project, select the Components you want to relate with the setup type.<\/p>\n\r"
popid_252556571="<p>Setup Files are the files that will be installed in the Windows computer (desktop computer). To open the Setup Files editor, select <span style=\"font-style: italic;\">Project &gt; Setup Files<\/span> menu command.<\/p>\n\r<p>Select the folder you want to navigate in the Desktop Files toolbox (to show this toolbox select <span style=\"font-style: italic;\">View &gt; Setup Files\' Folders<\/span> menu command), and then change the files\' properties or add new files. To add files to current folder select <span style=\"font-style: italic;\">Edit &gt; Add Files<\/span> menu command.<\/p>\n\r"
popid_1326199378="<p>Windows Mobile Files are the files that will be installed in the Windows Mobile device. To open the Windows Mobile Files editor, select <span style=\"font-style: italic;\">Windows Mobile &gt; Windows Mobile Files<\/span> menu command.<\/p>\n\r<p>Select the folder you want to navigate in the Device Files toolbox (to show this toolbox select <span style=\"font-style: italic;\">View &gt; Windows Mobile Files\' Folders<\/span> menu command), and then change the files\' properties or add new files. To add files to current folder select <span style=\"font-style: italic;\">Edit &gt; Add Files<\/span> menu command.<\/p>\n\r"
popid_301060345="<p>Palm OS Files are the files that will be installed in the Palm OS device. To open the Palm OS Files editor, select <span style=\"font-style: italic;\">Palm OS &gt; Palm OS Files<\/span> menu command.<\/p>\n\r<p>Change the files\' properties or add new files. To add files to current folder select <span style=\"font-style: italic;\">Edit &gt; Add Files<\/span> menu command.<\/p>\n\r"
popid_672558667X="<p>Setup Shortcuts are the shortcuts that will be installed in the Windows computer (desktop computer). To open the Setup Shortcuts editor, select <span style=\"font-style: italic;\">Project &gt; Setup Shortcuts<\/span> menu command.<\/p>\n\r<p>Select the folder you want to navigate in the Desktop Shortcuts toolbox (to show this toolbox select <span style=\"font-style: italic;\">View &gt; Setup Shortcuts\' Folders<\/span> menu command), and then change the shortcuts\' properties or add new shortcuts. To add a shortcut to current folder select <span style=\"font-style: italic;\">Edit &gt; Add Shortcut<\/span> menu command.<\/p>\n\r"
popid_1970120117X="<p>Windows Mobile Shortcuts are the shortcuts that will be installed in the Windows Mobile device. To open the Windows Mobile Shortcuts editor, select <span style=\"font-style: italic;\">Project &gt; Windows Mobile Shortcuts<\/span> menu command.<\/p>\n\r<p>Select the folder you want to navigate in the Device Shortcuts toolbox (to show this toolbox select <span style=\"font-style: italic;\">View &gt; Windows Mobile Shortcuts\' Folders<\/span> menu command), and then change the shortcuts\' properties or add new shortcuts. To add a shortcut to current folder select <span style=\"font-style: italic;\">Edit &gt; Add Shortcut<\/span> menu command.<\/p>\n\r"
popid_1545577343X="<p>Setup Registry are the registry\'s entries that will be installed in the Windows computer (desktop computer). To open the Setup Registry editor, select <span style=\"font-style: italic;\">Project &gt; Setup Registry\'s Entries<\/span> menu command.<\/p>\n\r<p>Select the registry\'s key you want to navigate in the Desktop Registry\'s Keys toolbox (to show this toolbox select <span style=\"font-style: italic;\">View &gt; Setup Registry\'s Keys<\/span> menu command), and then change the registry\'s entries properties or add new registry\'s entries. To add a registry\'s entry to current registry\'s key select <span style=\"font-style: italic;\">Edit &gt; Add Registry\'s Entry<\/span> menu command.<\/p>\n\r"
popid_1901929194X="<p>Windows Mobile Registry are the registry\'s entries that will be installed in the Windows Mobile device. To open the Windows Mobile Registry editor, select <span style=\"font-style: italic;\">Windows Mobile &gt; Windows Mobile Registry\'s Entries<\/span> menu command.<\/p>\n\r<p>Select the registry\'s key you want to navigate in the Desktop Registry\'s Keys toolbox (to show this toolbox select <span style=\"font-style: italic;\">View &gt; Windows &nbsp;Mobile Registry\'s Keys<\/span> menu command), and then change the registry\'s entries properties or add new registry\'s entries. To add a registry\'s entry to current registry\'s key select <span style=\"font-style: italic;\">Edit &gt; Add Registry\'s Entry<\/span> menu command.<\/p>\n\r"
popid_847701384X="<p>Setup INI are the INI files\' entries that will be installed in the Windows computer (desktop computer). To open the Setup INI editor, select <span style=\"font-style: italic;\">Project &gt; INI Files\' Entries<\/span> menu command.<\/p>\n\r<p>Change the INI files\' entries properties or add new INI files\' entries. To add a INI file\'s entry, select <span style=\"font-style: italic;\">Edit &gt; Add INI Entry<\/span> menu command.<\/p>\n\r"
popid_1794266018="<p>HotSync allows you synchronize the Palm OS device\'s information with the desktop computer. You can create your own synchronization modules, and make HotSync automatically synchronize your application\'s data when the synchronization process is running.<\/p>\n\r<p>&nbsp;<\/p>\n\r<p>To open the HotSync Conduits editor, select <span style=\"font-style: italic;\">Palm OS &gt; HotSync Conduits<\/span> menu command.<\/p>\n\r<p>Change the HotSync conduits properties or add new HotSync conduits. To add a HotSync conduit, select <span style=\"font-style: italic;\">Edit &gt; Add HotSync Conduit<\/span> menu command.<\/p>\n\r"
popid_1647433231="<p>Setup Languages editor displays all languages your setup program will support. You can define how many languages you want. All setup projects, including the ones that will not generate multi-language setup programs, have a setup language already defined called Default Language, to edit the properties of the Default Language you must go to the <a href=\"project_information.htm\">Project Information<\/a> section of the <a href=\"project_properties.htm\">Project Properties<\/a> dialog.<\/p>\n\r<p>&nbsp;<\/p>\n\r<p>To define a new language you want to support, open the Setup Languages editor (<span style=\"font-style: italic;\">Messages &gt; Setup Languages<\/span> menu command), then select <span style=\"font-style: italic;\">Editor &gt; Add Language<\/span> menu command.<\/p>\n\r"
popid_1281440017="<p>VisualSetup allows you define string variables that are language-dependents. Language-dependent variables are very useful to allow you create multi-language click-script events. For example, instead of displaying the message \"Hello world!\", you will display the message \"%HelloWorld%\" and define the language-dependent variable <span style=\"font-style: italic;\">%HelloWorld%<\/span> with the value \"Hello World!\" for English and \"Hola mundo!\" for Spanish.<\/p>\n\r<p>&nbsp;<\/p>\n\r<p>To define a language-dependent variable, open the Multi-Language String Table editor (<span style=\"font-style: italic;\">Messages &gt; Multi-Language String Table<\/span> menu command). Then, select <span style=\"font-style: italic;\">Editor &gt; Add String Table Entry<\/span>. Change the <span style=\"font-style: italic;\">Variable<\/span> property with the name of the variable you want to be language-dependent, and then type the value of this variable for each defined Setup Language.<\/p>\n\r"
popid_662029312X="<p>Setup Bitmaps are the image files you will use in the interface with the end-user. VisualSetup supports only Windows Bitmap files, that are automatically compacted during the setup compilation.<\/p>\n\r<p>&nbsp;<\/p>\n\r<p>To add a bitmap to your setup program, select <span style=\"font-style: italic;\">Appearance &gt; Setup Bitmaps<\/span> menu command. Then, select <span style=\"font-style: italic;\">Editor &gt; Add Bitmap<\/span> menu command and select the bitmap file you want to include.<\/p>\n\r"
popid_262341866="<p>Setup Icons are the icon files you will use in the interface with the end-user. VisualSetup supports only Windows Icon files, that are automatically compacted during the setup compilation.<\/p>\n\r<p>&nbsp;<\/p>\n\r<p>To add an icon to your setup program, select <span style=\"font-style: italic;\">Appearance &gt; Setup Icons<\/span> menu command. Then, select <span style=\"font-style: italic;\">Editor &gt; Add Icon<\/span> menu command and select the icon file you want to include.<\/p>\n\r"
popid_300124590="<p>Setup Texts are the text files you will use in the interface with the end-user. VisualSetup supports plain-text files (.TXT) and formatted text files (.RTF), that are automatically compacted during the setup compilation.<\/p>\n\r<p>&nbsp;<\/p>\n\r<p>To add a text to your setup program, select <span style=\"font-style: italic;\">Appearance &gt; Setup Texts<\/span> menu command. Then, select <span style=\"font-style: italic;\">Editor &gt; Add Text<\/span> menu command and select the text file you want to include.<\/p>\n\r"
popid_2065937394X="<p>VisualSetup allows you customize all the information that will be displayed in the background\'s window. You can display either strings, bitmaps or icons. To include a new background window\'s item, select <span style=\"font-style: italic;\">Editor &gt; Add Background Window\'s Item<\/span> menu command.<\/p>\n\r"
popid_2118626327="<p>You will use the Dialog\'s Translation Table editor to translate the dialogs of your setup project. It is a very easy and useful editor, that will increase the task of translating each string contained in the dialog.<\/p>\n\r<p>&nbsp;<\/p>\n\r<p>To translate a setup dialog, go to Setup Dialogs\' toolbox (<span style=\"font-style: italic;\">View &gt; Setup Dialogs<\/span> menu command). Right-click the dialog you want to translate and then select <span style=\"font-style: italic;\">Dialog\'s Translation Table<\/span>. The dialog\'s translation table editor will be displayed with all translatable strings of the selected setup dialog. Now, just translate the strings of the language that you want.<\/p>\n\r"
popid_1873083606X="<p>VisualSetup allows you define string variables that are dialog-dependents and language-dependents. Dialog-dependent variables are very useful when you are using a common Style for all wizard dialogs and you want to display in the Style Dialog\'s controls a dialog-dependent information, like the dialog\'s title, for instance. Language-dependent variables are very useful to allow you create multi-language click-script events.<\/p>\n\r<p>For example, instead of displaying the same caption in a Style Dialog\'s control that would show the dialog\'s title, you will display the caption \"%DialogTitle%\" and define the variable <span style=\"font-style: italic;\">%DialogTitle%<\/span> for each wizard dialog that uses this Style Dialog.<\/p>\n\r<p>&nbsp;<\/p>\n\r<p>To define a dialog-dependent and language-dependent variable, open the Dialog\'s Variable editor for the dialog you want. Go to Setup Dialogs\' toolbox (<span style=\"font-style: italic;\">View &gt; Setup Dialogs<\/span> menu command). Right-click the dialog you want to define a variable and then select <span style=\"font-style: italic;\">Dialog\'s Variables<\/span>. Then, select <span style=\"font-style: italic;\">Editor &gt; Add Dialog\'s Variable<\/span>. Change the <span style=\"font-style: italic;\">Variable<\/span> property with the name of the variable you want to be dialog-dependent and language-dependent, and then type the value of this variable for each defined Setup Language.<\/p>\n\r"
popid_37417941X="<p>Global variables are the variables that you can access from every item of your project. When you change a global variable\'s value, every string, numeric or logic expression that uses it will be updated. Also, the variables associated to dialogs\' controls must to declared as global variables.<\/p>\n\r<p>&nbsp;<\/p>\n\r<p>To declare a global variable go to Global Variables\' Declaration editor, select <span style=\"font-style: italic;\">Actions &gt; Global Variables\' Declaration<\/span> menu command. Then, select <span style=\"font-style: italic;\">Editor &gt; Add Global Variable<\/span> menu command.<\/p>\n\r"
popid_401842823X="<p style=\"margin: 0px 0px 0px 24px;\">1. Open the Custom Actions\' Manager, select <span style=\"font-style: italic;\">Actions &gt; Custom Actions\' Manager<\/span>.<\/p>\n\r<p style=\"margin: 0px 0px 0px 24px;\">2. Select <span style=\"font-style: italic;\">Editor &gt; Add Custom Action<\/span>.<\/p>\n\r<p style=\"margin: 0px 0px 0px 24px;\">3. Go to the properties editor and type the properties of the custom actions:<\/p>\n\r<p style=\"margin: 0px 0px 0px 24px;\">&nbsp;<\/p>\n\r<div style=\"text-align: left; text-indent: 0px; padding: 0px 0px 0px 0px; margin: 0px 0px 0px 24px;\"><table cellspacing=\"0\" cellpadding=\"2\" border=\"0\" style=\"border: none border-spacing:0px;\">\n\r<tr valign=\"top\" align=\"left\">\n\r<td width=\"129\" style=\"width: 129px;\"><p style=\"margin: 0px 0px 0px 24px;\"><span style=\"font-style: italic;\">Name<\/span><\/p>\n\r<\/td>\n\r<td valign=\"top\" width=\"538\" style=\"width: 538px;\"><p style=\"margin: 0px 0px 0px 24px;\">The name of the action. This name must to be unique, and you will use it to call your custom action from the events.<\/p>\n\r<\/td>\n\r<\/tr>\n\r<tr valign=\"top\" align=\"left\">\n\r<td width=\"129\" style=\"width: 129px;\"><p style=\"margin: 0px 0px 0px 24px;\"><span style=\"font-style: italic;\">Description<\/span><\/p>\n\r<\/td>\n\r<td valign=\"top\" width=\"538\" style=\"width: 538px;\"><p style=\"margin: 0px 0px 0px 24px;\">The description of the action, that will be displayed in the click-script\'s editor.<\/p>\n\r<\/td>\n\r<\/tr>\n\r<tr valign=\"top\" align=\"left\">\n\r<td width=\"129\" style=\"width: 129px;\"><p style=\"margin: 0px 0px 0px 24px;\"><span style=\"font-style: italic;\">Type<\/span><\/p>\n\r<\/td>\n\r<td valign=\"top\" width=\"538\" style=\"width: 538px;\"><p style=\"margin: 0px 0px 0px 24px;\">The type of the returned variable (<span style=\"font-style: italic;\">%Result%<\/span>). All custom actions have a special variable named <span style=\"font-style: italic;\">%Result%<\/span>, this variable is returned to the caller event as the <span style=\"font-style: italic;\">Result<\/span> parameter. This property defines the type of this special variable.<\/p>\n\r<\/td>\n\r<\/tr>\n\r<\/table>\n\r<\/div>\n\r<p style=\"margin: 0px 0px 0px 24px;\">&nbsp;<\/p>\n\r<p style=\"margin: 0px 0px 0px 24px;\">4. &nbsp;Define the parameters of your custom action, please read the topic <a href=\"defining_parameters.htm\">Defining Parameters<\/a> for more information.<\/p>\n\r<p style=\"margin: 0px 0px 0px 24px;\">5. Define the actions of your custom action, double-click the custom action in the Custom Actions\' Manager and the click-script\'s editor will be displayed. Edit the custom action and save it when you have finished.<\/p>\n\r"
popid_28362504X="<p style=\"margin: 0px 0px 0px 24px;\">1. Open the DLL Actions\' Manager, select <span style=\"font-style: italic;\">Actions &gt; DLL Actions\' Manager<\/span>.<\/p>\n\r<p style=\"margin: 0px 0px 0px 24px;\">2. Select <span style=\"font-style: italic;\">Editor &gt; Add DLL Action<\/span>.<\/p>\n\r<p style=\"margin: 0px 0px 0px 24px;\">3. Go to the properties editor and type the properties of the DLL actions:<\/p>\n\r<p style=\"margin: 0px 0px 0px 24px;\">&nbsp;<\/p>\n\r<div style=\"text-align: left; text-indent: 0px; padding: 0px 0px 0px 0px; margin: 0px 0px 0px 24px;\"><table cellspacing=\"0\" cellpadding=\"2\" border=\"0\" style=\"border: none border-spacing:0px;\">\n\r<tr valign=\"top\" align=\"left\">\n\r<td width=\"129\" style=\"width: 129px;\"><p style=\"margin: 0px 0px 0px 24px;\"><span style=\"font-style: italic;\">Name<\/span><\/p>\n\r<\/td>\n\r<td valign=\"top\" width=\"538\" style=\"width: 538px;\"><p style=\"margin: 0px 0px 0px 24px;\">The name of the action. This name must to be unique, and you will use it to call your DLL action from the events.<\/p>\n\r<\/td>\n\r<\/tr>\n\r<tr valign=\"top\" align=\"left\">\n\r<td width=\"129\" style=\"width: 129px;\"><p style=\"margin: 0px 0px 0px 24px;\"><span style=\"font-style: italic;\">Description<\/span><\/p>\n\r<\/td>\n\r<td valign=\"top\" width=\"538\" style=\"width: 538px;\"><p style=\"margin: 0px 0px 0px 24px;\">The description of the action, that will be displayed in the click-script\'s editor.<\/p>\n\r<\/td>\n\r<\/tr>\n\r<tr valign=\"top\" align=\"left\">\n\r<td width=\"129\" style=\"width: 129px;\"><p style=\"margin: 0px 0px 0px 24px;\"><span style=\"font-style: italic;\">Type<\/span><\/p>\n\r<\/td>\n\r<td valign=\"top\" width=\"538\" style=\"width: 538px;\"><p style=\"margin: 0px 0px 0px 24px;\">The type of the value returned by the DLL function. <\/p>\n\r<\/td>\n\r<\/tr>\n\r<tr valign=\"top\" align=\"left\">\n\r<td width=\"129\" style=\"width: 129px;\"><p style=\"margin: 0px 0px 0px 24px;\"><span style=\"font-style: italic;\">Unicode<\/span><\/p>\n\r<\/td>\n\r<td valign=\"top\" width=\"538\" style=\"width: 538px;\"><p style=\"margin: 0px 0px 0px 24px;\">Define if the DLL function uses the Unicode char set. VisualSetup automatically converts the Unicode strings to ANSI strings and ANSI strings to Unicode.<\/p>\n\r<\/td>\n\r<\/tr>\n\r<tr valign=\"top\" align=\"left\">\n\r<td width=\"129\" style=\"width: 129px;\"><p style=\"margin: 0px 0px 0px 24px;\"><span style=\"font-style: italic;\">FileName<\/span><\/p>\n\r<\/td>\n\r<td valign=\"top\" width=\"538\" style=\"width: 538px;\"><p style=\"margin: 0px 0px 0px 24px;\">The path of the DLL file that contains the function you want to call.<\/p>\n\r<\/td>\n\r<\/tr>\n\r<tr valign=\"top\" align=\"left\">\n\r<td width=\"129\" style=\"width: 129px;\"><p style=\"margin: 0px 0px 0px 24px;\"><span style=\"font-style: italic;\">FunctionName<\/span><\/p>\n\r<\/td>\n\r<td valign=\"top\" width=\"538\" style=\"width: 538px;\"><p style=\"margin: 0px 0px 0px 24px;\">The name of the function stored in the DLL file you want to call.<\/p>\n\r<\/td>\n\r<\/tr>\n\r<\/table>\n\r<\/div>\n\r<p style=\"margin: 0px 0px 0px 24px;\">&nbsp;<\/p>\n\r<p style=\"margin: 0px 0px 0px 24px;\">4. &nbsp;Define the parameters of your DLL action, please read the topic <a href=\"defining_parameters2.htm\">Defining Parameters<\/a> for more information.<\/p>\n\r"
popid_948200806="<p>Click-script editor is very easy to use. After opening the event you want to edit you will want to add new actions to event. To add a action to current event select <span style=\"font-style: italic;\">Click-Script &gt; Insert Action<\/span> menu command. Then select the kind of action you want and select the action you want. There are four kinds of actions:<\/p>\n\r<p>&nbsp;<\/p>\n\r<div style=\"text-align: left; text-indent: 0px; padding: 0px 0px 0px 0px; margin: 0px 0px 0px 0px;\"><table border=\"0\" cellpadding=\"0\" cellspacing=\"0\" style=\"line-height: normal;\"><tr valign=\"baseline\"><td width=\"13\"><span style=\"font-size: 9pt; font-family: \'Arial Unicode MS\', \'Lucida Sans Unicode\', \'Arial\'; color: #000000;\">&#8226;<\/span><\/td><td>Default actions: are all actions that VisualSetup natively supports.<\/td><\/tr><\/table><\/div><div style=\"text-align: left; text-indent: 0px; padding: 0px 0px 0px 0px; margin: 0px 0px 0px 0px;\"><table border=\"0\" cellpadding=\"0\" cellspacing=\"0\" style=\"line-height: normal;\"><tr valign=\"baseline\"><td width=\"13\"><span style=\"font-size: 9pt; font-family: \'Arial Unicode MS\', \'Lucida Sans Unicode\', \'Arial\'; color: #000000;\">&#8226;<\/span><\/td><td><span style=\"font-weight: bold;\">Custom<\/span> actions: are your custom actions that you have defined using the Custom Actions editor. For further information on custom actions, read the <a href=\"custom_actions.htm\">Custom Actions<\/a> topic.<\/td><\/tr><\/table><\/div><div style=\"text-align: left; text-indent: 0px; padding: 0px 0px 0px 0px; margin: 0px 0px 0px 0px;\"><table border=\"0\" cellpadding=\"0\" cellspacing=\"0\" style=\"line-height: normal;\"><tr valign=\"baseline\"><td width=\"13\"><span style=\"font-size: 9pt; font-family: \'Arial Unicode MS\', \'Lucida Sans Unicode\', \'Arial\'; color: #000000;\">&#8226;<\/span><\/td><td><span style=\"font-weight: bold;\">DLL<\/span> actions: are the actions that you have defined using the DLL Actions editor. For further information on DLL actions, read the  <a href=\"dll_actions.htm\">DLL Actions<\/a> topic.<\/td><\/tr><\/table><\/div><div style=\"text-align: left; text-indent: 0px; padding: 0px 0px 0px 0px; margin: 0px 0px 0px 0px;\"><table border=\"0\" cellpadding=\"0\" cellspacing=\"0\" style=\"line-height: normal;\"><tr valign=\"baseline\"><td width=\"13\"><span style=\"font-size: 9pt; font-family: \'Arial Unicode MS\', \'Lucida Sans Unicode\', \'Arial\'; color: #000000;\">&#8226;<\/span><\/td><td><span style=\"font-weight: bold;\">Libraries<\/span>\' actions: are the actions of the Actions\' Libraries that you have selected for your setup project. For further information on actions\' libraries, read the <a href=\"actions_libraries.htm\">Actions\' Libraries<\/a> topic.<\/p>\n\r<\/td><\/tr><\/table><\/div>"
popid_1869157510X="<p class=\"p_Sub-title\"><span class=\"f_Sub-title\">Trusted Release - Step 1<\/span><\/p>\n\r<p>&nbsp;<\/p>\n\r<p>When you select the first step of the Trusted Release build mode and ask VisualSetup to generate the setup program, VisualSetup generates the Setup DLL files for each defined Windows Mobile Component, with actions in some Windows Mobile Event, in the directory defined in the <span style=\"font-style: italic;\">Signed Setup DLLs Directory <\/span>property in the <a href=\"safe_build.htm\">Trusted Build<\/a> section of <a href=\"project_properties.htm\">Project Properties<\/a> dialog.<\/p>\n\r<p>If you are not using the Windows Mobile events, you do not need to generate the setup program using this step of Trusted Release mode; you can build the setup program using the <span style=\"font-style: italic;\">Trusted Release - Step 2<\/span> build mode directly.<\/p>\n\r<p>&nbsp;<\/p>\n\r<p>After generating the setup program using the <span style=\"font-style: italic;\">Trusted Release - Step 1<\/span> build mode, you need to sign every generated Setup DLL. Go to the next step only if you have already signed all Setup DLL files stored in the <span style=\"font-style: italic;\">Signed Setup DLLs Directory<\/span>. Maybe you will not need to sign all Setup DLL files, you just need to sign the ones that will be used in Windows Mobile 5 devices.<\/p>\n\r<p>&nbsp;<\/p>\n\r"
popid_1869157467X="<p class=\"p_Sub-title\"><span class=\"f_Sub-title\">Trusted Release - Step 2<\/span><\/p>\n\r<p class=\"p_Sub-title\"><span class=\"f_Sub-title\">&nbsp;<\/span><\/p>\n\r<p>When you select the second step of the Trusted Release build mode and ask VisualSetup to generate the setup program, VisualSetup generates the Windows Mobile packages in the directory defined in the <span style=\"font-style: italic;\">Signed CABs Directory <\/span>property in the <a href=\"safe_build.htm\">Trusted Build<\/a> section of <a href=\"project_properties.htm\">Project Properties<\/a> dialog.<\/p>\n\r<p>When you select this build mode, VisualSetup\'s compiler uses the signed Setup DLL files located in the <span style=\"font-style: italic;\">Signed Setup DLLs Directory<\/span>, that were previously generated using the <span style=\"font-style: italic;\">Trusted Build - Step 1<\/span> build mode, instead of regenerating them.<\/p>\n\r<p>&nbsp;<\/p>\n\r<p>After generating the setup program using the <span style=\"font-style: italic;\">Trusted Release - Step 2<\/span> build mode, you need to sign every generated Windows Mobile package. Go to the next step only if you have already signed all Windows Mobile package files stored in the <span style=\"font-style: italic;\">Signed CABs Directory<\/span>. Maybe you will not need to sign all Windows Mobile package files, you just need to sign the ones that will be used in Windows Mobile 5 devices.<\/p>\n\r<p>&nbsp;<\/p>\n\r"
popid_1869157424X="<p class=\"p_Sub-title\"><span class=\"f_Sub-title\">Trusted Release - Step 3<\/span><\/p>\n\r<p class=\"p_Sub-title\"><span class=\"f_Sub-title\">&nbsp;<\/span><\/p>\n\r<p>When you select the third step of the Trusted Release build mode and ask VisualSetup to generate the setup program, VisualSetup generates the setup program in the output directory defined in the <a href=\"output_options.htm\">Output Information<\/a> section of <a href=\"project_properties.htm\">Project Properties<\/a> dialog.<\/p>\n\r<p>When you select this build mode, VisualSetup\'s compiler uses the signed Windows Mobile package files located in the <span style=\"font-style: italic;\">Signed CABs Directory<\/span>, that were previously generated using the <span style=\"font-style: italic;\">Trusted Build - Step 2<\/span> build mode, instead of regenerating them.<\/p>\n\r<p>&nbsp;<\/p>\n\r"