Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

mconfig(1) [debian man page]

Mono(mconfig)															     Mono(mconfig)

NAME

       mconfig, - Utility for modifying .NET configuration files

SYNOPSIS

       mconfig [options] command [command_parameters]

DESCRIPTION

       mconfig	can  be  used to edit .NET configuration files, by adding "features" (that is sets of xml statements) defined in one of the config
       files read by mconfig. The config file can also define layouts of default configuration files, which may be useful for  bootstrapping  your
       .NET projects.

       To see the list of recognized commands, default configuration files and features, run mconfig without passing any parameters.

OPTIONS

       -c <config_file>, --config=<config_file>
	      Read  the specified config file after reading the other, preconfigured, config files for the utility. Settings in the specified file
	      override those found in the other configuration locations.

       -t {any | web | application}, --target={any | web | application}
	      Features and default configuration files defined in the mconfig config file(s) can be assigned to one of the  three  targets  -  web
	      (for ASP.NET features/config files), application - for .NET applications, any - applicable in both of the previous targets. Defaults
	      to any.

       -?, -h, --help
	      Show a summary usage screen.

       -v, --version
	      Show the mconfig version

COMMANDS

       {addfeature, af} <feature_name> [config_file_path]
	      Adds the feature named <feature_name> to the specified config file. If [config_file_path] is omitted, the name of the output config-
	      uration  file  will  be  chosen based on the selected target (see the -t option). The web target outputs configuration to file named
	      Web.config, and the application target outputs to file named application.exe.config. The any target does not have a  default  output
	      file.

	      If  the  specified  config file exists, the feature will be injected into it at the locations specified by mconfig configuration. If
	      the target config file does not exist, it will be created and will contain only the specified feature and all its dependencies.

       {defaultconfig, dc} [config_name [target_directory]]
	      Generates a default config file using the configuration entry named [config_name] and outputs the resulting  configuration  file	to
	      the directory given by the [target_directory] option.  If [config_name] is omitted, it defaults to Web.config for the web target and
	      application target. The any target does not specify any default output configuration name. If the  [target_directory]  parameter	is
	      omitted, it defaults to the current directory.

	      Name of the output config file created in [target_directory] is given in the config file layout definition.

FILES

       Config files are read in the order given below. Each subsequent file may override settings found in the files read before it.

       $prefix/etc/mono/mconfig/config.xml
	      The  default  configuration  file, distributed with mconfig. $prefix is the mconfig installation prefix specified on the compilation
	      time.

       $config_dir/mconfig/config.xml
	      $config_dir is the directory specified in the XDG_CONFIG_HOME environment variable or,
	       if it is empty, in the .config directory located in the user's home directory. This file is not distributed with Mono.

       ./mconfig.xml
	      Local configuration file which can contain per-application settings.

SEE ALSO

       mconfig.config (5)

AUTHOR

       Written by Marek Habersack

COPYRIGHT

       Copyright (C) 2007 Novell, Inc (http://www.novell.com)

MAILING LISTS

       Visit http://lists.ximian.com/mailman/listinfo/mono-devel-list for details.

WEB SITE

       Visit: http://www.mono-project.com for details

																     Mono(mconfig)

Check Out this Related Man Page

rc.config(4)						     Kernel Interfaces Manual						      rc.config(4)

NAME

       rc.config, rc.config.d - files containing system configuration information

SYNOPSIS

DESCRIPTION

       The  system  configuration  used  at  startup  is  contained in files within the directory The file sources all of the files within and and
       exports their contents to the environment.

   /etc/rc.config
       The file is a script that sources all of the scripts, and also sources To read the  configuration  definitions,	only  this  file  need	be
       sourced.   This	file  is  sourced by whenever it is run, such as when the command is run to transition between run states.  Each file that
       exists in is sourced, without regard to which startup scripts are to be executed.

   /etc/rc.config.d
       The configuration information is structured as a directory of files, rather than as a single file containing the  same  information.   This
       allows  developers  to  create and manage their own configuration files here, without the complications of shared ownership and access of a
       common file.

   /etc/rc.config.d/* Files
       This is where files containing configuration variable assignments are located.

       Configuration scripts must be written to be read by the POSIX shell, and not the Bourne shell, or In some cases, these files must  also	be
       read  and  possibly modified by control scripts or the sam program.  See sd(4) and sam(1M).  For this reason, each variable definition must
       appear on a separate line, with the syntax:

       No trailing comments may appear on a variable definition line.  Comment statements must be on separate lines, with the comment character in
       column one.  This example shows the required syntax for configuration files:

       Configuration variables may be declared as array parameters when describing multiple instances of the variable configuration.  For example,
       a system may contain two network interfaces, each having a unique IP address and subnet mask (see ifconfig(1M)).  An example of such a dec-
       laration is as follows:

       Note  that  there  must	be  no requirements on the order of the files sourced.	This means configuration files must not refer to variables
       defined in other configuration files, since there is no guarantee that the variable being referenced is currently  defined.   There  is	no
       protection  against  environment variable namespace collision in these configuration files.  Programmers must take care to avoid such prob-
       lems.

   /etc/TIMEZONE
       The file contains the definition of the environment variable.  This file is required by POSIX.  It is sourced by at the same time the files
       are sourced.

SEE ALSO

       rc(1M).

																      rc.config(4)
Man Page