Custom LabVIEW configuration file - Revision history

Q: Category reorg

2020-05-08T19:59:47Z

Category reorg

← Older revision		Revision as of 19:59, 8 May 2020
Line 54:		Line 54:

	[[Category:Configuration File\|Custom]]		[[Category:Configuration File\|Custom]]
	~~[[Category:Development Environment]]~~

Logmanoriginal: Fix category assignment

2020-04-10T10:01:00Z

Fix category assignment

← Older revision		Revision as of 10:01, 10 April 2020
Line 54:		Line 54:

	[[Category:Configuration File\|Custom]]		[[Category:Configuration File\|Custom]]
	[[Category:Development ~~environment~~]]		[[Category:Development Environment]]

Michael_Aivaliotis: added dev. env. category.

2009-02-10T00:23:25Z

added dev. env. category.

Tcplomp: Added config file category

2009-02-09T10:52:58Z

Added config file category

← Older revision		Revision as of 10:52, 9 February 2009
Line 1:		Line 1:
	'''''In the following, project has a pre-LabVIEW 8 meaning e.g. a collection of related VIs'''''		'''''In the following, project has a pre-LabVIEW 8 meaning e.g. a collection of related VIs'''''

	== '''~~Customize LabVIEW.ini to your project~~''' ==		'''''{{TOCright}}'''''

	~~The~~ LabVIEW ~~Preference file is stored by default in the LabVIEW installation directory. Often LabVIEW developers use only this default labview~~.ini ~~for all their projects, ignoring the benefits of having one preference file for each~~ project~~. Maybe this is due to the fact that it is not straightforward to open LabVIEW with a specific ini file.~~		== '''Customize LabVIEW.ini to your project''' ==

	~~=='''Using~~ LabVIEW with a ~~custom~~ ini file~~'''==~~		The LabVIEW Preference file is stored by default in the LabVIEW installation directory. Often LabVIEW developers use only this default labview.ini for all their projects, ignoring the benefits of having one preference file for each project. Maybe this is due to the fact that it is not straightforward to open LabVIEW with a specific ini file.

	==='''~~Command Line~~'''===		== '''Using LabVIEW with a custom ini file''' ==
	~~From the command line you have to specify the ini file with the -pref switch:~~

	~~[code]"c:\Program Files\National Instruments\LabVIEW 8.2\LabVIEW.exe" -pref "c:\MyProject\labview.ini"[/code]~~		=== '''Command Line''' ===

			From the command line you have to specify the ini file with the -pref switch:
			<!--c1--><div class="codetop">CODE</div><div class="codemain"><!--ec1-->"c:\Program Files\National Instruments\LabVIEW 8.2\LabVIEW.exe" -pref "c:\MyProject\labview.ini"<!--c2--></div><!--ec2-->
	This is not a very convenient method to start LabVIEW.		This is not a very convenient method to start LabVIEW.

	==='''Shortcuts'''===		=== '''Shortcuts''' ===

	Another method is to create a shortcut with the above command line. For each project edit a different shortcut specifying the ini file. This is far more convenient than the command line		Another method is to create a shortcut with the above command line. For each project edit a different shortcut specifying the ini file. This is far more convenient than the command line

	==='''Custom file extensions'''===		=== '''Custom file extensions''' ===
	Create a custom file extensions for LabVIEW ini files. Change the file extension of the preference file to something like *.lv82ini. Then in Windows create this file extension specifying the following action:
			Create a custom file extensions for LabVIEW ini files. Change the file extension of the preference file to something like *.lv82ini. Then in Windows create this file extension specifying the following action:
			<!--c1--><div class="codetop">CODE</div><div class="codemain"><!--ec1-->"c:\Program Files\National Instruments\LabVIEW 8.2\LabVIEW.exe" -pref "%L"<!--c2--></div><!--ec2-->
			With this setup you can start LabVIEW with a custom ini file just by double clicking on the lv82ini file of the project. If you work with more than one version of LabVIEW, create one file extension for each version like .lv80ini and .lv71ini with actions using the corresponding LabVIEW executable. That allows to conveniently start with the LabVIEW version and the preference file of the project.

			Already invoking LabVIEW from a shortcut or an action on a file extension, we can also make the command to run a VI. For example, setting the file extension action to run
			<!--c1--><div class="codetop">CODE</div><div class="codemain"><!--ec1-->"c:\Program Files\National Instruments\LabVIEW 8.2\LabVIEW.exe" "c:\tools\lv_start.vi" -pref "%L"<!--c2--></div><!--ec2-->
			will open the VI lv_start.vi when launching LabVIEW from a preference file. That VI, set to run when opened, can execute any suitable initialization task and load/run VIs specific to the project looking into the project directory (see below).

	~~[code]"c:\Program Files\National Instruments\LabVIEW 8.2\LabVIEW.exe" -pref "%L"[/code]~~		== '''Benefits of a custom ini file''' ==

	With this setup you can start LabVIEW with a custom ini file just by double clicking on the lv82ini file of the project. If you work with more than one version of LabVIEW, create one file extension for each version like .lv80ini and .lv71ini with actions using the corresponding LabVIEW executable. That allows to conveniently start with the LabVIEW version and the preference file of the project.		=== '''Default Path''' ===

	~~Already invoking~~ LabVIEW ~~from a shortcut or an action on a~~ file ~~extension, we can also make~~ the ~~command~~ to ~~run a VI~~. ~~For example~~, setting the ~~file extension action to run~~		The first thing to do using an ini file customized for your project is to set the default path setting to the project root path. You will soon realize that the file dialogs will show your project path as the startup directory rather than the LabVIEW directory. The file constant "Default Directory" will return the project directory so it is easy to build paths relative to the project directory without harcoding it. If you move the project folder, only change the default directory setting and relative paths will change accordingly. Moreover, in a built application, this default directory will default to the application directory so you can keep the same directory structure and relative paths in the built application without changing the code or checking if the application runs in Development or Run-Time LabVIEW.

	~~[code]"c:\Program Files\National Instruments\LabVIEW 8.2\LabVIEW.exe" "c:\tools\lv_start.vi" -pref "%L"[/code]~~		=== '''Browse history''' ===

	~~will open~~ the ~~VI lv_start.vi when launching LabVIEW from a preference~~ file. ~~That VI, set~~ to ~~run when~~ opened~~, can execute any suitable initialization task and load/run VIs specific to the~~ project ~~looking into the~~ project ~~directory (see below)~~.		The browse history (recently opened files and used directories) is stored in the ini file. Custom ini files allow to keep a different history for each project so in the list of recently opened files you see files opened whitin this project rather than files opened in an unrelated project.

	=='''~~Benefits of a custom ini file~~'''==		=== '''Source Code Control (SCC)''' ===

	~~==='''Default Path'''===~~		Since LabVIEW 8 SCC settings are stored in the preference file. Customized ini files then allow to have different SCC settings and providers for different projects. In LabVIEW 7.1 and before, SCC settings are stored in files kept in the default directory so if you take care of setting the default directory to the project directory, you can also have different SCC setting for each project. LabVIEW 8.5 (and up) gives the ability to use .lvproj dependent SCC settings.
	~~The first thing~~ to ~~do using an ini file customized~~ for ~~your project is to set the default path setting to the project root path~~. ~~You will soon realize that the file dialogs will show your project path as the startup directory rather than the~~ LabVIEW ~~directory~~. ~~The file constant "Default Directory" will return~~ the ~~project~~ directory so ~~it is easy to build paths relative to the project directory without harcoding it. If~~ you ~~move~~ the ~~project folder, only change the default directory setting and relative paths will change accordingly. Moreover, in a built application, this~~ default directory ~~will default~~ to the ~~application~~ directory so you can ~~keep the same directory structure~~ and ~~relative paths in~~ the ~~built application without changing the code or checking if the application runs in Development or Run-Time LabVIEW~~.

	==='''~~Browse history~~'''===		=== '''Other Project dependent Settings''' ===
	The browse history (recently opened files and used directories) is stored in the ini file. Custom ini files allow to keep a different history for each project so in the list of recently opened files you see files opened whitin this project rather than files opened in an unrelated project.

	~~==='''Source Code Control (SCC)'''===~~		Other settings might be project dependent like the palettes, search paths, decimal separator etc. All these can be set independantly for each project.
	~~Since LabVIEW 8 SCC~~ settings ~~are stored in~~ the ~~preference file. Customized ini files then allow to have different SCC settings and providers for different projects. In LabVIEW 7.1 and before~~, ~~SCC settings are stored in files kept in the default directory so if you take care of setting the default directory to the project directory~~, ~~you~~ can ~~also have different SCC setting~~ for each project.
	~~LabVIEW 8.5 (and up) gives the ability to use .lvproj dependent SCC settings~~.

	~~==='''Other~~ Project ~~dependent Settings'''===~~		The Project custom ini file is typically stored in the project directory and can be copied from the default labview.ini or from some convenient template. It is also logical to keep this file under SCC to make sure that LabVIEW is correctly configured for the project usage. For example, using an incorrect decimal separator setting can easily break an application.
	~~Other settings might~~ be project ~~dependent like the palettes, search paths~~, decimal separator ~~etc. All these~~ can ~~be set independantly for each project~~.

	The Project custom ini file is typically stored in the project directory and can be copied from the default labview.ini or from some convenient template. It is also logical to keep this file under SCC to make sure that LabVIEW is correctly configured for the project usage. For example, using an incorrect decimal separator setting can easily break an application.		== See Also ==

	~~== See Also ==~~
	[[LabVIEW configuration file]]		[[LabVIEW configuration file]]
	[[Category:~~Development Environment~~]]
			[[Category:Configuration_File\|Custom]]

