<a name="installation"></a>
<h2>Installation</h2>
<p>If you have not already downloaded NCover, click <a href="http://www.ncover.com/download">here</a>.</p>
<p>After downloading the appropriate installation file (NCover.msi for 32 bit systems or NCover64.msi for 64 bit systems),
double click it to begin the installation. Follow the instructions on screen.</p>
<p>Once installation has been completed, you will be prompted to register NCover. If you have used the program
before to register a valid key, you can skip this step, and begin using NCover. Otherwise, you have two options to complete
registration:
<ul>
<li><strong>Internet Registration:</strong> Enter your product key (click <a href="http://www.ncover.com/user/keys">here</a> if you do
not know your product key, or need a trial key) and click Next.</li>
<li><strong>License File Registration:</strong> License File registration becomes available once the registration program
has tried to register through the internet and failed. The easiest way to force that to happen is to disable your network connection
or unplug the ethernet cable. Once the registration program has failed to register through the internet, you will be sent to
<a href="http://www.ncover.com/keyRegistration">this page</a>,
where you will enter your product key. After clicking Submit, you will be able to download a license file.
In the NCover Registration program, browse to the license file, and complete registration.</li>
</ul>
Congratulations! You are now ready to use NCover.</p>
<a name="console"></a>
<h2>NCover.Console</h2>
<p>From the command line, type
<code>NCover.Console</code>
and press Enter. This will show a list of command line flags.
If you would like an in depth explanation of them, click
<a href="http://docs.ncover.com/ref/2-0/ncover-console/ncover-console-flag-summary">here</a>. As you can see from the
<a href="http://docs.ncover.com/ref/2-0/ncover-console">usage guide</a>,
covering a program is as simple as providing the application to cover as the first argument. For example,
<code>NCover.Console MyApp.exe</code> would run coverage on a program called MyApp.exe in the current directory.</p>
<p>By default, NCover.Console creates an output file in the current directory: Coverage.Xml.
The Xml file contains all of the interesting output about the coverage of your program.</p>
<p>
You can learn more about running NCover.Console in the
<a href="http://docs.ncover.com/ref/2-0/ncover-console/ncover-console-flag-summary">Command Line Flags Reference</a>.
</p>
<a name="explorer"></a>
<h2>NCoverExplorer</h2>
<p>Start NCover.Explorer and press Ctrl+N to open the Run NCover dialog. On this screen, you can browse to an executable
that you would like to profile. We recommend that you check the "Close window & load coverage file after successful run"
checkbox. When all of the sections under Options in the left hand pane are green checkmarks, click Run.
This will execute NCover with the options you specified. If you followed our recommendation, the Run dialog will automatically
close, and the coverage data will be loaded. Otherwise, you can close the dialog yourself and use the Open option from the
File menu to find your coverage report.</p>
<p>After you have loaded the coverage data, there are three important parts of the window. On the left side, all of the
coverage files, assemblies, namespaces, classes, and methods will be listed in a tree structure. The top pane lists the
sequence points contained in whichever segment you have selected in the left. Clicking any sequence points will load
highlighted source code in the bottom frame.</p>
<a name="htmloutput"></a>
<h2>HTML Output</h2>
<p>
A new feature to NCover 2.0, HTML Output allows you and your team to share coverage data from your continuous integration
server.
</p>
<p>
To generate HTML Output from NCover, use the //h option of NCover.Console and specify the directory that you would like the
HTML Output to be written to. For example, <code>NCover.Console MyApp.exe //h report</code> would run run coverage on a program
called MyApp.exe in the current directory, and export html output to a directory named report within the current directory.
</p>