mono/linux-packaging-mono
0
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Imported Upstream version 3.6.0

Browse Source 
Former-commit-id: da6be194a6b1221998fc28233f2503bd61dd9d14
This commit is contained in:
Jo Shields
2014-08-13 10:39:27 +01:00
commit a575963da9
50588 changed files with 8155799 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

370
man/ChangeLog Normal file
View File

@@ -0,0 +1,370 @@
2010-08-03 Andrés G. Aragoneses <andres@lindenlab.com>
* monolinker.1: Add the name="..." notation to the field examples too
(besides the signature="..." one).
2010-07-12 Rolf Bjarne Kvinge <RKvinge@novell.com>
* mono.1: Document MONO_DEBUG's new reverse-pinvoke-exceptions option.
2010-04-23 Miguel de Icaza <miguel@novell.com>
* mono.1: Sort environment variables, update a couple of docs.
2010-04-07 Andrés G. Aragoneses <andres@lindenlab.com>
* monolinker.1: Fix typo.
2010-04-01 Sebastien Pouliot <sebastien@ximian.com>
* mono.1: Document the new "security" option for logging
2010-03-26 Zoltan Varga <vargaz@gmail.com>
* mono.1: Document the MONO_ENABLE_SHM env variable.
2010-03-03 Rolf Bjarne Kvinge <RKvinge@novell.com>
* mono.1: Document exception tracing.
2010-02-18 Marek Habersack <mhabersack@novell.com>
* mono-configuration-crypto.1: added
* Makefile.am (man_MANS): added mono-configuration-crypto.1
2010-02-10 Geoff Norton <gnorton@novell.com>
* mono.1: Document the aot compiler options.
2010-02-08 Ankit Jain <jankit@novell.com>
* lc.1: Fix typos.
2009-12-11 Marek Habersack <mhabersack@novell.com>
* mono.1: documented the IOMAP report profiler module
2009-11-23 Marek Habersack <mhabersack@novell.com>
* mono.1: documented the 'report' option for MONO_IOMAP
2009-10-11 Ankit Jain <jankit@novell.com>
* xbuild.1: Add info about env var XBUILD_COLORS.
2009-10-09 Zoltan Varga <vargaz@gmail.com>
* mono.1: Document --debug=gdb option.
2009-09-24 Ankit Jain <jankit@novell.com>
* xbuild.1: Add info about env var XBUILD_EMIT_SOLUTION.
2009-09-14 Massimiliano Mantione <massi@ximian.com>
* mono.1: Updated the profiler documentation, removing the obsolete
signal related options and adding the description of the new socket
based command interface.
2009-08-21 Ankit Jain <jankit@novell.com>
* Makefile.am (man_MANS): Add xbuild.1
* xbuild.1: New.
2009-06-12 Jb Evain <jbevain@novell.com>
* mcs.1: update the /platform information.
2009-05-12 Tor Lillqvist <tml@novell.com>
* mkbundle.1: Document MONO_BUNDLED_OPTIONS.
2009-04-09 Jonathan Pryor <jpryor@novell.com>
* mdoc-update.1: Document -L, -r options.
2009-04-06 Jonathan Pryor <jpryor@novell.com>
* mdoc.5: Document //code/@src attribute.
2009-04-03 Andrés G. Aragoneses <aaragoneses@novell.com>
* monolinker.1: Document -m modifier.
2009-03-31 Jonathan Pryor <jpryor@novell.com>
* mdoc-update.1: Fix --out=DIRECTORY formatting. (It was causing the
remaining text to be bolded within monodoc).
2009-03-30 Jonathan Pryor <jpryor@novell.com>
* mdoc-update.1: Add new --exceptions=added functionality.
2009-03-23 Massimiliano Mantione <massi@ximian.com>
* mono.1: Updated the profiler documentation, removing the "gc-signal"
option (it does not exist anymore) and clarifying the role of signals
in heap profiling.
2009-03-20 Jonathan Pryor <jpryor@novell.com>
* mdoc-export-html.1: Document --force-update parameter.
2008-12-31 Massimiliano Mantione <massi@ximian.com>
* mono.1: Updated the profiler documentation, removing the "ts"
option (it does not exist anymore) and explaining the defaults for
allocation and heap profiling.
2008-12-12 Rolf Bjarne Kvinge <RKvinge@novell.com>
* Makefile.am, vbnc.1: Remove vbnc.1. It's living in the
mono-basic module now.
2008-11-20 Rodrigo Kumpera <rkumpera@novell.com>
* mono.1: Document env vars MONO_XDEBUG and MONO_VERBOSE_METHOD.
2008-10-18 Jonathan Pryor <jpryor@novell.com>
* Makefile.am (man_MANS): Remove unpackaged files.
2008-10-18 Jonathan Pryor <jpryor@novell.com>
* mdvalidator.1: Rename to mdvalidater.1.
* Makefile.am (man_MANS): Rename to mdvalidator.1 to mdvalidater.1.
2008-10-18 Jonathan Pryor <jpryor@novell.com>
* Makefile.am (man_MANS): Add mdoc.5 and mono-config.5.
2008-10-18 Mark Probst <mark.probst@gmail.com>
* mono.1: Documentation for "--no-x86-stack-align" option.
2008-10-17 Jonathan Pryor <jpryor@novell.com>
* Makefile: Add man pages added from monodoc/man...
2008-10-12 Atsushi Enomoto <atsushi@ximian.com>
* mono.1 : svn.myrealbox -> anonsvn.mono-project .
2008-10-10 Massimiliano Mantione <massi@ximian.com>
* mono.1: Document the new "sas" option.
2008-09-11 Daniel Morgan <monodanmorg@yahoo.com>
* sqlsharp.1: added commands
\bcs, \cs, \listproviders, \p
2008-08-27 Zoltan Varga <vargaz@gmail.com>
* mono-config.5: Fix a typo.
2008-08-22 Massimiliano Mantione <massi@ximian.com>
* mono.1: Restore original nonvisible formatting (' ', '\-', and '"'
were added everywhere by mistake in r109428).
2008-08-21 Massimiliano Mantione <massi@ximian.com>
* mono.1: Updated description of the logging profiler.
2008-08-08 Zoltan Varga <vargaz@gmail.com>
* mono.1: Remove no-dlsym aot option for now.
* mono.1: Document the 'static' aot option.
2008-08-01 Massimiliano Mantione <massi@ximian.com>
* mono.1: Updated description of the logging profiler.
2008-04-22 Robert Jordan <robertj@gmx.net>
* mono.1: Document MONO_DEBUG=no-gdb-backtrace.
2008-04-21 Martin Baulig <martin@ximian.com>
* mono.1: Documented the new --debug=mdb-optimizations option.
2008-04-17 Marek Habersack <mhabersack@novell.com>
* mono.1: add description of the new NullFileWatcher to the
documentation of the MONO_MANAGED_WATCHER envvar.
2008-03-26 Massimiliano Mantione <massi@ximian.com>
* mono.1: Added description of the logging profiler.
2008-03-08 Zoltan Varga <vargaz@gmail.com>
* mono.1: Fix a typo.
2008-03-07 Rodrigo Kumpera <rkumpera@novell.com>
* mono.1: Documented new --security options validil
and verifiable.
2007-12-08 Jonathan Pryor <jpryor@novell.com>
* wsdl.1: Fix groff comment (so that it doesn't appear in monodoc's
man-provider output).
2007-12-08 Marek Habersack <mhabersack@novell.com>
* mono.1: added short documentation about the
MONO_ASPNET_INHIBIT_SETTINGSMAP environment variable.
2007-12-07 Mark Probst <mark.probst@gmail.com>
* mono.1: Added a short paragraph on the MONO_GENERIC_SHARING
environment variable.
2007-11-21 Marek Habersack <mhabersack@novell.com>
* mconfig.1: modify to reflect parameter changes in mconfig.
2007-10-23 Marek Habersack <mhabersack@novell.com>
* mconfig.1: added
* Makefile.am (man_MANS): added mconfig.1
2007-10-17 Sebastien Pouliot <sebastien@ximian.com>
* sn.1: Fix help for -T / -t as this shows the public key token
(and not the public key).
2007-08-31 Sebastien Pouliot <sebastien@ximian.com>
* permview.1: add documentation for the -xml option now available
with the Cecil-enabled version of permview.
2007-07-17 Jb Evain <jbevain@novell.com>
* monolinker.1: add monolinker man page.
2007-07-11 Jb Evain <jbevain@novell.com>
* mcs.1: add info about smcs.
2007-07-04 Atsushi Enomoto <atsushi@ximian.com>
* mcs.1 : we do not use fixed Latin1 by default.
2007-07-02 Jackson Harper <jackson@ximian.com>
* xamlg.1:
* Makefile.am: Moved to more appropriate place.
2007-07-02 Jackson Harper <jackson@ximian.com>
* xamlg.1:
* Makefile.am: Add man page for xamlg.
2007-04-26 Dick Porter <dick@ximian.com>
* mono.1: Document MONO_DISABLE_SHM
2007-02-20 Rolf Bjarne Kvinge <RKvinge@novell.com>
* vbnc.1: Added man entry for vbnc.
* mbas.1: Deleted.
* Makefile.am: Added vbnc.1
Mon Jan 22 11:15:26 CET 2007 Paolo Molaro <lupus@ximian.com>
* mono.1: typo fixes from jessemerriman@warpmail.net (Jesse Merriman).
2007-01-17 Alp Toker <alp@atoker.com>
* gacutil.1: Spelling and grammar fixes.
2007-01-17 Alp Toker <alp@atoker.com>
* sn.1: Spelling and grammar fixes.
2006-12-08 Sebastien Pouliot <sebastien@ximian.com>
* mono.1: Document the MONO_TLS_SESSION_CACHE_TIMEOUT environment
variable that can be used to control the validity period of the
SSL/TLS negotiation cache.
2006-11-29 Joshua Tauberer <jit@occams.info>
* mkbundle.1: Corrected minor errors, added --nomain option.
2006-11-14 Atsushi Enomoto <atsushi@ximian.com>
* genxs.1 : introduced <baseSerializer> and <implementation>
elements. See also sgen.
2006-11-14 Atsushi Enomoto <atsushi@ximian.com>
* sgen.1, Makefile: revised a bit, to not mislead as if the output
were sources. It indeed generates an assembly.
2006-11-14 Atsushi Enomoto <atsushi@ximian.com>
* sgen.1, Makefile: added manpage for sgen.
2006-10-03 Dick Porter <dick@ximian.com>
* mono.1: Document the new MONO_IO_PORTABILITY_HELP environment
variable
2006-09-08 Robert Jordan <robertj@gmx.net>
* mkbundle.1: The `-z' option is now supported under Windows.
2006-08-31 Geoff Norton <gnorton@customerdna.com>
* macpack.1: Fix a typo for the -appname option.
2006-08-23 Wade Berrier <wberrier@novell.com>
* gacutil.1 : Change automake usage example because we always use $(prefix)/lib
for the gac, even on 64 bit systems.
2006-08-20 Gert Driesen <drieseng@users.sourceforge.net>
* mono.1 : Document MONO_EVENTLOG_TYPE, replaces MONO_EVENTLOG_PATH.
2006-08-17 Sebastien Pouliot <sebastien@ximian.com>
* sn.1: Document the (new - 1.1.17) support for PKCS#12/PFX password
protected files to sign assemblies.
2006-08-14 Atsushi Enomoto <atsushi@ximian.com>
* mono.1 : MONO_LOCAL_EVENTLOG_PATH -> MONO_EVENTLOG_PATH.
2006-08-14 Atsushi Enomoto <atsushi@ximian.com>
* mono.1 : description on MONO_LOCAL_EVENTLOG_PATH.
2006-03-15 Miguel de Icaza <miguel@novell.com>
* mono.1: Document MONO_XEXCEPTIONS and MONO_XSYNC, create new
section, sort the previous enviornment section.
2006-03-06 Lluis Sanchez Gual <lluis@novell.com>
* mono.1: Updated MONO_XMLSERIALIZER_THS option information.
2006-02-22 Jelmer Vernooij <jelmer@samba.org>
* mbas.1, Makefile.am: Add manpage for mbas (based on mcs.1)
2006-01-26 Jonathan Pryor <jonpryor@vt.edu>
* ChangeLog: Started
* mono-shlib-cop.1: Document another BUG/design issue that it doesn't check
for; formatting/style changes.
2009-05-22 Michael Barker <mike@middlesoft.co.uk>
* man.1: Added documentation for MONO_MESSAGING_PROVIDER environment
variable.

61
man/Makefile.am Normal file
View File

@@ -0,0 +1,61 @@
man_MANS = \
al.1 \
cert2spc.1 \
certmgr.1 \
chktrust.1 \
cilc.1 \
crlupdate.1 \
csharp.1 \
disco.1 \
dtd2xsd.1 \
gacutil.1 \
genxs.1 \
httpcfg.1 \
ilasm.1 \
lc.1 \
macpack.1 \
makecert.1 \
mconfig.1 \
mcs.1 \
mdassembler.1 \
mdoc.1 \
mdoc.5 \
mdoc-assemble.1 \
mdoc-export-html.1 \
mdoc-export-msxdoc.1 \
mdoc-update.1 \
mdoc-validate.1 \
mdvalidater.1 \
mkbundle.1 \
mono.1 \
mprof-report.1 \
mono-cil-strip.1 \
mono-config.5 \
monodocer.1 \
monodocs2html.1 \
monolinker.1 \
monop.1 \
mono-api-info.1 \
mono-service.1 \
mono-shlib-cop.1 \
mono-xmltool.1 \
mozroots.1 \
pdb2mdb.1 \
permview.1 \
prj2make.1 \
resgen.1 \
secutil.1 \
setreg.1 \
sgen.1 \
signcode.1 \
sn.1 \
soapsuds.1 \
sqlsharp.1 \
wsdl.1 \
xbuild.1 \
xsd.1 \
mono-configuration-crypto.1 \
ccrewrite.1 \
cccheck.1
EXTRA_DIST = $(man_MANS)

698
man/Makefile.in Normal file
View File

File diff suppressed because it is too large Load Diff

156
man/al.1 Normal file
View File

@@ -0,0 +1,156 @@
.TH "al" 1
.SH NAME
al, al2 \- Mono Assembly Linker
.SH SYNOPSIS
.B al [option] [source-files]
.SH DESCRIPTION
AL is the Mono assembly linkder.
.PP
This linker is used to put together assemblies from a collection of
modules (.netmodule files), assembly manifest files and resources.
.PP
Do not confuse this with the
.B monolinker,
which is a tool to reduce the size of assemblies based on the code
used.
.PP
Use al for processing 1.0 assemblies, use al2 to process 2.0 assemblies.
.SH OPTIONS
.TP
.B @<filename>
Read response file for more options.
.TP
.B -algid:<id>
Algorithm used to hash files. The <id> must be specified in hexadecimal.
.TP
.B -base:<addr> | -baseaddress:<addr>
Base address for the library. THIS FEATURE ISN'T IMPLEMENTED.
.TP
.B -bugreport:<filename>
Create a 'Bug Report' file. THIS FEATURE ISN'T IMPLEMENTED.
.TP
.B -comp:<text> | -company:<text>
This inserts the company name into the assembly metadata.
This is equivalent to adding the [AssemblyCompany ("<text>")] attribute
into C# source code.
.TP
.B -config:<text> | -configuration:<text>
This inserts the configuration string into the assembly metadata.
This is equivalent to adding the [AssemblyConfiguration ("<text>")]
attribute into C# source code.
.TP
.B -copy:<text> | -copyright:<text>
This inserts the copyright message into the assembly metadata.
This is equivalent to adding the [AssemblyCopyright ("<text>")]
attribute into C# source code.
.TP
.B -c:<text> | -culture:<text>
This inserts the supported culture into the assembly metadata.
This is equivalent to adding the [AssemblyCulture ("<text>")]
attribute into C# source code.
.TP
.B -delay | -delay+ | -delaysign | -delaysign+
The generated assembly will be delay signed.
This is equivalent to adding the [AssemblyDelaySignAttribute (true)]
attribute into C# source code.
.TP
.B -delay- | -delaysign-
The generated assembly will be fully signed (i.e. not delay signed).
This is the default option when signing (-keyfile or -keyname).
.TP
.B -descr:<text> | -description:<text>
This inserts a description of the assembly into the assembly metadata.
This is equivalent to adding the [AssemblyDescription ("<text>")]
attribute into C# source code.
.TP
.B -e:<filename> | -evidence:<filename>
This embed into the assembly the specified file as assembly security
evidences.
.TP
.B -fileversion:<version>
Optional Win32 version. This overrides the normal assembly version.
.TP
.B -flags:<flags>
Assembly flags. The <flags> must be specified in hexadecimal.
.TP
.B -fullpaths
Display files using fully-qualified filenames.
.TP
.B -keyf:<filename> | -keyfile:<filename>
Strongname (sign) the output assembly using the key pair present in
the specified strong name key file (snk). A full key pair is required
unless the delay signing option is also specified (-delay+).
This is equivalent to adding the [AssemblyKeyFile ("<text>")]
attribute into C# source code.
.TP
.B -keyn:<text> | -keyname:<text>
Strongname (sign) the output assembly using the key pair present in
the specified container. Delay signing isn't supported when using key
containers.
This is equivalent to adding the [AssemblyKeyName ("<text>")]
attribute into C# source code.
.TP
.B -main:<method>
Specifies the method name of the assembly entry point.
.TP
.B -nologo
Suppress the startup banner and copyright message.
.TP
.B -out:<filename>
Output file name for the assembly manifest.
.TP
.B -prod:<text> | product:<text>
This inserts the product name into the assembly metadata.
This is equivalent to adding the [AssemblyProduct ("<text>")]
attribute into C# source code.
.TP
.B -productv[ersion]:<text>
This inserts the product version into the assembly metadata.
This is equivalent to adding the [AssemblyInformationalVersion ("<text>")]
attribute into C# source code.
.TP
.B -t[arget]:<target> | -target=<target>
Valid <target>s are:
.B lib | library
to create a library (.dll),
.B exe
to create a console executable (.exe), and
.B win | winexe
to create a Windows executable (.exe).
.TP
.B -template:<filename>
Specifies an assembly to get default options from.
.TP
.B -title:<text>
This inserts an assembly title into the assembly metadata.
This is equivalent to adding the [AssemblyTitle ("<text>")]
attribute into C# source code.
.TP
.B -trade:<text> | -trademark:<text>
This inserts a trademark message into the assembly metadata.
This is equivalent to adding the [AssemblyTrademark ("<text>")]
attribute into C# source code.
.TP
.B -v:<version> | -version:<version>
This inserts the assembly version into the assembly metadata. You can
use * to auto-generate remaining numbers.
This is equivalent to adding the [AssemblyVersion ("<text>")]
attribute into C# source code.
.TP
.B -win32icon:<filename>
Use this icon for the output.
.TP
.B -win32res:<filename>
Specifies the Win32 resource file.
.TP
.B -? | -help
Display information about AL
.PP
.SH SEE ALSO
sn(1), monolinker(1)
.SH COPYRIGHT
Copyright (C) 2005 Novell, Inc (http://www.novell.com)
.SH MAILING LISTS
Visit http://lists.ximian.com/mailman/listinfo/mono-devel-list for details.
.SH WEB SITE
Visit: http://www.mono-project.com for details

67
man/cccheck.1 Normal file
View File

@@ -0,0 +1,67 @@
.\"
.\" cccheck manual page.
.\" Copyright (C) 2011 Alexander Chebaturkin
.\" Author:
.\" Alexander Chebaturkin (chebaturkin@gmail.com)
.\"
.TH Mono "cccheck"
.SH NAME
cccheck \- Perform static code contracts verification for CLR assemblies.
.SH SYNOPSIS
.PP
.B cccheck --assembly=<assembly> [options]
.SH DESCRIPTION
Perform static code contracts verification to find bugs and inconsistences
between code and specification. This includes non-null, integer analyses.
.PP
The assembly must have been built with the symbol CONTRACTS_FULL defined,
otherwise the calls to the contract methods will have been removed
by the compiler.
.PP
Currently only Contract.Assume() and Contract.Assert() methods are
supported. Only non-null analysis is supported, the consecutive analyses are
in development. An error message will be shown if cccheck is unable to process
all or some of the methods of specified assembly.
.SH CONFIGURATION OPTIONS
.TP
.I "--assembly <assembly-name>"
The assembly to perform static verification.
.TP
.I "--debug"
Shows debug information about process of proving the assertions. It shows
four layers of abstraction, raw layer, stack layer, heap layer,
and substituted expression level.
.TP
.I "--method=<method-name-substring>"
String for finding method. It filters all methods in assembly where method
name has this parameter as a substring.
.TP
.I "--help"
Show help for cccheck, listing configuration options.
.SH EXAMPLES
.TP
Suppose you have a method:
void Method() {
object x = null;
int y = 1;
if (y % 2 == 1)
x = new object();
else
x = new string();
Contract.Assert(x != null);
}
After the verification the tool will have results in following format:
"Assertion at : [Subroutine: <id> Block <blockId> PC <id>] :
is (true|false|unproven|unreachable)".
(PC is a program counter)
.SH AUTHOR
Written by Alexander Chebaturkin
.SH COPYRIGHT
Copyright 2011 Alexander Chebaturkin.
Released under MIT license.
.SH WEB SITE
Visit http://www.mono-project.com for details

67
man/ccrewrite.1 Normal file
View File

@@ -0,0 +1,67 @@
.\"
.\" ccrewrite manual page.
.\" Copyright (C) 2010 Novell, Inc (http://www.novell.com)
.\" Author:
.\" Chris Bacon <chrisbacon76@gmail.com>
.\"
.TH Mono "ccrewrite"
.SH NAME
ccrewrite \- Rewrite CLR assemblies for runtime code contract verification.
.SH SYNOPSIS
.PP
.B ccrewrite --assembly=<assembly> [options]
.SH DESCRIPTION
Rewrite CLR assemblies to convert calls into the System.Diagnostics.Contracts
namespace to perform runtime contract verification. This includes
contract inheritance for virtual methods.
.PP
The assembly must have been built with the symbol CONTRACTS_FULL defined,
otherwise the calls to the contract methods will have been removed
by the compiler.
.PP
Currently only pre-conditions are supported, using the Contract.Requires()
method. Contract inheritance for virtual methods is supported. Only a
limited range of operations and types can be used within a pre-condition,
an error message will be shown if ccrewrite is unable to process the
specified assembly.
.SH CONFIGURATION OPTIONS
.TP
.I "--assembly <assembly-name>"
The assembly to rewrite. If no --output option is specified, then this file
overwritten with the rewritten version.
.TP
.I "--debug"
Use debug information if available to improve the usefulness of contract
failure messages.
.TP
.I "--help"
Show help for ccrewrite, listing configuration options.
.TP
.I "--level <level> (default=4)"
Set the which contract types are present in rewritten assembly:
0 = No contracts;
1 = Release requires;
2 = Requires;
3 = Ensures;
4 = Invariants;
(Each level includes all previous levels)
.TP
.I "--output <file-name>"
Write the rewritten assembly to the specified file. If this is not present
then the input assembly file is overwritten with the rewritten version.
.TP
.I "--rewrite (default=true)"
Rewrite the assembly. If false, then nothing is done.
.TP
.I "--throwOnFailure (default=false)"
Throw a ContractException on unhandled contract failure. The default
behaviour is to Assert.
.SH AUTHOR
Written by Chris Bacon
.SH COPYRIGHT
Copyright (C) 2010 Chris Bacon.
Released under MIT license.
.SH WEB SITE
Visit http://www.mono-project.com for details

42
man/cert2spc.1 Normal file
View File

@@ -0,0 +1,42 @@
.\"
.\" cert2spc manual page.
.\" Copyright 2002, 2003 Motus Technologies
.\" Author:
.\" Sebastien Pouliot (spouliot@motus.com)
.\"
.TH Mono "cert2spc"
.SH NAME
cert2spc \- Transform multiple X.509 certificates to a Software
Publisher Certificate
.SH SYNOPSIS
.PP
.B cert2spc certificate|crl [certificate|crl ...] outputfile.spc
.SH DESCRIPTION
Combine a list of X.509 certificates or X.509 CRL (Certificate
Revocation List) into a Software Publisher Certificate (PKCS#7
file). The SPC file is required for signing a PE file (like an
assembly) using signcode.
.SH PARAMETERS
.TP
.I "certificate"
One (or more) X.509 certificate to add (space separated).
.TP
.I "crl"
One (or more) X.509 CRL to add (space separated).
.TP
.I "output.spc"
Software Publisher Certificate to output. If the specified file
exists it will be overwritten.
.SH AUTHOR
Written by Sebastien Pouliot
.SH COPYRIGHT
Copyright (C) 2002, 2003 Motus Technologies.
Released under BSD license.
.SH MAILING LISTS
Visit http://lists.ximian.com/mailman/listinfo/mono-devel-list for details.
.SH WEB SITE
Visit http://www.mono-project.com for details
.SH SEE ALSO
.BR makecert(1), signcode(1)

167
man/certmgr.1 Normal file
View File

@@ -0,0 +1,167 @@
.\"
.\" certmgr manual page.
.\" Copyright 2004-2005 Novell
.\" Copyright 2010 Pablo Ruiz
.\" Author:
.\" Sebastien Pouliot <sebastien@ximian.com>
.\" Pablo Ruiz Garcia <pruiz@netway.org>
.\"
.TH Mono "certmgr"
.SH NAME
certmgr \- Mono Certificate Manager (CLI version)
.SH SYNOPSIS
.PP
.B certmgr [action] [object type] [options] store [filename]
or
.B certmgr -ssl [options] url
.SH DESCRIPTION
This tool allow to list, add, remove or extract certificates, certificate
revocation lists (CRL) or certificate trust lists (CTL) to/from a
certificate store. Certificate stores are used to build and validate
certificate chains for Authenticode(r) code signing validation and SSL
server certificates.
.SH ACTIONS
.TP
.I "-list"
List the certificates, CTL or CTL in the specified store.
.TP
.I "-add"
Add a certificate, CRL or CTL to specified store. If filename it's a pkcs12
or pfx file, and it contains a private key, it will be imported to local key
pair container.
.TP
.I "-del"
Remove a certificate, CRL or CTL from specified store. You must specify the
object to be removed with it's hash value (and not a filename). This hash
value is shown when doing a
.B -list
on the store.
.TP
.I "-put"
Copy a certificate, CRL or CTL from a store to a file.
.TP
.I "-ssl"
Download and add the certificates from a SSL session. You'll be asked to
confirm the addition of every certificate received from the server. Note
that SSL/TLS protocols do not requires a server to send the root certificate.
This action assume an certificate (-c) object type and will import the
certificates in appropriate stores (i.e. server certificate in the
OtherPeople store, the root certificate in the Trust store, any other
intermediate certificates in the IntermediateCA store).
.TP
.I "-importKey"
Allows importing a private key from a pkcs12 file into a local key pair
store. (Usefull when you already have the key's corresponding certificate
installed at the specific store.)
.SH OBJECT TYPES
.TP
.I "-c", "-cert", "-certificate"
Add, Delete or Put certificates. That is the specified file must/will contains
X.509 certificates in DER binary encoding.
.TP
.I "-crl"
Add, Delete or Put certificate revocation lists (CRL). That is the specified
file must/will contains X.509 CRL in DER binary encoding.
.TP
.I "-ctl"
Add, Delete or Put certificate trust lists (CRL). UNSUPPORTED.
.SH OPTIONS
.TP
.I "-m"
Use the machine's certificate stores (instead of the default user's stores).
.TP
.I "-v"
More details displayed on the console.
.TP
.I "-p password"
Use the specify password when accessing a pkcs12 file.
.TP
.I "-help", "-h", "-?", "/?"
Display help about this tool.
.SH FILES
.B WARNING: This details the current behavior of Mono and could change between releases.
The only safe way to interact with certificate stores is to use the certmgr
tool. The current releases of Mono keeps all the user certificate stores in
separates directories under
.I ~/.config/.mono/certs/
.TP
For example the trusted root certificates for a user would be kept under
.I ~/.config/.mono/certs/Trust/
.TP
Certificates files are kept in DER (binary) format (extension .cer).
.TP
The filenames either starts with
.I tbp
(thumbprint) or
.I ski
(subject key identifier).
.TP
The rest of the filename is the base64-encoded value (tbp or ski).
.TP
Private key data is stored under
.I ~/.config/.mono/keypairs/
.SH EXAMPLES
.TP
.B mono certmgr.exe -list -c -m Trust
List all certificates in the machine Trust store. This will display the hash
value for each certificate. This value can be used to identify uniquely a
certificate for some operations (e.g. delete). E.g.
.B Unique Hash: FFA3AC0084DA1673B5A031EBB2156B3E8FBBF6D8
.TP
.B mono certmgr.exe -del -c -m Trust FFA3AC0084DA1673B5A031EBB2156B3E8FBBF6D8
Remove the certificate, represented by the hash value, from the machine Trust
store. Note that the machine store is normally restricted. The following
error message will appear if the current user doesn't have the minimum access
rights to remove the certificate:
.B Access to the machine 'Trust' certificate store has been denied.
.TP
.B certmgr -ssl https://www.verisign.com
Import certificates from www.verisign.com used for HTTP over SSL. See KNOWN
ISSUES (MD2) if you're downloading from www.verisign.com.
.TP
.B certmgr -ssl ldaps://www.nldap.com:636
Import the certificates from www.nldap.com used for secure LDAP. This works
even if we don't know how to speak LDAP because we stop the communication
shortly after the SSL handshake (which gives us the certificate).
.SH KNOWN ISSUES
.TP
.B MD2
Some Certificate Authorities (CA) old root certificates use the MD2 hash
algorithm. MD2 is old enough not to be part of the standard .NET framework.
This makes it impossible to validate a digital signature made with MD2. For
this reason MD2 is included in the Mono.Security.dll assembly. However the
machine.config file must be updated so the OID for MD2 is known at runtime.
To correct this insert the following XML snippet inside the <configuration>
element of your machine.config file.
<mscorlib>
<cryptographySettings>
<cryptoNameMapping>
<cryptoClasses>
<cryptoClass monoMD2="Mono.Security.Cryptography.MD2Managed, Mono.Security, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=0738eb9f132ed756" />
</cryptoClasses>
<nameEntry name="MD2" class="monoMD2" />
</cryptoNameMapping>
<oidMap>
<oidEntry OID="1.2.840.113549.2.2" name="MD2" />
</oidMap>
</cryptographySettings>
</mscorlib>
.SH AUTHOR
Written by Sebastien Pouliot
Minor additions by Pablo Ruiz García
.SH COPYRIGHT
Copyright (C) 2004-2005 Novell.
.SH MAILING LISTS
Visit http://lists.ximian.com/mailman/listinfo/mono-list for details.
.SH WEB SITE
Visit http://www.mono-project.com for details
.SH SEE ALSO
.BR makecert(1), setreg(1)

46
man/chktrust.1 Normal file
View File

@@ -0,0 +1,46 @@
.\"
.\" chktrust manual page.
.\" Copyright 2003 Motus Technologies
.\" Copyright 2004 Novell
.\" Author:
.\" Sebastien Pouliot (sebastien@ximian.com)
.\"
.TH Mono "chktrust"
.SH NAME
chktrust \- Check the trust of a PE executable.
.SH SYNOPSIS
.PP
.B chktrust [options] filename
.SH DESCRIPTION
Verify if an PE executable (CLR assembly, Win32 EXE or DLL) has a valid
Authenticode(r) signature that can be traced back to a trusted certificate
authority (CA). This means that
.TP
(a) the signature is valid (i.e. file integrity) and,
.TP
(b) the code-signing certificate can be chained back to one of the
certificates in the Trust store.
.SH OPTIONS
.TP
.I "-q", "-quiet"
Quiet mode. Limited display on console.
.TP
.I "-v", "-verbose"
Verbose mode. More details displayed on the console.
.TP
.I "-help", "-h", "-?", "/?"
Display help about this tool.
.SH KNOWN RESTRICTIONS
chktrust cannot validate Authenticode signatures on CAB files.
.SH AUTHOR
Written by Sebastien Pouliot
.SH COPYRIGHT
Copyright (C) 2003 Motus Technologies.
Copyright (C) 2004 Novell.
Released under BSD license.
.SH MAILING LISTS
Visit http://lists.ximian.com/mailman/listinfo/mono-list for details.
.SH WEB SITE
Visit http://www.mono-project.com for details
.SH SEE ALSO
.BR signcode(1), makecert(1), certmgr(1), setreg(1)

21
man/cilc.1 Normal file
View File

@@ -0,0 +1,21 @@
.TH "cilc" 1
.SH NAME
cilc \- Mono CIL-to-C binding generator
.SH SYNOPSIS
.B cilc
[options]
.I assembly
.I target
.SH DESCRIPTION
cilc is the Mono CIL-to-C binding generator. It takes a CIL assembly as input
and generates a directory of C sources which, when compiled, provide a C
interface to the classes contained within that assembly by means of a shared
object library.
.PP
Generated sources make use of the Mono embedding API. Thus a complete Mono
development environment must be available on the development system and a
complete Mono runtime environment must be available on target systems.
.SH AUTHOR
Written by Alp Toker <alp@atoker.com>
.SH SEE ALSO
mono(1)

56
man/crlupdate.1 Normal file
View File

@@ -0,0 +1,56 @@
.\"
.\" crlupdate manual page.
.\"
.\" Author:
.\" Sebastien Pouliot <sebastien@ximian.com>
.\"
.\" Copyright (C) 2011 Novell, Inc (http://www.novell.com)
.\"
.TH Mono "crlupdate"
.SH NAME
crlupdate \- Mono Certficate Revocation List Downloader and Updater
.SH SYNOPSIS
.PP
.B crlupdate [-m] [-v] [-f]
.SH DESCRIPTION
This tool allows the download of new, or update of existing, Certficate
Revocation List (CRL) associated with the certificates present in the
user (default) or machine stores. The CRL present in the stores are used
to determine the validity of unexpired, trusted X.509 certificates.
To ensure CRL are always fresh consider automating the updates using the
\fIat\fR (or similar) command(s).
.SH OPTIONS
.TP
.I "-m"
Update CRL associated with certificates in the machine store. By default
the tool works on the user store.
.TP
.I "-v"
Verbose mode. Display extra information while downloading and updating
the CRL.
.TP
.I "-f"
Force the download of all CRL even if they are not normally due to be
updated (i.e. nextUpdate is still in the future).
.SH EXAMPLES
.TP
.B mono crlupdate.exe
Download (if missing) or update (if existing and past due date) all CRL
associated with certificates present in user store.
.TP
.B mono crlupdate.exe -f -m
Force the download of every CRL associated with certificates present in
the machine store. Note that the user running this needs read/write
access to the machine store or not update will occur.
.SH AUTHOR
Written by Sebastien Pouliot
.SH COPYRIGHT
Copyright (C) 2011 Novell.
.SH MAILING LISTS
Visit http://lists.ximian.com/mailman/listinfo/mono-list for details.
.SH WEB SITE
Visit http://www.mono-project.com for details
.SH SEE ALSO
.BR certmgr(1), at(1)

372
man/csharp.1 Normal file
View File

@@ -0,0 +1,372 @@
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
..
.TH csharp 1 "4 September 2008"
.SH NAME
csharp, gsharp \- Interactive C# Shell
.SH SYNOPSIS
.B csharp [--attach PID] [-e EXPRESSION] [file1 [file2]]
[options]
.P
.B gsharp [file1 [file2]]
.SH DESCRIPTION
The
.I csharp
is an interactive C# shell that allows the user to enter and evaluate
C# statements and expressions from the command line. The regular
.I mcs
command line options can be used in this version of the compiler.
.PP
The
.I gsharp
command is a GUI version of the C# interpreter that uses Gtk# and
provides an area to attach widgets as well. This version can be
attached to other Gtk# applications in a safe way as it injects itself
into the main loop of a Gtk# application, avoiding any problems
arising from the multi-threaded nature of injecting itself into a
target process.
.PP
Files specified in the command line will be loaded and executed as
scripts.
.PP
Starting with Mono 2.10, the
.I csharp
command can be used as an interpreter executed by executables flagged
with the Unix execute attribute. To do this, make the first line of
your C# source code look like this:
.nf
"#!/usr/bin/csharp"
Console.WriteLine ("Hello, World");
.fi
.SH OPTIONS
The commands accept all of the commands that are available to the
.I mcs
command, so you can reference assemblies, specify paths, language
level and so on from the command line. In addition, the following
command line options are supported:
.TP
.I "\-\-attach"
This is an advanced option and should only be used if you have a deep
understanding of multi-threading. This option is availble on the
.I csharp
command and allows the compiler to be injected into other processes.
This is done by injecting the C# shell in a separate thread that runs
concurrently with your application. This means that you must take
special measures to avoid crashing the target application while using
it. For example, you might have to take the proper locks before
issuing any commands that might affect the target process state, or
sending commands through a method dispatcher.
.TP
.I "\-e" EXPRESSION
This will evaluate the specified C# EXPRESSION and exit
.SH OPERATION
Once you launch the csharp command, you will be greeted with the
interactive prompt:
.PP
.nf
$ csharp
Mono C# Shell, type "help;" for help
Enter statements below.
csharp>
.fi
.PP
A number of namespaces are pre-defined with C# these include System,
System.Linq, System.Collections and System.Collections.Generic.
Unlike the compiled mode, it is possible to add new using statements
as you type code, for example:
.PP
.nf
csharp> new XmlDocument ();
<interactive>(1,6): error CS0246: The type or namespace name `XmlDocument' could not be found. Are you missing a using directive or an assembly reference?
csharp> using System.Xml;
csharp> new XmlDocument ();
System.Xml.XmlDocument
.fi
.PP
Every time a command is typed, the scope of that command is one of a
class that derives from the class Mono.CSharp.InteractiveBase. This
class defines a number of static properties and methods. To display
a list of available commands access the `help' property:
.nf
csharp> help;
"Static methods:
LoadPackage (pkg); - Loads the given Package (like -pkg:FILE)
[...]
ShowVars (); - Shows defined local variables.
ShowUsing (); - Show active using decltions.
help;
"
csharp>
.fi
.PP
When expressions are entered, the C# shell will display the result of
executing the expression:
.PP
.nf
csharp> Math.Sin (Math.PI/4);
0.707106781186547
csharp> 1+1;
2
csharp> "Hello, world".IndexOf (',');
5
.fi
.PP
The C# shell uses the ToString() method on the returned object to
display the object, this sometimes can be limiting since objects that
do not override the ToString() method will get the default behavior
from System.Object which is merely to display their type name:
.PP
.nf
csharp> var a = new XmlDocument ();
csharp> a;
System.Xml.Document
csharp> csharp> a.Name;
"#document"
csharp>
.fi
.PP
A few datatypes are handled specially by the C# interactive shell like
arrays, System.Collections.Hashtable, objects that implement
System.Collections.IEnumerable and IDictionary and are rendered
specially instead of just using ToString ():
.PP
.nf
csharp> var pages = new Hashtable () {
> { "Mono", "http://www.mono-project.com/" },
> { "Linux", "http://kernel.org" } };
csharp> pages;
{{ "Mono", "http://www.mono-project.com/" }, { "Linux", "http://kernel.org" }}
.fi
.PP
It is possible to use LINQ directly in the C# interactive shell since
the System.Linq namespace has been imported at startup. The
following sample gets a list of all the files that have not been
accessed in a week from /tmp:
.PP
.nf
csharp> using System.IO;
csharp> var last_week = DateTime.Now - TimeSpan.FromDays (7);
csharp> var old_files = from f in Directory.GetFiles ("/tmp")
> let fi = new FileInfo (f)
> where fi.LastAccessTime < LastWeek select f;
csharp>
.fi
.PP
You can of course print the results in a single statement as well:
.PP
.nf
csharp> using System.IO;
csharp> var last_week = DateTime.Now - TimeSpan.FromDays (7);
csharp> from f in Directory.GetFiles ("/tmp")
> let fi = new FileInfo (f)
> where fi.LastAccessTime < last_week select f;
[...]
csharp>
.fi
.PP
LINQ and its functional foundation produce on-demand code for
IEnumerable return values. For instance, the return value from a
using `from' is an IEnumerable that is evaluated on demand. The
automatic rendering of IEnumerables on the command line will trigger
the IEnumerable pipeline to execute at that point instead of having
its execution delayed until a later point.
.PP
If you want to avoid having the IEnumerable rendered at this point,
simply assign the value to a variable.
.PP
Unlike compiled C#, the type of a variable can be changed if a new
declaration is entered, for example:
.PP
.nf
csharp> var a = 1;
csharp> a.GetType ();
System.Int32
csharp> var a = "Hello";
csharp> a.GetType ();
System.String
csharp> ShowVars ();
string a = "Hello"
.fi
.PP
In the case that an expression or a statement is not completed in a
single line, a continuation prompt is displayed, for example:
.PP
.nf
csharp> var protocols = new string [] {
> "ftp",
> "http",
> "gopher"
> };
csharp> protocols;
{ "ftp", "http", "gopher" }
.fi
.PP
Long running computations can be interrupted by using the Control-C
sequence:
.PP
.nf
csharp> var done = false;
csharp> while (!done) { }
Interrupted!
System.Threading.ThreadAbortException: Thread was being aborted
at Class1.Host (System.Object& $retval) [0x00000]
at Mono.CSharp.InteractiveShell.ExecuteBlock (Mono.CSharp.Class host, Mono.CSharp.Undo undo) [0x00000]
csharp>
.fi
.PP
.SH INTERACTIVE EDITING
The C# interactive shell contains a line-editor that provides a more
advanced command line editing functionality than the operating system
provides. These are available in the command line version, the GUI
versions uses the standard Gtk# key bindings.
.PP
The command set is similar to many other applications (cursor keys)
and incorporates some of the Emacs commands for editing as well as a
history mechanism to
.PP
.PP
The following keyboard input is supported:
.TP
.I Home Key, Control-a
Goes to the beginning of the line.
.TP
.I End Key, Control-e
Goes to the end of the line.
.TP
.I Left Arrow Key, Control-b
Moves the cursor back one character.
.TP
.I Right Arrow Key, Control-f
Moves the cursor forward one character.
.TP
.I Up Arrow Key, Control-p
Goes back in the history, replaces the current line with the previous
line in the history.
.TP
.I Down Arrow Key, Control-n
Moves forward in the history, replaces the current line with the next
lien in the history.
.TP
.I Return
Executes the current line if the statement or expression is complete,
or waits for further input.
.TP
.I Control-C
Cancel the current line being edited. This will kill any currently
in-progress edits or partial editing and go back to a toplevel
definition.
.TP
.I Backspace Key
Deletes the character before the cursor
.TP
.I Delete Key, Control-d
Deletes the character at the current cursor position.
.TP
.I Control-k
Erases the contents of the line until the end of the line and places
the result in the cut and paste buffer.
.TP
.I Alt-D
Deletes the word starting at the cursor position and appends into the
cut and paste buffer. By pressing Alt-d repeatedly, multiple words
can be appended into the paste buffer.
.TP
.I Control-Y
Pastes the content of the kill buffer at the current cursor position.
.TP
.I Control-Q
This is the quote character. It allows the user to enter
control-characters that are otherwise taken by the command editing
facility. Press Control-Q followed by the character you want to
insert, and it will be inserted verbatim into the command line.
.TP
.I Control-D
Terminates the program. This terminates the input for the program.
.SH STATIC PROPERTIES AND METHODS
Since the methods and properties of the base class from where the
statements and expressions are executed are static, they can be
invoked directly from the shell. These are the available properties
and methods:
.TP
.I void LoadAssembly(string assembly)
Loads the given assembly. This is equivalent to passing the compiler
the -r: flag with the specified string.
.TP
.I void LoadPackage(string package)
Imports the package specified. This is equivalent to invoking the
compiler with the -pkg: flag with the specified string.
.TP
.I string Prompt { get; set }
The prompt used by the shell. It defaults to the value "csharp> ".
.I string ContinuationPrompt { get; set; }
The prompt used by the shell when further input is required to
complete the expression or statement.
.TP
.I void ShowVars()
Displays all the variables that have been defined so far and their
types. In the csharp shell declaring new variables will shadow
previous variable declarations, this is different than C# when
compiled.
.I void ShowUsing()
Displays all the using statements in effect.
.I TimeSpan Time (Action a)
Handy routine to time the time that some code takes to execute. The
parameter is an Action delegate, and the return value is a TimeSpan.
For example:
.PP
.nf
csharp> Time (() => { for (int i = 0; i < 5; i++) Console.WriteLine (i);});
0
1
2
3
4
00:00:00.0043230
csharp>
.fi
.PP
The return value is a TimeSpan, that you can store in a variable for
benchmarking purposes.
.SH GUI METHODS AND PROPERTIES
In addition to the methods and properties available in the console
version there are a handful of extra properties available on the GUI
version. For example a "PaneContainer" Gtk.Container is exposed that
you can use to host Gtk# widgets while prototyping or the "MainWindow"
property that gives you access to the current toplevel window.
.SH STARTUP FILES
The C# shell will load all the Mono assemblies and C# script files
located in the ~/.config/csharp directory on Unix. The assemblies are
loaded before the source files are loaded.
.PP
C# script files are files
that have the extension .cs and they should only contain statements
and expressions, they can not contain full class definitions (at least
not as of Mono 2.0). Full class definitions should be compiled into
dlls and stored in that directory.
.SH AUTHORS
The Mono C# Compiler was written by Miguel de Icaza, Ravi Pratap,
Martin Baulig, Marek Safar and Raja Harinath. The development was
funded by Ximian, Novell and Marek Safar.
.SH LICENSE
The Mono Compiler Suite is released under the terms of the GNU GPL or
the MIT X11. Please read the accompanying `COPYING' file for details.
Alternative licensing for the compiler is available from Novell.
.SH SEE ALSO
gmcs(1), mcs(1), mdb(1), mono(1), pkg-config(1)
.SH BUGS
To report bugs in the compiler, you must file them on our bug tracking
system, at:
http://www.mono-project.com/Bugs
.SH MAILING LIST
The Mono Mailing lists are listed at http://www.mono-project.com/Mailing_Lists
.SH MORE INFORMATION
The Mono C# compiler was developed by Novell, Inc
(http://www.novell.com, http) and is based on the
ECMA C# language standard available here:
http://www.ecma.ch/ecma1/STAND/ecma-334.htm
.PP
The home page for the Mono C# compiler is at
http://www.mono-project.com/CSharp_Compiler information about the
interactive mode for C# is available in http://mono-project.com/CsharpRepl

68
man/disco.1 Normal file
View File

@@ -0,0 +1,68 @@
.\"
.\" disco manual page.
.\" (C) 2003 Novell, Inc.
.\" Author:
.\" Lluis Sanchez Gual (lluis@ximian.com)
.\"
.TH disco 1
.SH NAME
disco \- Mono's Web Service Discovery Tool
.SH SYNOPSIS
.PP
.B disco
[options] url
.SH DESCRIPTION
.I disco
is a tool for discovering web services and for retireving the documents that
describe those services.
.PP
.I url
is the location of a DISCO document, which includes a list of WSDL documents,
XML schemas and references to other DISCO documents.
.PP
.I disco
downloads the DISCO document and all referenced documents (unless
the
.I "-nosave"
option is specified), and saves them to disk.
.SH OPTIONS
The following options are available:
.TP
.I "-nologo"
Supress the startup logo.
.TP
.I "-nosave"
Do not save the discovered documents to disk. The default is to save the documents.
.TP
.I "-o:directory", "-out:directory"
The directory where to save the discovered documents.
By default, documents are saved in the current directory.
.TP
.I "-u:username", "-user:username"
The user name to use when connecting to the server.
.TP
.I "-p:password", "-password:password"
The password to use when connecting to the server.
.TP
.I "-d:domain", "-domain:domain"
The domain to use when connecting to the server.
.TP
.I "-proxy:url"
The url of the proxy server to use for http requests.
.TP
.I "-proxyusername:username"
The user name to use when connecting to the proxy.
.TP
.I "-proxypassword:password"
The password to use when connecting to the proxy.
.TP
.I "-proxydomain:domain"
The domain to use when connecting to the proxy.
.SH AUTHORS
Lluis Sanchez Gual (lluis@ximian.com)
.PP
.SH LICENSE
disco is released under the terms of the GNU GPL.
.PP
.SH SEE ALSO
wsdl(1), soapsuds(1), mono(1), mcs(1)

19
man/dtd2xsd.1 Normal file
View File

@@ -0,0 +1,19 @@
.TH "dtd2xsd" 1
.SH NAME
dtd2xsd \- XML Schema generator from XML document that contains DTD.
.SH SYNOPSIS
.B dtd2xsd
[options]
.I instance-xmlfile
.I optional-xsdfile
.SH DESCRIPTION
dtd2xsd generates an XML schema document from a document type definition (DTD).
Right now you have to specify instance XML file that references or contains
DTD. DTD itself is not readable with this tiny tool.
.PP
By default, it outputs resulting XML schema to console. If optional-xsdfile
parameter is specified, it outputs the result to the specified file.
.SH AUTHOR
Atsushi Enomoto <atsushi@ximian.com>
.SH SEE ALSO
mono(1)

121
man/gacutil.1 Normal file
View File

@@ -0,0 +1,121 @@
..\"
.\" gacutil manual page.
.\" (C) 2004 Novell, Inc.
.\" Author:
.\" Miguel de Icaza (miguel@gnu.org)
.\"
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
..
.TH gacutil "Mono 1.0"
.SH NAME
gacutil \- Global Assembly Cache management utility.
.SH SYNOPSIS
.PP
.B gacutil [-user] [command] [options]
.SH DESCRIPTION
\fIgacutil\fP is a tool used by developers to install versioned
assemblies into the system Global Assembly Cache (GAC) to become part
of the assemblies that are available for all applications at runtime.
.PP
Notice that they are not directly available to the compiler. The
convention is that assemblies must also be placed in a separate
directory to be accessed by the compiler. This is done with the
-package directive to gacutil.
.PP
The tool allows for installation, removal, and listing of the
contents of the assembly cache.
.PP
The GAC is relative to the Mono installation prefix:
mono_prefix/lib/mono.
.PP
.SH COMMANDS
.I -i <assembly_path> [-check_refs] [-package NAME] [-root ROOTDIR] [-gacdir GACDIR]
.Sp
Installs an assembly into the global assembly cache. <assembly_path>
is the name of the file that contains the assembly manifest
.Sp
The -package option can be used to also create a directory in in
prefix/lib/mono with the name NAME, and a symlink is created from
NAME/assembly_name to the assembly on the GAC. This is used so
developers can reference a set of libraries at once.
.Sp
The -root option is used to specify the "libdir" value of an installation
prefix which differs from the prefix of the system GAC.
Typical automake usage is "-root $(DESTDIR)$(prefix)/lib".
To access assemblies installed to a prefix other than the mono prefix,
it is necessary to set the MONO_GAC_PREFIX environment variable.
.Sp
The -gacdir option is included for backward compatibility but is not
recommended for new code. Use the -root option instead.
.Sp
The -check_refs option is used to ensure that the assembly being
installed into the GAC does not reference any non strong named
assemblies. Assemblies being installed to the GAC should not reference
non strong named assemblies, however the is an optional check.
.fi
.PP
.I "-l" [assembly_name] [-root ROOTDIR] [-gacdir GACDIR]
.Sp
Lists the contents of the global assembly cache. When the
<assembly_name> parameter is specified only matching assemblies are
listed.
.PP
.I "-u" <assembly_display_name> [-package NAME] [-root ROOTDIR] [-gacdir GACDIR]
.Sp
Uninstalls an assembly from the global assembly cache.
<assembly_display_name> is the name of the assembly (partial or
fully qualified) to remove from the global assembly cache. If a
partial name is specified all matching assemblies will be
uninstalled. As opposed to the install option that takes a filename,
this takes as an argument the assembly name, which looks like this:
.nf
MyLibrary.Something, version=1.0.0.0, publicKeyToken=xxxx,culture=neutral
.fi
.Sp
Notice that you can have spaces in the command line. There is no need
to quote them.
.Sp
Performs a greedy removal. If you only specify one
component like, "MyLibrary.Something", it will remove all versions of
the library.
.Sp
.I "-us" <assembly_path> [-package NAME] [-root ROOTDIR] [-gacdir GACDIR]
Uninstalls an assembly using the specified assembly's full name.
<assembly path> is the path to an assembly. The full assembly name
is retrieved from the specified assembly if there is an assembly in
the GAC with a matching name, it is removed. Unlike the -u option this
option takes a file name, like this:
.nf
Example: -us myDll.dll
.fi
.Sp
.I "-ul" <assembly_list_file> [-package NAME] [-root ROOTDIR] [-gacdir GACDIR]
Uninstalls one or more assemblies from the global assembly cache.
<assembly_list_file> is the path to a test file containing a list of
assembly names on separate lines.
.nf
Example -ul assembly_list.txt
.fi
.nf
assembly_list.txt contents:
assembly1,Version=1.0.0.0,Culture=en,PublicKeyToken=0123456789abcdef
assembly2,Version=2.0.0.0,Culture=en,PublicKeyToken=0123456789abcdef
.fi
.SH FILES
On Unix assemblies are loaded from the installation lib directory. If you set
`prefix' to /usr, the assemblies will be located in /usr/lib. On
Windows, the assemblies are loaded from the directory where mono and
mint live.
.PP
/etc/mono/config, ~/.mono/config
.PP
Mono runtime configuration file. See the mono-config(5) manual page
for more information.
.SH WEB SITE
Visit: http://www.go-mono.com for details
.SH SEE ALSO
.BR mcs(1), mono(1)