Ddefriese: /* '''Customize LabVIEW.ini to your project''' */

2008-11-27T18:58:00Z

'''Customize LabVIEW.ini to your project'''

← Older revision		Revision as of 18:58, 27 November 2008
Line 3:		Line 3:
	== '''Customize LabVIEW.ini to your project''' ==		== '''Customize LabVIEW.ini to your project''' ==

	The LabVIEW Preference file is stored by default in the LabVIEW installation directory. Often LabVIEW ~~developpers~~ use only this default labview.ini for all their projects, ignoring the benefits of having one preference file for each project. Maybe this is due to the fact that it is not straightforward to open LabVIEW with a specific ini file.		The LabVIEW Preference file is stored by default in the LabVIEW installation directory. Often LabVIEW developers use only this default labview.ini for all their projects, ignoring the benefits of having one preference file for each project. Maybe this is due to the fact that it is not straightforward to open LabVIEW with a specific ini file.

	=='''Using LabVIEW with a custom ini file'''==		=='''Using LabVIEW with a custom ini file'''==

Tcplomp: /* '''Source Code Control (SCC)''' */

2008-10-02T18:45:51Z

'''Source Code Control (SCC)'''

← Older revision		Revision as of 18:45, 2 October 2008
Line 40:		Line 40:
	==='''Source Code Control (SCC)'''===		==='''Source Code Control (SCC)'''===
	Since LabVIEW 8 SCC settings are stored in the preference file. Customized ini files then allow to have different SCC settings and providers for different projects. In LabVIEW 7.1 and before, SCC settings are stored in files kept in the default directory so if you take care of setting the default directory to the project directory, you can also have different SCC setting for each project.		Since LabVIEW 8 SCC settings are stored in the preference file. Customized ini files then allow to have different SCC settings and providers for different projects. In LabVIEW 7.1 and before, SCC settings are stored in files kept in the default directory so if you take care of setting the default directory to the project directory, you can also have different SCC setting for each project.
			LabVIEW 8.5 (and up) gives the ability to use .lvproj dependent SCC settings.

	==='''Other Project dependent Settings'''===		==='''Other Project dependent Settings'''===

