|
xtd
0.2.0
|
Definition
process creation flags definitions.
- Warning
- Internal use only
Variables | |
| constexpr int32_t | DEBUG_PROCESS |
| The calling thread starts and debugs the new process and all child processes created by the new process. It can receive all related debug events using the WaitForDebugEvent function. | |
| constexpr int32_t | DEBUG_ONLY_THIS_PROCESS |
| The calling thread starts and debugs the new process. It can receive all related debug events using the WaitForDebugEvent function. | |
| constexpr int32_t | CREATE_SUSPENDED |
| The primary thread of the new process is created in a suspended state, and does not run until the ResumeThread function is called. | |
| constexpr int32_t | DETACHED_PROCESS |
| For console processes, the new process does not inherit its parent's console (the default). The new process can call the AllocConsole function at a later time to create a console. For more information, see Creation of a Console. | |
| constexpr int32_t | CREATE_NEW_CONSOLE |
| The new process has a new console, instead of inheriting its parent's console (the default). For more information, see Creation of a Console. | |
| constexpr int32_t | CREATE_NEW_PROCESS_GROUP |
| The new process is the root process of a new process group. The process group includes all processes that are descendants of this root process. The process identifier of the new process group is the same as the process identifier, which is returned in the lpProcessInformation parameter. Process groups are used by the GenerateConsoleCtrlEvent function to enable sending a CTRL+BREAK signal to a group of console processes. | |
| constexpr int32_t | CREATE_UNICODE_ENVIRONMENT |
| If this flag is set, the environment block pointed to by lpEnvironment uses Unicode characters. Otherwise, the environment block uses ANSI characters. | |
| constexpr int32_t | CREATE_SEPARATE_WOW_VDM |
| This flag is valid only when starting a 16-bit Windows-based application. If set, the new process runs in a private Virtual DOS Machine (VDM). By default, all 16-bit Windows-based applications run as threads in a single, shared VDM. The advantage of running separately is that a crash only terminates the single VDM; any other programs running in distinct VDMs continue to function normally. Also, 16-bit Windows-based applications that are run in separate VDMs have separate input queues. That means that if one application stops responding momentarily, applications in separate VDMs continue to receive input. The disadvantage of running separately is that it takes significantly more memory to do so. You should use this flag only if the user requests that 16-bit applications should run in their own VDM. | |
| constexpr int32_t | CREATE_SHARED_WOW_VDM |
| The flag is valid only when starting a 16-bit Windows-based application. If the. | |
| constexpr int32_t | INHERIT_PARENT_AFFINITY |
| The process inherits its parent's affinity. If the parent process has threads in more than one processor group, the new process inherits the group-relative affinity of an arbitrary group in use by the parent. | |
| constexpr int32_t | CREATE_PROTECTED_PROCESS |
| The process is to be run as a protected process. The system restricts access to protected processes and the threads of protected processes. For more information on how processes can interact with protect. | |
| constexpr int32_t | EXTENDED_STARTUPINFO_PRESENT |
| The process is created with extended startup information; the lpStartupInfo parameter specifies a STARTUPINFOEX structure. | |
| constexpr int32_t | CREATE_SECURE_PROCESS |
| This flag allows secure processes, that run in the Virtualization-Based Security environment, to launch. | |
| constexpr int32_t | CREATE_BREAKAWAY_FROM_JOB |
| The child processes of a process associated with a job are not associated with the job. | |
| constexpr int32_t | CREATE_PRESERVE_CODE_AUTHZ_LEVEL |
| Allows the caller to execute a child process that bypasses the process restrictions that would normally be applied automatically to the process. | |
| constexpr int32_t | CREATE_DEFAULT_ERROR_MODE |
| The new process does not inherit the error mode of the calling process. Instead, the new process gets the default error mode. | |
| constexpr int32_t | CREATE_NO_WINDOW |
| The process is a console application that is being run without a console window. Therefore, the console handle for the application is not set. | |
Variable Documentation
◆ DEBUG_PROCESS
|
constexpr |
#include <xtd.core.native/include/xtd/native/process_creation_flags.hpp>
The calling thread starts and debugs the new process and all child processes created by the new process. It can receive all related debug events using the WaitForDebugEvent function.
- Library
- xtd.core.native
- Remarks
- For more info see https://docs.microsoft.com .
- Warning
- Internal use only
◆ DEBUG_ONLY_THIS_PROCESS
|
constexpr |
#include <xtd.core.native/include/xtd/native/process_creation_flags.hpp>
The calling thread starts and debugs the new process. It can receive all related debug events using the WaitForDebugEvent function.
- Library
- xtd.core.native
- Remarks
- For more info see https://docs.microsoft.com .
- Warning
- Internal use only
◆ CREATE_SUSPENDED
|
constexpr |
#include <xtd.core.native/include/xtd/native/process_creation_flags.hpp>
The primary thread of the new process is created in a suspended state, and does not run until the ResumeThread function is called.
- Library
- xtd.core.native
- Remarks
- For more info see https://docs.microsoft.com .
- Warning
- Internal use only
◆ DETACHED_PROCESS
|
constexpr |
#include <xtd.core.native/include/xtd/native/process_creation_flags.hpp>
For console processes, the new process does not inherit its parent's console (the default). The new process can call the AllocConsole function at a later time to create a console. For more information, see Creation of a Console.
- Library
- xtd.core.native
- Remarks
- For more info see https://docs.microsoft.com .
- Warning
- Internal use only
◆ CREATE_NEW_CONSOLE
|
constexpr |
#include <xtd.core.native/include/xtd/native/process_creation_flags.hpp>
The new process has a new console, instead of inheriting its parent's console (the default). For more information, see Creation of a Console.
- Library
- xtd.core.native
- Remarks
- For more info see https://docs.microsoft.com .
- Warning
- Internal use only
◆ CREATE_NEW_PROCESS_GROUP
|
constexpr |
#include <xtd.core.native/include/xtd/native/process_creation_flags.hpp>
The new process is the root process of a new process group. The process group includes all processes that are descendants of this root process. The process identifier of the new process group is the same as the process identifier, which is returned in the lpProcessInformation parameter. Process groups are used by the GenerateConsoleCtrlEvent function to enable sending a CTRL+BREAK signal to a group of console processes.
- Library
- xtd.core.native
- Remarks
- For more info see https://docs.microsoft.com .
- Warning
- Internal use only
◆ CREATE_UNICODE_ENVIRONMENT
|
constexpr |
#include <xtd.core.native/include/xtd/native/process_creation_flags.hpp>
If this flag is set, the environment block pointed to by lpEnvironment uses Unicode characters. Otherwise, the environment block uses ANSI characters.
- Library
- xtd.core.native
- Remarks
- For more info see https://docs.microsoft.com .
- Warning
- Internal use only
◆ CREATE_SEPARATE_WOW_VDM
|
constexpr |
#include <xtd.core.native/include/xtd/native/process_creation_flags.hpp>
This flag is valid only when starting a 16-bit Windows-based application. If set, the new process runs in a private Virtual DOS Machine (VDM). By default, all 16-bit Windows-based applications run as threads in a single, shared VDM. The advantage of running separately is that a crash only terminates the single VDM; any other programs running in distinct VDMs continue to function normally. Also, 16-bit Windows-based applications that are run in separate VDMs have separate input queues. That means that if one application stops responding momentarily, applications in separate VDMs continue to receive input. The disadvantage of running separately is that it takes significantly more memory to do so. You should use this flag only if the user requests that 16-bit applications should run in their own VDM.
- Library
- xtd.core.native
- Remarks
- For more info see https://docs.microsoft.com .
- Warning
- Internal use only
◆ CREATE_SHARED_WOW_VDM
|
constexpr |
#include <xtd.core.native/include/xtd/native/process_creation_flags.hpp>
The flag is valid only when starting a 16-bit Windows-based application. If the.
- Library
- xtd.core.native
- Remarks
- For more info see https://docs.microsoft.com .
- Warning
- Internal use only
◆ INHERIT_PARENT_AFFINITY
|
constexpr |
#include <xtd.core.native/include/xtd/native/process_creation_flags.hpp>
The process inherits its parent's affinity. If the parent process has threads in more than one processor group, the new process inherits the group-relative affinity of an arbitrary group in use by the parent.
- Library
- xtd.core.native
- Remarks
- For more info see https://docs.microsoft.com .
- Warning
- Internal use only
◆ CREATE_PROTECTED_PROCESS
|
constexpr |
#include <xtd.core.native/include/xtd/native/process_creation_flags.hpp>
The process is to be run as a protected process. The system restricts access to protected processes and the threads of protected processes. For more information on how processes can interact with protect.
- Library
- xtd.core.native
- Remarks
- For more info see https://docs.microsoft.com .
- Warning
- Internal use only
◆ EXTENDED_STARTUPINFO_PRESENT
|
constexpr |
#include <xtd.core.native/include/xtd/native/process_creation_flags.hpp>
The process is created with extended startup information; the lpStartupInfo parameter specifies a STARTUPINFOEX structure.
- Library
- xtd.core.native
- Remarks
- For more info see https://docs.microsoft.com .
- Warning
- Internal use only
◆ CREATE_SECURE_PROCESS
|
constexpr |
#include <xtd.core.native/include/xtd/native/process_creation_flags.hpp>
This flag allows secure processes, that run in the Virtualization-Based Security environment, to launch.
- Library
- xtd.core.native
- Remarks
- For more info see https://docs.microsoft.com .
- Warning
- Internal use only
◆ CREATE_BREAKAWAY_FROM_JOB
|
constexpr |
#include <xtd.core.native/include/xtd/native/process_creation_flags.hpp>
The child processes of a process associated with a job are not associated with the job.
- Library
- xtd.core.native
- Remarks
- For more info see https://docs.microsoft.com .
- Warning
- Internal use only
◆ CREATE_PRESERVE_CODE_AUTHZ_LEVEL
|
constexpr |
#include <xtd.core.native/include/xtd/native/process_creation_flags.hpp>
Allows the caller to execute a child process that bypasses the process restrictions that would normally be applied automatically to the process.
- Library
- xtd.core.native
- Remarks
- For more info see https://docs.microsoft.com .
- Warning
- Internal use only
◆ CREATE_DEFAULT_ERROR_MODE
|
constexpr |
#include <xtd.core.native/include/xtd/native/process_creation_flags.hpp>
The new process does not inherit the error mode of the calling process. Instead, the new process gets the default error mode.
- Library
- xtd.core.native
- Remarks
- For more info see https://docs.microsoft.com .
- Warning
- Internal use only
◆ CREATE_NO_WINDOW
|
constexpr |
#include <xtd.core.native/include/xtd/native/process_creation_flags.hpp>
The process is a console application that is being run without a console window. Therefore, the console handle for the application is not set.
- Library
- xtd.core.native
- Remarks
- For more info see https://docs.microsoft.com .
- Warning
- Internal use only
Generated on Sun Dec 1 2024 09:55:50 for xtd by Gammasoft. All rights reserved.