309
man/genxs.1 Normal file
View File

@@ -0,0 +1,309 @@
.\"
.\" genxs manual page.
.\" (C) Lluis Sanchez Gual (lluis@ximian.com)
.\"
.TH genxs 1
.SH NAME
genxs \- Mono's Xml Serializer Generator
.SH SYNOPSIS
.PP
.B genxs
configurationFile [destinationFolder]
.SH DESCRIPTION
.I genxs
is a tool for generating custom XML serialization writers and readers for
classes.
.PP
.I configurationFile
is configuration file which specifies several
information, such as the class for which to generate the reader and writer, the
name and namespace of the classes to generate, and a collection of hooks to
apply. By using hooks it is possible to customize the
behavior of the serializer without needing to modify the generated file, so you
can safely regenerate it if the source class is modified.
.PP
.I destinationFolder
specifies the folder where the files will be generated.
.PP
.B NOTE:
This tool only runs in the Mono runtime, since it uses some internal
classes not available in other runtimes.
.SH CONFIGURATION FILE FORMAT
The configuration file is an xml document based on the following grammar
("?" means optional, "*" 0 or more):
.PP
.nf
<configuration>
<serializer class="name" assembly="name"> *
<reader>name</reader> ?
<writer>name</writer> ?
<namespace>name</namespace> ?
<outFileName>name</outFileName> ?
<readerHooks> ?
<hook ...> *
</readerHooks>
<writerHooks> ?
<hook ...> *
</writerHooks>
</serializer>
</configuration>
.fi
.PP
A configuration file can have multiple "serializer" elements, each of which
specifies the class for which to generate a serializer together with several
generation options. The source class is specified in the following attributes:
.PP
.IP " *" 5
.I class
: name of the class (including namespace).
.IP " *" 5
.I assembly
: assembly name. It can include the complete path.
.PP
Generation options are specified in child elements:
.PP
.IP " *" 5
.I reader
: name of the reader class.
.IP " *" 5
.I noReader
: if "true", it does not generate reader class.
.IP " *" 5
.I writer
: name of the writer class.
.IP " *" 5
.I baseSerializer
: name of the base xml serializer class. This item is 2.0 only.
.IP " *" 5
.I implementation
: name of the serializer implementation class. This item is 2.0 only.
.IP " *" 5
.I noWriter
: if "true", it does not generate writer class.
.IP " *" 5
.I namespace
: namespace of the reader and writer classes.
.IP " *" 5
.I generateAsInternal
: if "true", it generates classes as internal.
.IP " *" 5
.I outFileName
: name of the generated file.
.IP " *" 5
.I readerHooks
: a list of hooks to apply to the reader.
.IP " *" 5
.I writerHooks
: a list of hooks to apply to the writer.
.SH SPECIFYING HOOKS
Using hooks you can customize the behavior of readers and writers.
A hook specification follows this grammar:
.PP
.nf
<hook type="name">
<select> ?
<typeName>name</typeName> ?
<typeAttribute>name</typeAttribute> *
<typeMember>name</typeMember> ?
</select>
<replace>source code</replace> ?
<insertBefore>source code</insertBefore> ?
<insertAfter>source code</insertAfter> ?
</hook>
.fi
.PP
The "type" attribute specifies the context in which the hook is applied. It can
be one of the following:
.PP
.IP " *" 5
.I attributes
: hook is applied where attributes are serialized/deserialized.
.IP " *" 5
.I elements
: hook is applied where elements are serialized/deserialized.
.IP " *" 5
.I unknownAttribute
: hook is applied where unknown attributes are processed.
.IP " *" 5
.I unknownElement
: hook is applied where unknown elements are processed.
.IP " *" 5
.I member
: hook is applied where a member is serialized/deserialized.
.IP " *" 5
.I type
: hook is applied for the whole type.
.PP
The "select" element specifies the classes and members to which the hook has
to be added. It can contain the following elements:
.PP
.IP " *" 5
.I typeName
: the class with that name will be selected (must include namespace)
.IP " *" 5
.I typeAttribute
: all classes which have that attribute applied will be selected (specify the
full attribute class name, including namespace). Several attribute names can be
specified.
.IP " *" 5
.I typeMember
: name of the class member for which the hook must be added.
.PP
The hook source code can be specified using any of the following elements:
.PP
.IP " *" 5
.I replace
: the provided source code will replace all serialization/deserialization
operations in the hook context.
.IP " *" 5
.I insertBefore
: the source code will be added before the hook context.
.IP " *" 5
.I insertAfter
: the source code will be added after the hook context.
.PP
When writing the code for a hook you can use some special variables that are
defined during the code generation process. The variables are the following:
.PP
.IP " *" 5
.I $TYPE:
name of the class being generated, without namespace.
.IP " *" 5
.I $FULLTYPE:
full name of the class being generated, including namespace.
.IP " *" 5
.I $OBJECT:
the object being serialized or deserialized. When using a replace
reader hook of type "type", the hook code must assign the deserialized object
to this variable.
.IP " *" 5
-I $ELEMENT:
name of the element of the object being serialized/deserialized.
.IP " *" 5
.I $NAMESPACE:
namespace of the element of the object being serialized/deserialized.
.IP " *" 5
.I $MEMBER:
name of the member being serialized/deserialized. Only valid in the "member"
context.
.SH HOOK EXAMPLES
The following example adds a call to a Validate method after the deserialization
of any object:
.PP
.nf
<hook type="type">
<insertAfter>
System.Xml.Schema.XmlSchema.Validate$TYPE ($OBJECT);
</insertAfter>
</hook>
.fi
.PP
This example specifies the code to be used to deserialize the XmlSchema class:
.PP
.nf
<hook type="type">
<select>
<typeName>System.Xml.Schema.XmlSchema</typeName>
</select>
<replace>
$OBJECT = System.Xml.Schema.XmlSchema.Read (Reader, null);
</replace>
</hook>
.fi
.PP
That one specifies the code to be used to read XmlSchema instances:
.PP
.nf
<hook type="type">
<select>
<typeName>System.Xml.Schema.XmlSchema</typeName>
</select>
<replace>$OBJECT.Write (Writer);</replace>
</hook>
.fi
.PP
With this two hooks the serializer will print some information when serializing
the class "MyClass":
.PP
.nf
<hook type="type">
<select>
<typeName>MyNamespace.MyClass</typeName>
</select>
<insertBefore>Console.WriteLine ("Serializing MyClass");</replace>
<insertAfter>Console.WriteLine ("MyClass serialized");</insertAfter>
</hook>
<hook type="member">
<select>
<typeName>MyNamespace.MyClass</typeName>
</select>
<insertAfter>
Console.WriteLine ("Serialized member $MEMBER");
</insertAfter>
</hook>
.fi
.PP
This hook writes an additional element for all types that have the custom
attribute "MyAttribute":
.PP
.nf
<hook type="elements">
<select>
<typeAttribute>MyNamespace.MyAttribute</typeAttribute>
</select>
<insertAfter>
Writer.WriteStartElement ("privateData");
Writer.WriteString ($OBJECT.PrivateData);
Writer.WriteEndElement ();
</insertAfter>
</hook>
.fi
.SH CONFIGURATION FILE EXAMPLE
This is the configuration file used to generate the serializer for ServiceDescription:
.PP
.nf
<configuration>
<serializer class="System.Web.Services.Description.ServiceDescription" assembly="System.Web.Services">
<reader>ServiceDescriptionReaderBase</reader>
<writer>ServiceDescriptionWriterBase</writer>
<namespace>System.Web.Services.Description</namespace>
<outFileName>ServiceDescriptionSerializerBase.cs</outFileName>
<readerHooks>
<hook type="unknownElement">
<select>
<typeAttribute>System.Web.Services.Configuration.XmlFormatExtensionPointAttribute</typeAttribute>
</select>
<replace>ServiceDescription.ReadExtension (Reader, $OBJECT);</replace>
</hook>
<hook type="type">
<select>
<typeName>System.Xml.Schema.XmlSchema</typeName>
</select>
<replace>$OBJECT = System.Xml.Schema.XmlSchema.Read (Reader, null);</replace>
</hook>
</readerHooks>
<writerHooks>
<hook type="elements">
<select>
<typeAttribute>System.Web.Services.Configuration.XmlFormatExtensionPointAttribute</typeAttribute>
</select>
<insertBefore>ServiceDescription.WriteExtensions (Writer, $OBJECT);</insertBefore>
</hook>
<hook type="type">
<select>
<typeName>System.Xml.Schema.XmlSchema</typeName>
</select>
<replace>$OBJECT.Write (Writer);</replace>
</hook>
</writerHooks>
</serializer>
</configuration>
.fi
.SH AUTHORS
Lluis Sanchez Gual (lluis@ximian.com)
.PP
.SH LICENSE
GenXS is released under the terms of the GNU GPL.
.PP
.SH SEE ALSO
mono(1), mcs(1), sgen(1)