MichaelAivaliotis at 08:34, 7 May 2007

2007-05-07T08:34:17Z

← Older revision		Revision as of 08:34, 7 May 2007
Line 45:		Line 45:

	The Project custom ini file is typically stored in the project directory and can be copied from the default labview.ini or from some convenient template. It is also logical to keep this file under SCC to make sure that LabVIEW is correctly configured for the project usage. For example, using an incorrect decimal separator setting can easily break an application.		The Project custom ini file is typically stored in the project directory and can be copied from the default labview.ini or from some convenient template. It is also logical to keep this file under SCC to make sure that LabVIEW is correctly configured for the project usage. For example, using an incorrect decimal separator setting can easily break an application.

			== See Also ==
			[[LabVIEW configuration file]]
	[[Category:Development Environment]]		[[Category:Development Environment]]

MichaelAivaliotis: LabVIEW ini File moved to Custom LabVIEW configuration file: initial title was too generic and contained the word ini.

2007-05-07T08:25:55Z

LabVIEW ini File moved to Custom LabVIEW configuration file: initial title was too generic and contained the word ini.

← Older revision	Revision as of 08:25, 7 May 2007
(No difference)

MichaelAivaliotis: Cosmetic changes

2007-04-05T08:47:51Z

Cosmetic changes

MichaelAivaliotis at 14:55, 4 April 2007

