source: Scheduling/trunk/cs/bsdx0200GUISourceCode/AssemblyInfo.cs@ 1015

Last change on this file since 1015 was 1011, checked in by Sam Habiel, 14 years ago

UCPatientAppts: Fixes printing empty table bug reported by EHS.
DAccessTemplate: Various usability improvements.
CGDocumentManager: Fixed Delegate code so that it can operate asynchronously
CGAVView: Some temporary fixes (not totally usable): Added non-functional Delete Slots menu option; Added Background worker for saving acccess slots
In the future, Delete Slots will work; and will use ADO.net Updatable datatable for saving access slots.
calendarGrid: just some comments for now
AssemblyInfo: bumped version up to v1.4.2

File size: 2.6 KB
RevLine 
[614]1using System.Reflection;
2using System.Runtime.CompilerServices;
[789]3using System.Runtime.InteropServices;
[614]4
5//
6// General Information about an assembly is controlled through the following
7// set of attributes. Change these attribute values to modify the information
8// associated with an assembly.
9//
[789]10[assembly: AssemblyTitle("Clinical Scheduling")]
11[assembly: AssemblyDescription("Windows Scheduling Application for VistA")]
[614]12[assembly: AssemblyConfiguration("")]
[788]13[assembly: AssemblyCompany("WorldVistA")]
[614]14[assembly: AssemblyProduct("")]
15[assembly: AssemblyCopyright("")]
16[assembly: AssemblyTrademark("")]
17[assembly: AssemblyCulture("")]
18
19//
20// Version information for an assembly consists of the following four values:
21//
22// Major Version
23// Minor Version
24// Build Number
25// Revision
26//
27// You can specify all the values or you can default the Revision and Build Numbers
28// by using the '*' as shown below:
29
[1011]30[assembly: AssemblyVersion("1.4.2.*")]
[614]31
32//
33// In order to sign your assembly you must specify a key to use. Refer to the
34// Microsoft .NET Framework documentation for more information on assembly signing.
35//
36// Use the attributes below to control which key is used for signing.
37//
38// Notes:
39// (*) If no key is specified, the assembly is not signed.
40// (*) KeyName refers to a key that has been installed in the Crypto Service
41// Provider (CSP) on your machine. KeyFile refers to a file which contains
42// a key.
43// (*) If the KeyFile and the KeyName values are both specified, the
44// following processing occurs:
45// (1) If the KeyName can be found in the CSP, that key is used.
46// (2) If the KeyName does not exist and the KeyFile does exist, the key
47// in the KeyFile is installed into the CSP and used.
48// (*) In order to create a KeyFile, you can use the sn.exe (Strong Name) utility.
49// When specifying the KeyFile, the location of the KeyFile should be
50// relative to the project output directory which is
51// %Project Directory%\obj\<configuration>. For example, if your KeyFile is
52// located in the project directory, you would specify the AssemblyKeyFile
53// attribute as [assembly: AssemblyKeyFile("..\\..\\mykey.snk")]
54// (*) Delay Signing is an advanced option - see the Microsoft .NET Framework
55// documentation for more information on this.
56//
57[assembly: AssemblyDelaySign(false)]
58[assembly: AssemblyKeyFile("")]
59[assembly: AssemblyKeyName("")]
[1011]60[assembly: AssemblyFileVersionAttribute("1.4.2.0")]
[789]61[assembly: ComVisibleAttribute(false)]
Note: See TracBrowser for help on using the repository browser.