Starts or continues a build, with extended options and logon credentials.
builder.StartEx2(ByVal launchType As BuildLaunchTypeEnum, ByVal flowThreadIdentity As Boolean = False, ByVal processIdentityUserName = "", ByVal processIdentityDomain = "", ByVal processIdentityPassword = "", ByVal logonNetCredentialsOnly As Boolean = True, useInteractiveWinStaDesktop As Boolean = True, ByVal stepType As StepTypeEnum = -1, ByVal startIndex As Long = -1, Optional ByVal selSteps As Variant)
How the build is being launched.
Whether to use the impersonated identity of the calling thread for the build thread. If False, the default identity of the process will be used for the build thread.
The user account name for an identity to use for any process started by build actions or script that call RunProgram/Ex or a Run Program action. This is the name of the user account to log on to. If you use the UPN format, user@DNS_domain_name, the domain field must be blank. The user account must have the Log On Locally permission on the local computer. This permission is granted to all users on workstations and servers, but only to administrators on domain controllers. If specified, the process will be created with the specified credentials. If blank, the process will be created using the default identify of the calling process.
Note: When specifying user credentials, processes started by the build will inherit the environment block of the calling process.
The name of the domain or server whose account database contains the user account specified in processIdentityUserName. Can be blank or . for the current domain.
The password of the user account for an identity to use for any processes started by the build.
Applies only if credentials are specified in the previous parameters. If True, processes created by the build will use the specified credentials on the network only. The new process uses the same token as the caller, but the system creates a new logon session within LSA, and the process uses the specified credentials as the default credentials. This can be used to create a process that uses a different set of credentials locally than it does remotely. This is useful in inter-domain scenarios where there is no trust relationship. The system does not validate the specified credentials. Therefore, the process can start, but it may not have access to network resources. If False, new processes will load the specified user's profile in the HKEY_USERS registry key. Loading the profile can be time-consuming, so it is best to pass False only if the process must access the information in the HKEY_CURRENT_USER registry key.
Applies only if credentials are specified in the previous parameters. If False, new processes created by the build will inherit the desktop and windowstation of the calling process (permission for the specified user account to the inherited windowstation and desktop are added automatically). If True, the interactive windowstation and desktop will be used by processes created by the build.
Note: Permissions for the specified user account are not automatically added to the interactive windowstation and desktop when True is passed, and applications may not start or draw properly unless the necessary permissions are assigned manually (see http://support.microsoft.com/kb/q165194/ for more details).
Type of steps to start building. If -1 is passed, the build is started or continued from the current position.
Index to set the current build position to. If -1 is passed, the build is started/continued from the current build position.
Array of Long values containing one or more selection ranges (first and last step index) to be built, or a Boolean value of True (-1) to build the specified step group (the step and all steps indented underneath it). If not passed, all checked steps are evaluated for building.
Applies to Builder object