MAN page from CentOS 6 mono-web-4.6.2-5.200.x86_64.rpm

Mono

Section: Misc. Reference Manual Pages (mconfig)
Index

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 readby mconfig. The config file can also define layouts of default configurationfiles, which may be useful for bootstrapping your .NET projects.

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

OPTIONS

-c <config_file>, --config=<config_file>: Read the specified config file after reading the other, preconfigured, configfiles for the utility. Settings in the specified file override those found inthe 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 previoustargets. 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 configuration file will be chosen based on the selected target (see the -t option). The webtarget outputs configuration to file named Web.config, and the applicationtarget outputs to file named application.exe.config. The any target does nothave a default output file.
If the specified config file exists, the feature will be injected into it at the locationsspecified by mconfig configuration. If the target config file does not exist, it will be createdand 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 outputsthe 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 andapplication target. The any target does not specify any default output configurationname. 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 filelayout definition.

FILES

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

$prefix/etc/mono/mconfig/config.xml: The default configuration file, distributed with mconfig. $prefix is the mconfig installationprefix 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 fileis not distributed with Mono.
./mconfig.xml: Local configuration file which can contain per-application settings.

AUTHOR

Written by Marek Habersack

COPYRIGHT

MAILING LISTS

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

WEB SITE

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

This document was created byman2html,using the manual pages.