2007-04-04T14:55:48Z

← Older revision		Revision as of 14:55, 4 April 2007
Line 1:		Line 1:
			'''''In the following, project has a pre-LabVIEW 8 meaning e.g. a collection of related VIs'''''

	== '''Customize LabVIEW.ini to your project''' ==		== '''Customize LabVIEW.ini to your project''' ==

	~~''In the following, project has a pre-LabVIEW 8 meaning e.g. a collection of related VIs''~~

	The LabVIEW Preference file is stored by default in the LabVIEW installation directory. Often LabVIEW developpers use only this default labview.ini for all their projects, ignoring the benefits of having one preference file for each project. Maybe this is due to the fact that it is not straightforward to open LabVIEW with a specific ini file.		The LabVIEW Preference file is stored by default in the LabVIEW installation directory. Often LabVIEW developpers use only this default labview.ini for all their projects, ignoring the benefits of having one preference file for each project. Maybe this is due to the fact that it is not straightforward to open LabVIEW with a specific ini file.

← Older revision		Revision as of 00:23, 10 February 2009
Line 1:		Line 1:
	'''''In the following, project has a pre-LabVIEW 8 meaning e.g. a collection of related VIs'''''		'''''In the following, project has a pre-LabVIEW 8 meaning e.g. a collection of related VIs'''''

	'''''{{TOCright}}'''''		'''''{{TOCright}}'''''
Line 5:		Line 5:
	== '''Customize LabVIEW.ini to your project''' ==		== '''Customize LabVIEW.ini to your project''' ==

	The LabVIEW Preference file is stored by default in the LabVIEW installation directory. Often LabVIEW developers use only this default labview.ini for all their projects, ignoring the benefits of having one preference file for each project. Maybe this is due to the fact that it is not straightforward to open LabVIEW with a specific ini file.		The LabVIEW Preference file is stored by default in the LabVIEW installation directory. Often LabVIEW developers use only this default labview.ini for all their projects, ignoring the benefits of having one preference file for each project. Maybe this is due to the fact that it is not straightforward to open LabVIEW with a specific ini file.

	== '''Using LabVIEW with a custom ini file''' ==		== '''Using LabVIEW with a custom ini file''' ==
