Click here to Skip to main content
Click here to Skip to main content
Add your own
alternative version

Observer Pattern in .NET

, 9 Mar 2004
A mechanism for drastically reducing coupling between interacting classes
observer.zip
ObserverPatternClassic
bin
Debug
ObserverPatternClassic.exe
ObserverPatternClassic.pdb
obj
Debug
temp
TempPE
ObserverPatternClassic.pdb
ObserverPatternClassic.exe
ObserverPatternClassic.exe.incr
App.ico
ObserverPatternClassic.csproj.user
ObserverPatternClassic.suo
observernet.zip
ObserverPattern
bin
Debug
ObserverPattern.exe
ObserverPattern.pdb
obj
Debug
temp
ObserverPattern.projdata
TempPE
ObserverPattern.exe
ObserverPattern.exe.incr
ObserverPattern.pdb
App.ico
ObserverPattern.csproj.user
ObserverPattern.suo
observers.zip
Observers
observer.NET.zip
observer.zip
using System.Reflection;
using System.Runtime.CompilerServices;

//
// 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("")]
[assembly: AssemblyDescription("")]
[assembly: AssemblyConfiguration("")]
[assembly: AssemblyCompany("")]
[assembly: AssemblyProduct("")]
[assembly: AssemblyCopyright("")]
[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("1.0.*")]

//
// 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("")]

By viewing downloads associated with this article you agree to the Terms of Service and the article's licence.

If a file you wish to view isn't highlighted, and is a text file (not binary), please let us know and we'll add colourisation support for it.

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

About the Author

Sunil Kumar K.S
Web Developer
United States United States
Sunil Kumar Works for Wipro Technologies, one of the leading software services company in the world. He is a Microsoft Certified Solution Developer(MCSD) in .NET

| Advertise | Privacy | Mobile
Web04 | 2.8.140718.1 | Last Updated 10 Mar 2004
Article Copyright 2004 by Sunil Kumar K.S
Everything else Copyright © CodeProject, 1999-2014
Terms of Service
Layout: fixed | fluid