1
<!-- saved from url=(0014)about:internet --><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
3
<!-- Standard Head Part -->
5
<title>NUnit - ProjectEditor</title>
6
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
7
<meta http-equiv="Content-Language" content="en-US">
8
<meta name="norton-safeweb-site-verification" content="tb6xj01p4hgo5x-8wscsmq633y11-e6nhk-bnb5d987bseanyp6p0uew-pec8j963qlzj32k5x9h3r2q7wh-vmy8bbhek5lnpp5w4p8hocouuq39e09jrkihdtaeknua" />
9
<link rel="stylesheet" type="text/css" href="nunit.css">
10
<link rel="shortcut icon" href="favicon.ico">
12
<!-- End Standard Head Part -->
16
<!-- Standard Header for NUnit.org -->
18
<a id="logo" href="http://www.nunit.org"><img src="img/logo.gif" alt="NUnit.org" title="NUnit.org"></a>
1
<!-- saved from url=(0014)about:internet --><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN">
3
<!-- Standard Head Part -->
5
<title>NUnit - ProjectEditor</title>
6
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
7
<meta http-equiv="Content-Language" content="en-US">
8
<meta name="norton-safeweb-site-verification" content="tb6xj01p4hgo5x-8wscsmq633y11-e6nhk-bnb5d987bseanyp6p0uew-pec8j963qlzj32k5x9h3r2q7wh-vmy8bbhek5lnpp5w4p8hocouuq39e09jrkihdtaeknua" />
9
<link rel="stylesheet" type="text/css" href="nunit.css">
10
<link rel="shortcut icon" href="favicon.ico">
12
<!-- End Standard Head Part -->
16
<!-- Standard Header for NUnit.org -->
18
<a id="logo" href="http://www.nunit.org"><img src="img/logo.gif" alt="NUnit.org" title="NUnit.org"></a>
20
20
<a href="http://www.nunit.org">NUnit</a>
21
21
<a class="active" href="index.html">Documentation</a>
24
<!-- End of Header -->
28
<h2>Project Editor</h2>
30
<p>Beginning with NUnit 2.6, the Project Editor is a separate program, which may be executed
31
directly or run through the Project | Edit dropdown menu of the NUnit GUI. The editor now
32
provides two main views of the project: a property-oriented view based on the Project Editor
33
that was built into earlier versions of the NUnit GUI and an xml view, which allows direct
34
editing of the .nunit file.
36
<h2>Property View</h2>
38
<p>This view consists of a common area and two tabs, as seen in the image below.</p>
40
<div class="screenshot-left">
41
<img src="img/generalTab.jpg"></div>
45
<p>The common area of the Project Editor contains information pertaining to
46
the project as a whole. Information that applies to a particular configuration
47
is displayed in the General and Assemblies tabs.
50
<p>This label shows the full path to the project file. In the case of a
51
wrapper project, the path is set to the same directory as the assembly
52
that was initially opened.
54
<h4>Application Base</h4>
55
<p>This TextBox allows the user to change the project AppBase, which defaults to
56
the directory of the project file. The button to the right of the TextBox
57
allows the user to browse and select a directory.
59
<h4>Process Model</h4>
60
<p>This dropdown list allows you to specify how operating system processes are
61
used in loading and running the tests in this project. Four settings are
64
<li>The <b>Default</b> setting refers to the option selected by the user
65
on the Assembly Isolation page of the NUnit Settings Dialog.
66
<li><b>Single</b> means that tests are run in a test domain in the
67
same process as NUnit. This is the way previous versions of NUnit
69
<li><b>Separate</b> means that all the tests are run in a separate process
71
<li><b>Multiple</b> means that NUnit will create a separate process for
72
each test assembly in the project and run its tests there.
76
<p>This dropdown list allows you to specify how tests are loaded into
77
AppDomains by NUnit. Three settings are defined:
79
<li>The <b>Default</b> setting refers to the option selected by the user
80
on the Assembly Isolation page of the NUnit Settings Dialog.
81
<li><b>Single</b> means that all tests will run in a single test domain
82
created by NUnit. This was the way versions of NUnit prior to 2.4
84
<li><b>Multiple</b> means that each test assembly is loaded into a
85
separate AppDomain. This setting is not available when Multiple
86
processes are selected in the Process Model dropown.
89
<h4>Configuration</h4>
90
<p>This dropdown list allows you to select the particular configuration
91
within a project that is displayed in the bottom part of the dialog.
93
<h4>Edit Configs...</h4>
94
<p>This button opens the
95
<a href="configEditor.html">Configuration Editor</a>,
96
which allows you to add, delete or rename configs and set the
101
<p>The General tab allows setting a number of options pertaining to the selected configuration, all of
102
which will be stored in the NUnit project file as attributes of the <config> xml node.</p>
105
<p>This dropdown allows you to select a particular runtime framework to be used
106
for loading and running tests under the current configuration. Currently,
107
only Microsoft .NET and Mono are supported. If <b>Any</b> is selected, the
108
tests will be run under the same runtime that NUnit itself is currently using.
111
<p>This ComboBox allows you to select the particular version of the runtime framework
112
to be used for loading and running tests under the current configuration. The
113
dropdown list contains entries for
122
<p>If you select "Default" the assemblies in the project are examined to determine
123
the version that is required.
124
See <a href="runtimeSelection.html">Runtime Selection</a> for
125
more information on how NUnit selects the version to be used.
127
<p>In special cases, you may wish to enter a version number that is not listed
128
in the list box. You may specify the version using two, three or four
129
components. The version you provide will be saved as you enter it. Leaving
130
the text box blank is equivalent to selecting "Default."
132
<p><b>Note:</b> Running tests under a different runtime or version from the one that NUnit
133
is currently using will force them to run in a separate process.
135
<p><b>Note:</b> To conform with normal usage, specifying Mono as the runtime
136
with "1.0" as the version results in use of the Mono 1.0 profile, equating
139
<h4>ApplicationBase</h4>
140
<p>The ApplicationBase defaults to the directory containing the project file. Beginning
141
with NUnit 2.2.3, it may be set to any location that is desired.</p>
143
<h4>Configuration File Name</h4>
144
<p>The configuration file defaults to the name of the test project with the extension changed
145
from .nunit to .config. The user may substitute another name.</p>
147
<h4>PrivateBinPath</h4>
148
<p>By default, the PrivateBinPath is generated from the assembly locations specified on the
149
Assemblies Tab. For those applications requiring a different level of control, it may be
150
specified manually or using this editor or placed in the configuration file.</p>
152
<h3>Assemblies Tab</h3>
154
<p>The assemblies tab contains the list of assemblies that form part of this test project.</p>
156
<p>Note: Although the dialog shows the location of assemblies as absolute paths, they are always
157
persisted in the NUnit project file as paths relative to the application base. This allows moving
158
projects as a whole to a different directory location.</p>
160
<div class="screenshot-left">
161
<img src="img/assembliesTab.jpg"></div>
164
<p>Opens a dialog allowing adding an assembly to this configuration. If Visual
165
Stuio support is enabled, you may also select and add a VS project.</p>
168
<p>After confirmation, removes the selected assembly from this configuration.</p>
170
<h4>Assembly Path</h4>
171
<p>This text box displays the full path to the selected assembly. You may edit
172
the contents to change the path to the assembly.
176
<p>This view simply displays the XML from the project file, as seen here. You may
177
edit the XML directly.</p>
179
<div class="screenshot-left">
180
<img src="img/xmlView.jpg"></div>
182
<p><b>Note:</b> In this version of NUnit, the XML editor is somewhat primitive.
183
Errors in XML formatting are caught and an error message displayed. However,
184
the values of attributes are not validated as they are in the property-based
185
view and it is possible to create a project file, which NUnit is unable to
186
load. Improvements, including intellisense and better error handling, are
187
planned in future versions of the Project Editor.
196
<li><a href="index.html">NUnit 2.6</a></li>
198
<li><a href="getStarted.html">Getting Started</a></li>
199
<li><a href="writingTests.html">Writing Tests</a></li>
200
<li><a href="runningTests.html">Running Tests</a></li>
202
<li><a href="nunit-console.html">Console Runner</a></li>
203
<li><a href="nunit-gui.html">Gui Runner</a></li>
204
<li><a href="pnunit.html">PNUnit Runner</a></li>
205
<li><a href="nunit-agent.html">NUnit Agent</a></li>
206
<li id="current"><a href="projectEditor.html">Project Editor</a></li>
207
<li><a href="runtimeSelection.html">Runtime Selection</a></li>
208
<li><a href="assemblyIsolation.html">Assembly Isolation</a></li>
209
<li><a href="configFiles.html">Configuration Files</a></li>
210
<li><a href="multiAssembly.html">Multiple Assemblies</a></li>
211
<li><a href="vsSupport.html">Visual Studio Support</a></li>
213
<li><a href="extensibility.html">Extensibility</a></li>
214
<li><a href="releaseNotes.html">Release Notes</a></li>
215
<li><a href="samples.html">Samples</a></li>
216
<li><a href="license.html">License</a></li>
218
<li><a href="vsTestAdapter.html">NUnit Test Adapter 0.90</a></li>
220
<li><a href="vsTestAdapterLicense.html">License</a></li>
222
<li><a href="&r=2.6.html"></a></li>
223
<li><a href="&r=2.6.html"></a></li>
226
<!-- End of Submenu -->
229
<!-- Standard Footer for NUnit.org -->
231
Copyright © 2012 Charlie Poole. All Rights Reserved.
233
<!-- End of Footer -->
24
<!-- End of Header -->
28
<h2>Project Editor</h2>
30
<p>Beginning with NUnit 2.6, the Project Editor is a separate program, which may be executed
31
directly or run through the Project | Edit dropdown menu of the NUnit GUI. The editor now
32
provides two main views of the project: a property-oriented view based on the Project Editor
33
that was built into earlier versions of the NUnit GUI and an xml view, which allows direct
34
editing of the .nunit file.
36
<h2>Property View</h2>
38
<p>This view consists of a common area and two tabs, as seen in the image below.</p>
40
<div class="screenshot-left">
41
<img src="img/generalTab.jpg"></div>
45
<p>The common area of the Project Editor contains information pertaining to
46
the project as a whole. Information that applies to a particular configuration
47
is displayed in the General and Assemblies tabs.
50
<p>This label shows the full path to the project file. In the case of a
51
wrapper project, the path is set to the same directory as the assembly
52
that was initially opened.
54
<h4>Application Base</h4>
55
<p>This TextBox allows the user to change the project AppBase, which defaults to
56
the directory of the project file. The button to the right of the TextBox
57
allows the user to browse and select a directory.
59
<h4>Process Model</h4>
60
<p>This dropdown list allows you to specify how operating system processes are
61
used in loading and running the tests in this project. Four settings are
64
<li>The <b>Default</b> setting refers to the option selected by the user
65
on the Assembly Isolation page of the NUnit Settings Dialog.
66
<li><b>Single</b> means that tests are run in a test domain in the
67
same process as NUnit. This is the way previous versions of NUnit
69
<li><b>Separate</b> means that all the tests are run in a separate process
71
<li><b>Multiple</b> means that NUnit will create a separate process for
72
each test assembly in the project and run its tests there.
76
<p>This dropdown list allows you to specify how tests are loaded into
77
AppDomains by NUnit. Three settings are defined:
79
<li>The <b>Default</b> setting refers to the option selected by the user
80
on the Assembly Isolation page of the NUnit Settings Dialog.
81
<li><b>Single</b> means that all tests will run in a single test domain
82
created by NUnit. This was the way versions of NUnit prior to 2.4
84
<li><b>Multiple</b> means that each test assembly is loaded into a
85
separate AppDomain. This setting is not available when Multiple
86
processes are selected in the Process Model dropown.
89
<h4>Configuration</h4>
90
<p>This dropdown list allows you to select the particular configuration
91
within a project that is displayed in the bottom part of the dialog.
93
<h4>Edit Configs...</h4>
94
<p>This button opens the
95
<a href="configEditor.html">Configuration Editor</a>,
96
which allows you to add, delete or rename configs and set the
101
<p>The General tab allows setting a number of options pertaining to the selected configuration, all of
102
which will be stored in the NUnit project file as attributes of the <config> xml node.</p>
105
<p>This dropdown allows you to select a particular runtime framework to be used
106
for loading and running tests under the current configuration. Currently,
107
only Microsoft .NET and Mono are supported. If <b>Any</b> is selected, the
108
tests will be run under the same runtime that NUnit itself is currently using.
111
<p>This ComboBox allows you to select the particular version of the runtime framework
112
to be used for loading and running tests under the current configuration. The
113
dropdown list contains entries for
122
<p>If you select "Default" the assemblies in the project are examined to determine
123
the version that is required.
124
See <a href="runtimeSelection.html">Runtime Selection</a> for
125
more information on how NUnit selects the version to be used.
127
<p>In special cases, you may wish to enter a version number that is not listed
128
in the list box. You may specify the version using two, three or four
129
components. The version you provide will be saved as you enter it. Leaving
130
the text box blank is equivalent to selecting "Default."
132
<p><b>Note:</b> Running tests under a different runtime or version from the one that NUnit
133
is currently using will force them to run in a separate process.
135
<p><b>Note:</b> To conform with normal usage, specifying Mono as the runtime
136
with "1.0" as the version results in use of the Mono 1.0 profile, equating
139
<h4>ApplicationBase</h4>
140
<p>The ApplicationBase defaults to the directory containing the project file. Beginning
141
with NUnit 2.2.3, it may be set to any location that is desired.</p>
143
<h4>Configuration File Name</h4>
144
<p>The configuration file defaults to the name of the test project with the extension changed
145
from .nunit to .config. The user may substitute another name.</p>
147
<h4>PrivateBinPath</h4>
148
<p>By default, the PrivateBinPath is generated from the assembly locations specified on the
149
Assemblies Tab. For those applications requiring a different level of control, it may be
150
specified manually or using this editor or placed in the configuration file.</p>
152
<h3>Assemblies Tab</h3>
154
<p>The assemblies tab contains the list of assemblies that form part of this test project.</p>
156
<p>Note: Although the dialog shows the location of assemblies as absolute paths, they are always
157
persisted in the NUnit project file as paths relative to the application base. This allows moving
158
projects as a whole to a different directory location.</p>
160
<div class="screenshot-left">
161
<img src="img/assembliesTab.jpg"></div>
164
<p>Opens a dialog allowing adding an assembly to this configuration. If Visual
165
Stuio support is enabled, you may also select and add a VS project.</p>
168
<p>After confirmation, removes the selected assembly from this configuration.</p>
170
<h4>Assembly Path</h4>
171
<p>This text box displays the full path to the selected assembly. You may edit
172
the contents to change the path to the assembly.
176
<p>This view simply displays the XML from the project file, as seen here. You may
177
edit the XML directly.</p>
179
<div class="screenshot-left">
180
<img src="img/xmlView.jpg"></div>
182
<p><b>Note:</b> In this version of NUnit, the XML editor is somewhat primitive.
183
Errors in XML formatting are caught and an error message displayed. However,
184
the values of attributes are not validated as they are in the property-based
185
view and it is possible to create a project file, which NUnit is unable to
186
load. Improvements, including intellisense and better error handling, are
187
planned in future versions of the Project Editor.
196
<li><a href="index.html">NUnit 2.6.3</a></li>
198
<li><a href="getStarted.html">Getting Started</a></li>
199
<li><a href="writingTests.html">Writing Tests</a></li>
200
<li><a href="runningTests.html">Running Tests</a></li>
202
<li><a href="nunit-console.html">Console Runner</a></li>
203
<li><a href="nunit-gui.html">Gui Runner</a></li>
204
<li><a href="pnunit.html">PNUnit Runner</a></li>
205
<li><a href="nunit-agent.html">NUnit Agent</a></li>
206
<li id="current"><a href="projectEditor.html">Project Editor</a></li>
207
<li><a href="runtimeSelection.html">Runtime Selection</a></li>
208
<li><a href="assemblyIsolation.html">Assembly Isolation</a></li>
209
<li><a href="configFiles.html">Configuration Files</a></li>
210
<li><a href="multiAssembly.html">Multiple Assemblies</a></li>
211
<li><a href="vsSupport.html">Visual Studio Support</a></li>
213
<li><a href="extensibility.html">Extensibility</a></li>
214
<li><a href="releaseNotes.html">Release Notes</a></li>
215
<li><a href="samples.html">Samples</a></li>
216
<li><a href="license.html">License</a></li>
218
<li><a href="vsTestAdapter.html">NUnit Test Adapter</a></li>
220
<li><a href="vsTestAdapterLicense.html">License</a></li>
221
<li><a href="vsTestAdapterReleaseNotes.html">Release Notes</a></li>
223
<li><a href="&r=2.6.3.html"></a></li>
224
<li><a href="&r=2.6.3.html"></a></li>
227
<!-- End of Submenu -->
230
<!-- Standard Footer for NUnit.org -->
232
Copyright © 2012 Charlie Poole. All Rights Reserved.
234
<!-- End of Footer -->
added
removed
doc/projectEditor.html