Line 11:		Line 11:
	=== '''Command Line''' ===		=== '''Command Line''' ===

	From the command line you have to specify the ini file with the -pref switch:		From the command line you have to specify the ini file with the -pref switch:
	<!--c1--><div class="codetop">CODE</div><div class="codemain"><!--ec1-->"c:\Program Files\National Instruments\LabVIEW 8.2\LabVIEW.exe" -pref "c:\MyProject\labview.ini"<!--c2--></div><!--ec2-->		<!--c1--><div class="codetop">CODE</div><div class="codemain"><!--ec1-->"c:\Program Files\National Instruments\LabVIEW 8.2\LabVIEW.exe" -pref "c:\MyProject\labview.ini"<!--c2--></div><!--ec2-->
	This is not a very convenient method to start LabVIEW.		This is not a very convenient method to start LabVIEW.

	=== '''Shortcuts''' ===		=== '''Shortcuts''' ===

	Another method is to create a shortcut with the above command line. For each project edit a different shortcut specifying the ini file. This is far more convenient than the command line		Another method is to create a shortcut with the above command line. For each project edit a different shortcut specifying the ini file. This is far more convenient than the command line

	=== '''Custom file extensions''' ===		=== '''Custom file extensions''' ===

	Create a custom file extensions for LabVIEW ini files. Change the file extension of the preference file to something like *.lv82ini. Then in Windows create this file extension specifying the following action:		Create a custom file extensions for LabVIEW ini files. Change the file extension of the preference file to something like *.lv82ini. Then in Windows create this file extension specifying the following action:
	<!--c1--><div class="codetop">CODE</div><div class="codemain"><!--ec1-->"c:\Program Files\National Instruments\LabVIEW 8.2\LabVIEW.exe" -pref "%L"<!--c2--></div><!--ec2-->		<!--c1--><div class="codetop">CODE</div><div class="codemain"><!--ec1-->"c:\Program Files\National Instruments\LabVIEW 8.2\LabVIEW.exe" -pref "%L"<!--c2--></div><!--ec2-->
	With this setup you can start LabVIEW with a custom ini file just by double clicking on the lv82ini file of the project. If you work with more than one version of LabVIEW, create one file extension for each version like .lv80ini and .lv71ini with actions using the corresponding LabVIEW executable. That allows to conveniently start with the LabVIEW version and the preference file of the project.		With this setup you can start LabVIEW with a custom ini file just by double clicking on the lv82ini file of the project. If you work with more than one version of LabVIEW, create one file extension for each version like .lv80ini and .lv71ini with actions using the corresponding LabVIEW executable. That allows to conveniently start with the LabVIEW version and the preference file of the project.

	Already invoking LabVIEW from a shortcut or an action on a file extension, we can also make the command to run a VI. For example, setting the file extension action to run		Already invoking LabVIEW from a shortcut or an action on a file extension, we can also make the command to run a VI. For example, setting the file extension action to run
	<!--c1--><div class="codetop">CODE</div><div class="codemain"><!--ec1-->"c:\Program Files\National Instruments\LabVIEW 8.2\LabVIEW.exe" "c:\tools\lv_start.vi" -pref "%L"<!--c2--></div><!--ec2-->		<!--c1--><div class="codetop">CODE</div><div class="codemain"><!--ec1-->"c:\Program Files\National Instruments\LabVIEW 8.2\LabVIEW.exe" "c:\tools\lv_start.vi" -pref "%L"<!--c2--></div><!--ec2-->
	will open the VI lv_start.vi when launching LabVIEW from a preference file. That VI, set to run when opened, can execute any suitable initialization task and load/run VIs specific to the project looking into the project directory (see below).		will open the VI lv_start.vi when launching LabVIEW from a preference file. That VI, set to run when opened, can execute any suitable initialization task and load/run VIs specific to the project looking into the project directory (see below).

	== '''Benefits of a custom ini file''' ==		== '''Benefits of a custom ini file''' ==