75
man/httpcfg.1 Normal file
View File

@@ -0,0 +1,75 @@
.\"
.\" httpcfg manual page.
.\" Copyright 2006 Novell
.\" Author:
.\" Miguel de Icaza (miguel@novell.com)
.\"
.TH Mono "httpcfg"
.SH NAME
httpcfg \- Mono Certificate Management for HttpListener
.SH SYNOPSIS
.PP
.B httpcfg [options] certificate
.SH DESCRIPTION
This tool is used to manage the certificates used by the HttpListener
embeddable server class when the HttpListener is configured as an
HTTPS server instead of an HTTP server.
.PP
You must select one of the possible actions: add, delete or list.
.PP
When adding a certificate (-add), you must provide the following
information: a certificate (with the -cert flag) a Private Key file
(with the -pvk argument, the filename is typically "key") and a port
number (with the -port flag).
.PP
When deleting a certificate (-del or -delete) you need to provide the
port number.
.SH PARAMETERS
.TP
.I "-add"
Adds a new certificate/private key combination for being used at a
given port by the HttpListener API.
.TP
.I "-del," "-delete"
Deletes the certificates associated for the port specified (must be
specified separatedly).
.TP
.I "-list"
List all known certificates.
.TP
.I "-port PORT"
Specifies the port to add certificates to, or remove certificates
from.
.TP
.I "-pvk FILE"
Specifies the Private Key file.
.TP
.I "-cert CERT"
Specifies the certificate file to use.
.SH EXAMPLES
.nf
httpcfg -add -port 8081 -pvk myfile.pvk -cert MyCert
.fi
.PP
For more details on creating the certificate file and the private key,
see the following web page:
.PP
http://www.mono-project.com/UsingClientCertificatesWithXSP
.SH FILES
The certificates are stored in the ~/.mono/httplistener directory
.SH AUTHOR
.B httpcfg
was written by Gonzalo Paniagua.
.SH COPYRIGHT
Copyright (C) 2006 Novell.
.SH MAILING LISTS
Visit http://lists.ximian.com/mailman/listinfo/mono-devel-list for details.
.SH WEB SITE
Visit http://www.mono-project.com for details
.SH SEE ALSO
.B makecert(1), signcode(1), cert2spc(1)
.PP
The private key format:
.nf
http://www.drh-consultancy.demon.co.uk/pvk.html
.fi

