<\/p>\n\r
Having Coverage Validator launch your program is the most common way to start up <\/p>\n\r
<\/p>\n\r
When you\'re ready to start running a .Net Core program<\/p>\n\r
<\/p>\n\r
<\/p>\n\r
Or use the shortcut<\/p>\n\r
<\/p>\n\r
<\/span> + <\/span> Launch .Net Core Application<\/p>\n\r <\/p>\n\r <\/p>\n\r <\/p>\n\r <\/span><\/p>\n\r <\/p>\n\r <\/p>\n\r <\/p>\n\r .Net Core applications can be self contained or framework dependent. This changes how the launch dialog works.<\/p>\n\r <\/p>\n\r •<\/span>.Net Core application type<\/span> choose which type of .Net Core application you are launching <\/span><\/p> <\/span><\/p>\n\r <\/span><\/p>\n\r <\/p>\n\r •<\/span>Application to launch (*.exe)<\/span> type or Browse<\/span> to set the program name (*.exe) to launch <\/span><\/p> <\/span><\/p>\n\r When you set this value the Application to launch DLL field will be automatically populated to have the same name as the EXE field but with a .DLL extension.<\/p>\n\r <\/p>\n\r •<\/span>Application to launch (*.dll)<\/span> type or Browse<\/span> to set the program name (*.dll) to launch <\/span><\/p> <\/p>\n\r •<\/span>Application to monitor<\/span> choose the application that actually gets monitored <\/span><\/p> <\/p>\n\r Alternatively you can monitor another application which will get launched by the start program.<\/p>\n\r <\/p>\n\r If the start application has already been added to the Applications to Monitor<\/a> settings with a default application then that default will be entered here automatically.<\/p>\n\r <\/p>\n\r Otherwise, if nothing has been set up yet, you can do it from here:<\/p>\n\r <\/p>\n\r •<\/span>Edit...<\/span> set the child applications that can be monitored for the start program <\/span><\/p> <\/p>\n\r This uses the Applications to Monitor dialog - which is exactly equivalent to using the Applications to Monitor<\/a> settings page.<\/p>\n\r <\/p>\n\r A fallback option is to start monitoring <<Any application that is launched>>.<\/span><\/p>\n\r <\/p>\n\r If in doubt, just use the same as the start application. <\/p>\n\r <\/p>\n\r <\/p>\n\r <\/p>\n\r <\/p>\n\r •<\/span>Application to launch (*.exe)<\/span> type or Browse<\/span> to set the program name (*.exe) to launch <\/span><\/p> <\/span><\/p>\n\r We don\'t auto-populate this field when you choose the Framework dependent application type. This because you may have your .Net Core runtime stored in a location that we can\'t auto-detect.<\/p>\n\r <\/p>\n\r To accommodate alternate locations for the .Net Core runtime we only auto-populate this field if it is empty when you choose the application DLL.<\/p>\n\r <\/p>\n\r •<\/span>Application to launch (*.dll)<\/span> type or Browse<\/span> to set the program name (*.dll) to launch <\/span><\/p> <\/span><\/p>\n\r If you set this when Application to launch EXE field is empty, the EXE field will be automatically populated with the path to the system .Net Core framework dependent runtime. <\/p>\n\r <\/p>\n\r This is typically c:\\program files\\dotnet\\dotnet.exe<\/span>.<\/p>\n\r <\/p>\n\r •<\/span>Application to monitor<\/span> choose the application that actually gets monitored <\/span><\/p> <\/p>\n\r Alternatively you can monitor another application which will get launched by the start program.<\/p>\n\r <\/p>\n\r If the start application has already been added to the Applications to Monitor<\/a> settings with a default application then that default will be entered here automatically.<\/p>\n\r <\/p>\n\r Otherwise, if nothing has been set up yet, you can do it from here:<\/p>\n\r <\/p>\n\r •<\/span>Edit...<\/span> set the child applications that can be monitored for the start program <\/span><\/p> <\/p>\n\r This uses the Applications to Monitor dialog - which is exactly equivalent to using the Applications to Monitor<\/a> settings page.<\/p>\n\r <\/p>\n\r A fallback option is to start monitoring <<Any application that is launched>>.<\/span><\/p>\n\r <\/p>\n\r If in doubt, just use the same as the start application. <\/p>\n\r <\/p>\n\r <\/span><\/p>\n\r •<\/span>.Net Core dotnet.exe arguments<\/span> any arguments that will be passed to the .Net Core runtime to control how the .Net Core runtime behaves. <\/span><\/p> <\/span><\/p>\n\r •<\/span>Edit...<\/span> displays the .Net Core runtime arguments editor<\/a> <\/span><\/p> <\/span><\/p>\n\r <\/p>\n\r <\/p>\n\r •<\/span>Launch Count<\/span> when monitoring a child<\/span> application, set its nth<\/span> invocation as the one to monitor <\/span><\/p> <\/p>\n\r If the application to start is the same as the application to monitor then this is set to 1 and cannot be changed.<\/p>\n\r <\/p>\n\r This will be reset to 1 every time the Application to Monitor field selection changes.<\/p>\n\r <\/p>\n\r If in doubt, leave it set to 1. <\/p>\n\r <\/p>\n\r <\/p>\n\r •<\/span>Command Line Arguments<\/span> enter program arguments exactly as passed to the target program <\/span><\/p> <\/p>\n\r •<\/span>Startup Directory<\/span> enter or click Dir...<\/span> to set the directory for the program to start in <\/span><\/p> <\/p>\n\r •<\/span>Environment Variables<\/span> click Edit...<\/span> to set any additional environment variables before your program starts <\/span><\/p> <\/p>\n\r •<\/span>File to supply to stdin<\/span> optionally enter or Browse <\/span>to set a file <\/span>to be read and piped to the standard input of the application <\/span><\/p> <\/p>\n\r •<\/span>File to supply to stdout<\/span> optionally enter or Browse <\/span>to set a file to be written with data piped from the standard output of the application <\/span><\/p> <\/span> The list at the bottom of the wizard shows previously run programs.<\/p>\n\r <\/p>\n\r Selecting an item in the list populates all the details above as used on the last run for that program.<\/p>\n\r <\/p>\n\r You can still edit those details before starting.<\/p>\n\r <\/p>\n\r •<\/span>Full path<\/span> shows the full path to the executable in the list •<\/span>Image Name<\/span> shows the short program name without path<\/p> <\/span><\/p>\n\r •<\/span>Delete<\/span> removes a selected program from the list<\/p> <\/p>\n\r •<\/span>Reset<\/span> clears all details in the wizard - including the list of previously run applications below<\/p> <\/span><\/p>\n\r <\/p>\n\r •<\/span>Type of data collection<\/span> Are you only interested in Native data, .Net data or both Native data and .Net data? <\/span><\/p> <\/span><\/p>\n\r •<\/span>Native Only<\/span> Ignore all .Net data in the target application. <\/span><\/p> <\/span><\/p>\n\r •<\/span>.Net Only<\/span> Ignore all Native data in the target application. <\/span><\/p> <\/span><\/p>\n\r •<\/span>Mixed Mode<\/span> Collect both Native and .Net data from the target application <\/span><\/p> <\/span><\/p>\n\r This setting cannot be changed after the application is launched <\/span><\/p>\n\r <\/span><\/p>\n\r •<\/span>Collect data from application<\/span> If it\'s the startup procedure you want to validate, obviously start collecting data from launch. <\/span><\/p> <\/p>\n\r Depending on your application, and what you want to validate, you may want to start collecting data immediately, or do it later.<\/p>\n\r <\/p>\n\r If your program has a complex start-up procedure, initialising lots of data, it may be much faster not<\/span> to collect data until the program has launched. <\/p>\n\r <\/p>\n\r <\/p>\n\r •<\/span>Redirect standard output<\/span> Controls redirection of stdout and stderr<\/p> <\/p>\n\r Use this option if you want to collect the output of stdout and stderr for later analysis. <\/p>\n\r <\/p>\n\r Be aware that if the output of the program under test generates a lot of data via stdout or stderr that this data will need to be stored in memory and could exhaust Coverage Validator\'s memory.<\/p>\n\r <\/p>\n\r •<\/span>Display command prompt<\/span> Shows or hides the launched application.<\/p> <\/span><\/p>\n\r If you are collecting stdout and stderr you may not be interested in viewing the application (or the command prompt if it is a console application). This provides you the option to hide the application when it is running.<\/p>\n\r <\/span><\/p>\n\r Be aware that if you hide a command prompt you will not be able to type anything into the application.<\/p>\n\r <\/p>\n\r <\/p>\n\r The option to start collecting data is at the top.<\/p>\n\r <\/p>\n\r •<\/span>Launch<\/span> start your program and attach Coverage Validator to it <\/span><\/p> <\/p>\n\r Double clicking a program in the list will also start it immediately.<\/p>\n\r <\/p>\n\r •<\/span>Cmd Line...<\/span> display the command line builder<\/a> <\/span><\/p> <\/p>\n\r <\/p>\n\r <\/p>\n\r If administrator privileges are required, the Launch button will show the privileges icon reminding you of the need to restart.<\/p>\n\r <\/p>\n\r <\/p>\n\r <\/p>\n\r <\/p>\n\r •<\/span>Launch<\/span> shows the Administrator Privileges Required confirmation dialog before restarting <\/span><\/p> <\/p>\n\r <\/span><\/p>\n\r <\/p>\n\r If you started Coverage Validator in administrator mode, you won\'t see any of these warnings, and everything will behave as normal.<\/p>\n\r <\/p>\n\r <\/p>\n\r <\/p>\n\r <\/p>\n\r The three fields Application to Start<\/span>, Application to Monitor<\/span> and Launch Count<\/span> work together to control which application actually gets monitored by Coverage Validator.<\/p>\n\r <\/p>\n\r Let\'s say we have a program P<\/span>.<\/p>\n\r <\/p>\n\r In the simplest case, simply:<\/p>\n\r <\/p>\n\r •<\/span>start<\/span> P<\/span><\/p>You can easily re-launch the most recently run program<\/a>. <\/h1>\n\r
.Net Core Application Type<\/span><\/h1>\n\r
.Net Core Self Contained Application<\/span><\/h1>\n\r
\n\rThis will typically just be the program that you set to start - unless otherwise specified.<\/p>\n\rSee also: Application to Monitor<\/a> settings<\/h1>\n\r
.Net Core Framework Dependent Application<\/span><\/h1>\n\r
\n\rThis will typically just be the program that you set to start - unless otherwise specified.<\/p>\n\rSee also: Application to Monitor<\/a> settings<\/h1>\n\r
Fields common to all .Net Core applications<\/span><\/h1>\n\r
See also: Launch Count.<\/h1>\n\r
\n\rWhen setting your target program, this will default to the location of the executable<\/p>\n\r
\n\rThese are managed in the Environment Variables Dialog<\/a>.<\/p>\n\r
\n\r <\/span><\/p>\n\r<\/a>Using details from a previous run<\/span><\/h1>\n\r
<\/span><\/h1>\n\r
\n\r <\/p><\/a>Data collection and redirection<\/span><\/h1>\n\r
<\/span><\/h1>\n\r
See the section on controlling data collection<\/a> for how to turn collection on and off after launch. <\/h1>\n\r
<\/span><\/h1>\n\r
The data collection option may be disabled because of the instrumentation mode that is selected<\/a>.<\/h1>\n\r
<\/a>Administrator privileges in dialog mode<\/span><\/h1>\n\r
<\/a>How do I use Application to Monitor and Launch Count?<\/span><\/h1>\n\r