An ADO.NET multi-database, multi-tier solution

using System;
using System.Reflection;
using System.Runtime.CompilerServices;
using System.Runtime.InteropServices;
using System.Security.Permissions;

//
// General Information about an assembly is controlled through the following 
// set of attributes. Change these attribute values to modify the information
// associated with an assembly.
//
[assembly: AssemblyTitle("MultiTier Example Business")]
[assembly: AssemblyDescription("")]
[assembly: AssemblyConfiguration("")]
[assembly: AssemblyCompany("Jochen Jonckheere")]
[assembly: AssemblyProduct("MultiTier")]
[assembly: AssemblyCopyright("Copyright � 2004 Jochen Jonckheere")]
[assembly: AssemblyTrademark("")]
[assembly: AssemblyCulture("")]		

//
// Version information for an assembly consists of the following four values:
//
//      Major Version
//      Minor Version 
//      Build Number
//      Revision
//
// You can specify all the values or you can default the Revision and Build Numbers 
// by using the '*' as shown below:

[assembly: AssemblyVersion("0.1.100.*")]

//
// In order to sign your assembly you must specify a key to use. Refer to the 
// Microsoft .NET Framework documentation for more information on assembly signing.
//
// Use the attributes below to control which key is used for signing. 
//
// Notes: 
//   (*) 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 
//       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 which is
//       %Project Directory%\obj\<configuration>. For example, if your KeyFile is
//       located in the project directory, you would specify the AssemblyKeyFile 
//       attribute as [assembly: AssemblyKeyFile("..\\..\\mykey.snk")]
//   (*) Delay Signing is an advanced option - see the Microsoft .NET Framework
//       documentation for more information on this.
//
[assembly: AssemblyDelaySign(false)]
[assembly: AssemblyKeyFile("")]
[assembly: AssemblyKeyName("")]

//
// CLS-compliant
//
//The Common Language Specification (CLS) defines naming restrictions,data types,
//and rules to which assemblies must conform if they are to be accessible across
//programming languages. Good design dictates that all assemblies explicitly indicate
//CLS compliance with System.CLSCompliantAttribute. If the attribute is not present 
//on an assembly, the assembly is not compliant.
[assembly:CLSCompliant(true)]

//
// ComVisibleAttribute 
//
//The ComVisibleAttribute attribute determines how COM clients access managed code. 
//Good design dictates that assemblies explicitly indicate COM visibility. 
//COM visibility can be set for an entire assembly and then overridden for individual
//types and type members. If the attribute is not present, the contents of the assembly
//are visible to COM clients.
[assembly:ComVisible(false)]


//
// Security
//
[assembly:SecurityPermissionAttribute(SecurityAction.RequestMinimum, Flags = SecurityPermissionFlag.Execution)]