68
man/ilasm.1 Normal file
View File

@@ -0,0 +1,68 @@
.TH "ilasm" 1
.SH NAME
ilasm, ilasm2 \- Mono IL assembler
.SH SYNOPSIS
.B ilasm
[option] [source-files]
.PP
.B ilasm2
[option] [source-files]
.SH DESCRIPTION
ilasm is the Mono ILAsm assembler. You can pass one or more options to
drive the compiler, and a set of source files.
.PP
Use \fIilasm\fR to generate 1.0 assemblies and use \fIilasm2\fR to
assemble programs that use the 2.0 features (generics).
.PP
The Mono ILAsm assembler accepts options starting with / or - for mosted
options.
.PP
The Mono ILAsm assembler generates images (.exe and .dll files) that contain
CIL byte code that can be executed by any system that implemented a Common
Language Infrastructure virtual machine.
.SH OPTIONS
.TP
.B \//output:<file_name>
Specify the output file name.
.TP
.B \//exe
Generate an exe
.TP
.B \//dll
Generate a library
.TP
.B \//scan_only
Just scan the IL code and display tokens.
.TP
.B \//show_tokens
Show tokens as they are parsed.
.TP
.B \//show_method_def
Display method information when a method is defined.
.TP
.B \//show_method_ref
Display method information when a method is referenced
.TP
.B \//key:KEYFILE
Strongname (sign) the output assembly using the key pair present in
the specified strong name key file (snk). A full key pair is required
(i.e. delay signing is done using a .publickey directive in the sources).
.TP
.B \//key:@CONTAINER
Strongname (sign) the output assembly using the key pair present in
the specified container.
.TP
.B \--about
Display information about ilasm
.TP
.B \--version
Display ilasm version
.SH SEE ALSO
.BR mono(1), mcs(1)
.SH COPYRIGHT
Copyright (C) 2004, 2007 Novell, Inc (http://www.novell.com)
.SH MAILING LISTS
Visit http://lists.ximian.com/mailman/listinfo/mono-devel-list for details.
.SH WEB SITE
Visit: http://www.mono-project.com for details

87
man/lc.1 Normal file
View File

@@ -0,0 +1,87 @@
.\"
.\" lc manual page.
.\" (C) 2009 Carlo Kok
.\"
.\" Author:
.\" Carlo Kok (ck@remobjects.com)
.\"
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
..
.TH lc "Mono 2.6"
.SH NAME
lc \- Mono License Compiler
.SH SYNOPSIS
.PP
.B lc -c filename -t targetassembly [-i reference...] [-v] [-o outputpath] [-nologo]
.SH DESCRIPTION
\fIlc\fP tool is a license compiler for Mono. It's used to convert a
licenses.licx file to a resource that can be embedded into an executable.
.PP
When using commercial components for .NET they often require a license
resource at runtime to make sure the developer was licensed to use this
control. The most common way of making sure the component was properly
licensed is by using license resources. At compile time the developer
uses the \fIlc\fP tool to convert a licenses.licx file to a
programname.exe.licenses file and embed that as a managed resource
during compilation.
.SH RUNTIME OPTIONS
The following options are available:
.TP
\fB--complist=filename\fR, \fB-c filename\fR
This option is used to specify the input file, the licenses.licx file
to create a license reesource for. This option is required. The license
compiler will read each line in this file and try to load the types
specified on that line.
.TP
\fB--target=assemblyname\fR, \fB-t targetassembly\fR
full assembly name with file extension for the target assembly. The
license compiler uses this as a key when compiling the licenses. It
has to match the assembly the resource will be embedded in. This option
is required.
.TP
\fB--load=reference\fR, \fB-i reference\fR
Assembly reference to load before trying to compile a license. This
option is needed for assemblies where the references are not in the
gac. Compilers should pass all references to the license compiler.
.TP
\fB--verbose,\fR, \fB-v\fR
Gives more verbose output about the license compiling process.
.TP
\fB--help\fR, \fB-h\fR
Displays usage instructions.
.TP
\fB--outdir=path\fR, \fB-o path\fR
Target path file the licenses resource. By default the license
compiler emits the resource in the current directory. The filename
will always match the target assembly passed to --target with .licenses
added.
.TP
\fB--nologo\fR
Do not emit the "Mono License Compiler" logo on stdout while compilng.
.SH LICENSE FILES
The format for the license files (licenses.licx) is the following:
.nf
# comment
namespace.type, assemblyname
namespace.type, full-assemblyname
.fi
.Sp
All lines starting with a # are ignored. the first form requires
that the assembly was loaded through the --load,-i option but
does not require the full assembly name, only the first part.
The second form requires the full assembly name including locale,
version and publickeytoken.
.SH MAILING LISTS
Mailing lists are listed at the
http://www.mono-project.com/Mailing_Lists
.SH WEB SITE
http://www.mono-project.com
.SH SEE ALSO
.PP
mono(1), mcs(1)

72
man/macpack.1 Normal file
View File

@@ -0,0 +1,72 @@
..\"
.\" macpack manual page.
.\" (C) 2004 Geoff Norton
.\" Author:
.\" Geoff Norton (gnorton@customerdna.com)
.\"
.de Sp \" Vertical space (when we can't use .PP)
.if t .sp .5v
.if n .sp
..
.TH macpack "Mono 1.0"
.SH NAME
macpack \- Macintosh OS X Packager for managed gui assemblies
.SH SYNOPSIS
.PP
.B macpack [options] assembly
.SH DESCRIPTION
\fImacpack\fP is a tool used to package managed assemblies (like
System.Windows.Forms or Cocoa#) that require gui availability for deployment
on Mac OS X.
.PP
macpack will prepare a OS X compatible bundle from the provided assembly
and resources. The bundle will include the specified assembly as well
as any of the provided resources (specified with the -resource: switch).
.PP
Developers can specify the kind of application to produce using the
-mode: argument. This controls how the environment in the Mono class
libraries is setup.
.PP
.SH OPTIONS
.I "-a assembly"
.Sp
This option tells macpack where the managed assembly that you
want to bundle resides. This option is also used to point to the shell
script to launch in the case of a X11/Gtk# application.
.Sp
This is the same as just passing the assembly as an argument.
.Sp
.I "-m [winforms,x11,console,cocoa]"
or
.I "-mode:[winforms,x11,console,cocoa]"
.Sp
A value indicating the kind of application: WinForms is a Winforms
application running on Quartz; X11 is an application that requires
the X11 server to run; console is a non-graphical application; cocoa
is an application based on Cocoa#
.Sp
.I "-n NAME"
or
.I "-appname:NAME"
.Sp
This option specifies the application name of the emitted bundle.
This is what you will see in Finder.
.Sp
.I "-o DIRECTORY"
or
.I "-output:DIRECTORY"
.Sp
This option specifies the path to output the generated Application.
.Sp
.I "-r RESOURCE"
or
.I "-resource:RESOURCE"
.Sp
This option can be specified multiple times. It will place a copy of each resource
into the bundles resources directory. Alternatively, you can use a
comma separated list of resources.
.fi
.SH AUTHOR
Geoff Norton
.SH WEB SITE
Visit: http://www.mono-project.com for details

Some files were not shown because too many files have changed in this diff Show More