Mercurial > repos > IBDev-IBBoard.WarFoundry.GUI.WinForms
comparison AssemblyInfo.cs @ 0:7dd160dacb60
Initial commit of WarFoundry code
author | IBBoard <dev@ibboard.co.uk> |
---|---|
date | Fri, 19 Dec 2008 15:57:51 +0000 |
parents | |
children | 8379fa964dd3 |
comparison
equal
deleted
inserted
replaced
-1:000000000000 | 0:7dd160dacb60 |
---|---|
1 using System.Reflection; | |
2 using System.Runtime.CompilerServices; | |
3 | |
4 // | |
5 // General Information about an assembly is controlled through the following | |
6 // set of attributes. Change these attribute values to modify the information | |
7 // associated with an assembly. | |
8 // | |
9 [assembly: AssemblyTitle("WarFoundry Army Builder")] | |
10 [assembly: AssemblyDescription("WarFoundry is an army creator/designer/builder designed to cover a wide range of war game systems")] | |
11 [assembly: AssemblyConfiguration("")] | |
12 [assembly: AssemblyCompany("")] | |
13 [assembly: AssemblyProduct("WarFoundry")] | |
14 [assembly: AssemblyCopyright("IBBoard, 2007")] | |
15 [assembly: AssemblyTrademark("")] | |
16 [assembly: AssemblyCulture("")] | |
17 | |
18 // | |
19 // Version information for an assembly consists of the following four values: | |
20 // | |
21 // Major Version | |
22 // Minor Version | |
23 // Build Number | |
24 // Revision | |
25 // | |
26 // You can specify all the values or you can default the Revision and Build Numbers | |
27 // by using the '*' as shown below: | |
28 | |
29 [assembly: AssemblyVersion("1.0.0.*")] | |
30 | |
31 // | |
32 // In order to sign your assembly you must specify a key to use. Refer to the | |
33 // Microsoft .NET Framework documentation for more information on assembly signing. | |
34 // | |
35 // Use the attributes below to control which key is used for signing. | |
36 // | |
37 // Notes: | |
38 // (*) If no key is specified, the assembly is not signed. | |
39 // (*) KeyName refers to a key that has been installed in the Crypto Service | |
40 // Provider (CSP) on your machine. KeyFile refers to a file which contains | |
41 // a key. | |
42 // (*) If the KeyFile and the KeyName values are both specified, the | |
43 // following processing occurs: | |
44 // (1) If the KeyName can be found in the CSP, that key is used. | |
45 // (2) If the KeyName does not exist and the KeyFile does exist, the key | |
46 // in the KeyFile is installed into the CSP and used. | |
47 // (*) In order to create a KeyFile, you can use the sn.exe (Strong Name) utility. | |
48 // When specifying the KeyFile, the location of the KeyFile should be | |
49 // relative to the project output directory which is | |
50 // %Project Directory%\obj\<configuration>. For example, if your KeyFile is | |
51 // located in the project directory, you would specify the AssemblyKeyFile | |
52 // attribute as [assembly: AssemblyKeyFile("..\\..\\mykey.snk")] | |
53 // (*) Delay Signing is an advanced option - see the Microsoft .NET Framework | |
54 // documentation for more information on this. | |
55 // | |
56 [assembly: AssemblyDelaySign(false)] | |
57 [assembly: AssemblyKeyFile("")] | |
58 [assembly: AssemblyKeyName("")] |