Line 33:		Line 33:
	=== '''Default Path''' ===		=== '''Default Path''' ===

	The first thing to do using an ini file customized for your project is to set the default path setting to the project root path. You will soon realize that the file dialogs will show your project path as the startup directory rather than the LabVIEW directory. The file constant "Default Directory" will return the project directory so it is easy to build paths relative to the project directory without harcoding it. If you move the project folder, only change the default directory setting and relative paths will change accordingly. Moreover, in a built application, this default directory will default to the application directory so you can keep the same directory structure and relative paths in the built application without changing the code or checking if the application runs in Development or Run-Time LabVIEW.		The first thing to do using an ini file customized for your project is to set the default path setting to the project root path. You will soon realize that the file dialogs will show your project path as the startup directory rather than the LabVIEW directory. The file constant "Default Directory" will return the project directory so it is easy to build paths relative to the project directory without harcoding it. If you move the project folder, only change the default directory setting and relative paths will change accordingly. Moreover, in a built application, this default directory will default to the application directory so you can keep the same directory structure and relative paths in the built application without changing the code or checking if the application runs in Development or Run-Time LabVIEW.

	=== '''Browse history''' ===		=== '''Browse history''' ===

	The browse history (recently opened files and used directories) is stored in the ini file. Custom ini files allow to keep a different history for each project so in the list of recently opened files you see files opened whitin this project rather than files opened in an unrelated project.		The browse history (recently opened files and used directories) is stored in the ini file. Custom ini files allow to keep a different history for each project so in the list of recently opened files you see files opened whitin this project rather than files opened in an unrelated project.

	=== '''Source Code Control (SCC)''' ===		=== '''Source Code Control (SCC)''' ===

	Since LabVIEW 8 SCC settings are stored in the preference file. Customized ini files then allow to have different SCC settings and providers for different projects. In LabVIEW 7.1 and before, SCC settings are stored in files kept in the default directory so if you take care of setting the default directory to the project directory, you can also have different SCC setting for each project. LabVIEW 8.5 (and up) gives the ability to use .lvproj dependent SCC settings.		Since LabVIEW 8 SCC settings are stored in the preference file. Customized ini files then allow to have different SCC settings and providers for different projects. In LabVIEW 7.1 and before, SCC settings are stored in files kept in the default directory so if you take care of setting the default directory to the project directory, you can also have different SCC setting for each project. LabVIEW 8.5 (and up) gives the ability to use .lvproj dependent SCC settings.

	=== '''Other Project dependent Settings''' ===		=== '''Other Project dependent Settings''' ===

	Other settings might be project dependent like the palettes, search paths, decimal separator etc. All these can be set independantly for each project.		Other settings might be project dependent like the palettes, search paths, decimal separator etc. All these can be set independantly for each project.

	The Project custom ini file is typically stored in the project directory and can be copied from the default labview.ini or from some convenient template. It is also logical to keep this file under SCC to make sure that LabVIEW is correctly configured for the project usage. For example, using an incorrect decimal separator setting can easily break an application.		The Project custom ini file is typically stored in the project directory and can be copied from the default labview.ini or from some convenient template. It is also logical to keep this file under SCC to make sure that LabVIEW is correctly configured for the project usage. For example, using an incorrect decimal separator setting can easily break an application.

	== See Also ==		== See Also ==
Line 53:		Line 53:
	[[LabVIEW configuration file]]		[[LabVIEW configuration file]]

	[[Category:~~Configuration_File~~\|Custom]]		[[Category:Configuration File\|Custom]]
			[[Category:Development environment]]

← Older revision		Revision as of 08:47, 5 April 2007
Line 5:		Line 5:
	The LabVIEW Preference file is stored by default in the LabVIEW installation directory. Often LabVIEW developpers use only this default labview.ini for all their projects, ignoring the benefits of having one preference file for each project. Maybe this is due to the fact that it is not straightforward to open LabVIEW with a specific ini file.		The LabVIEW Preference file is stored by default in the LabVIEW installation directory. Often LabVIEW developpers use only this default labview.ini for all their projects, ignoring the benefits of having one preference file for each project. Maybe this is due to the fact that it is not straightforward to open LabVIEW with a specific ini file.

	==='''Using LabVIEW with a custom ini file'''===		=='''Using LabVIEW with a custom ini file'''==

	===='''Command Line'''====		==='''Command Line'''===
	From the command line you have to specify the ini file with the -pref switch:		From the command line you have to specify the ini file with the -pref switch:

Line 14:		Line 14:
	This is not a very convenient method to start LabVIEW.		This is not a very convenient method to start LabVIEW.

	===='''Shortcuts'''====		==='''Shortcuts'''===
	Another method is to create a shortcut with the above command line. For each project edit a different shortcut specifying the ini file. This is far more convenient than the command line		Another method is to create a shortcut with the above command line. For each project edit a different shortcut specifying the ini file. This is far more convenient than the command line

	===='''Custom file extensions'''====		==='''Custom file extensions'''===
	Create a custom file extensions for LabVIEW ini files. Change the file extension of the preference file to something like *.lv82ini. Then in Windows create this file extension specifying the following action:		Create a custom file extensions for LabVIEW ini files. Change the file extension of the preference file to something like *.lv82ini. Then in Windows create this file extension specifying the following action:

Line 30:		Line 30:
	will open the VI lv_start.vi when launching LabVIEW from a preference file. That VI, set to run when opened, can execute any suitable initialization task and load/run VIs specific to the project looking into the project directory (see below).		will open the VI lv_start.vi when launching LabVIEW from a preference file. That VI, set to run when opened, can execute any suitable initialization task and load/run VIs specific to the project looking into the project directory (see below).

	==='''Benefits of a custom ini file'''===		=='''Benefits of a custom ini file'''==

	===='''Default Path'''====		==='''Default Path'''===
	The first thing to do using an ini file customized for your project is to set the default path setting to the project root path. You will soon realize that the file dialogs will show your project path as the startup directory rather than the LabVIEW directory. The file constant "Default Directory" will return the project directory so it is easy to build paths relative to the project directory without harcoding it. If you move the project folder, only change the default directory setting and relative paths will change accordingly. Moreover, in a built application, this default directory will default to the application directory so you can keep the same directory structure and relative paths in the built application without changing the code or checking if the application runs in Development or Run-Time LabVIEW.		The first thing to do using an ini file customized for your project is to set the default path setting to the project root path. You will soon realize that the file dialogs will show your project path as the startup directory rather than the LabVIEW directory. The file constant "Default Directory" will return the project directory so it is easy to build paths relative to the project directory without harcoding it. If you move the project folder, only change the default directory setting and relative paths will change accordingly. Moreover, in a built application, this default directory will default to the application directory so you can keep the same directory structure and relative paths in the built application without changing the code or checking if the application runs in Development or Run-Time LabVIEW.

	===='''Browse history'''====		==='''Browse history'''===
	The browse history (recently opened files and used directories) is stored in the ini file. Custom ini files allow to keep a different history for each project so in the list of recently opened files you see files opened whitin this project rather than files opened in an unrelated project.		The browse history (recently opened files and used directories) is stored in the ini file. Custom ini files allow to keep a different history for each project so in the list of recently opened files you see files opened whitin this project rather than files opened in an unrelated project.

	===='''Source Code Control (SCC)'''====		==='''Source Code Control (SCC)'''===
	Since LabVIEW 8 SCC settings are stored in the preference file. Customized ini files then allow to have different SCC settings and providers for different projects. In LabVIEW 7.1 and before, SCC settings are stored in files kept in the default directory so if you take care of setting the default directory to the project directory, you can also have different SCC setting for each project.		Since LabVIEW 8 SCC settings are stored in the preference file. Customized ini files then allow to have different SCC settings and providers for different projects. In LabVIEW 7.1 and before, SCC settings are stored in files kept in the default directory so if you take care of setting the default directory to the project directory, you can also have different SCC setting for each project.

	===='''Other Project dependent Settings'''====		==='''Other Project dependent Settings'''===
	Other settings might be project dependent like the palettes, search paths, decimal separator etc. All these can be set independantly for each project.		Other settings might be project dependent like the palettes, search paths, decimal separator etc. All these can be set independantly for each project.

	The Project custom ini file is typically stored in the project directory and can be copied from the default labview.ini or from some convenient template. It is also logical to keep this file under SCC to make sure that LabVIEW is correctly configured for the project usage. For example, using an incorrect decimal separator setting can easily break an application.		The Project custom ini file is typically stored in the project directory and can be copied from the default labview.ini or from some convenient template. It is also logical to keep this file under SCC to make sure that LabVIEW is correctly configured for the project usage. For example, using an incorrect decimal separator setting can easily break an application.
	[[Category:Development Environment]]		[[Category:Development Environment]]