[Mono-list] How to create valid AssemblyInfo.cs file
John BouAntoun
John.BouAntoun@rogen.com.au
Fri, 14 Feb 2003 08:25:58 +1100
You could try using a windows box that autogenerates one for you (using =
Sharp Develop) or you could copy and paste this template here:
using System.Reflection;
using System.Runtime.CompilerServices;
//
// General Information about an assembly is controlled through the =
following=20
// set of attributes. Change these attribute values to modify the =
information
// associated with an assembly.
//
[assembly: AssemblyTitle("")]
[assembly: AssemblyDescription("")]
[assembly: AssemblyConfiguration("")]
[assembly: AssemblyCompany("")]
[assembly: AssemblyProduct("")]
[assembly: AssemblyCopyright("")]
[assembly: AssemblyTrademark("")]
[assembly: AssemblyCulture("")]=20
//
// Version information for an assembly consists of the following four =
values:
//
// Major Version
// Minor Version=20
// Build Number
// Revision
//
// You can specify all the values or you can default the Revision and =
Build Numbers=20
// by using the '*' as shown below:
[assembly: AssemblyVersion("1.0.0")]
//
// In order to sign your assembly you must specify a key to use. Refer =
to the=20
// Microsoft .NET Framework documentation for more information on =
assembly signing.
//
// Use the attributes below to control which key is used for signing.=20
//
// Notes:=20
// (*) If no key is specified, the assembly is not signed.
// (*) KeyName refers to a key that has been installed in the Crypto =
Service
// Provider (CSP) on your machine. KeyFile refers to a file which =
contains
// a key.
// (*) If the KeyFile and the KeyName values are both specified, the=20
// following processing occurs:
// (1) If the KeyName can be found in the CSP, that key is used.
// (2) If the KeyName does not exist and the KeyFile does exist, the key =
// in the KeyFile is installed into the CSP and used.
// (*) In order to create a KeyFile, you can use the sn.exe (Strong =
Name) utility.
// When specifying the KeyFile, the location of the KeyFile should be
// relative to the "project output directory". The location of the =
project output
// directory is dependent on whether you are working with a local or web =
project.
// For local projects, the project output directory is defined as
// <Project Directory>\obj\<Configuration>. For example, if your KeyFile =
is
// located in the project directory, you would specify the =
AssemblyKeyFile=20
// attribute as [assembly: AssemblyKeyFile("..\\..\\mykey.snk")]
// For web projects, the project output directory is defined as
// %HOMEPATH%\VSWebCache\<Machine Name>\<Project =
Directory>\obj\<Configuration>.
// (*) Delay Signing is an advanced option - see the Microsoft .NET =
Framework
// documentation for more information on this.
//
[assembly: AssemblyDelaySign(false)]
[assembly: AssemblyKeyFile("")]
[assembly: AssemblyKeyName("")]
-----Original Message-----
From: Michael Schwery [mailto:cleamcpb@hotmail.com]
Sent: Friday, 14 February 2003 4:00 AM
To: mono-list@lists.ximian.com
Subject: [Mono-list] How to create valid AssemblyInfo.cs file
I created a app on mono and tried to run it under
.net but it complains that it can't find a AssenblyInfo file. How can I =
create a vaild one?
Tired of spam? Get advanced junk mail protection with MSN 8. =
_______________________________________________ Mono-list maillist - =
Mono-list@lists.ximian.com =
http://lists.ximian.com/mailman/listinfo/mono-list=20