Re: Where is the log4net.Config.XmlConfigurator?
In previous releases of log4net this class was called DOMConfigurator. But this class will indeed be renamed to XmlConfigurator in the next release ... Hope this helps, Gert - Original Message - From: "Phillip Haack" <[EMAIL PROTECTED]> To: Sent: Wednesday, May 19, 2004 10:20 PM Subject: Where is the log4net.Config.XmlConfigurator? Hi all, According to the document ( http://logging.apache.org/log4net/release/manual/configuration.html) there is a log4net.Config.XmlConfigurator class, but I can't seem to find this class anywhere. There's no file in the source code corresponding to this class. Any help? Thanks! Phil Haack
Re: Cannot get Log4Net to compile using Nant or VC 2003
Torben, You need a more recent version of NAnt : http://nant.sourceforge.net/nightly/builds. Gert - Original Message - From: "Torben Sorensen" <[EMAIL PROTECTED]> To: "Log4NET User" Sent: Friday, August 06, 2004 7:44 PM Subject: Cannot get Log4Net to compile using Nant or VC 2003 Hi All, I have gotten the latest version of log4net via CVS. After a lot of digging, I've put the log4net directory in the path, and I've tried the 'build.cmd' command again. I'm still getting the same error: C:\CVS\log4net\logging-log4net>build.cmd LOG4NET_DIR is C:\CVS\log4net\logging-log4net NANTEXE_PATH is nant.exe BUILD_FILE is C:\CVS\log4net\logging-log4net\log4net.build NAnt 0.84 (Build 0.84.1455.0; net-1.0.win32; release; 12/26/2003) Copyright (C) 2001-2003 Gerry Shaw http://nant.sourceforge.net Buildfile: file:///C:/CVS/log4net/logging-log4net/log4net.build Target(s) specified: compile-all check-current-build-config: BUILD FAILED C:\CVS\log4net\logging-log4net\log4net.include(185,10): [if] at least one if condition must be set (propertytrue, targetexists, etc...): Total time: 0.3 seconds. This electronic message transmission, including attachments, is for the exclusive use of the individuals to which this e-mail is addressed and is to be reviewed and used exclusively for authorized company purposes. This transmission may contain proprietary, confidential or privileged information. If you are not the intended recipient of this transmission, you are hereby notified that any use, copying, disclosure, dissemination, distribution or taking of any action in reliance upon the contents of this transmission is strictly prohibited. If you believe you may have received this electronic message in error, please notify the sender immediately by return email and delete or destroy the original message and/or any copy of it from your computer system and/or your files. Thank you.
Re: Building using NAnt
Dennis, Did you get the sources from CVS ? I think you somehow have an extra linefeed between each line, not sure what causes this (I also had this once, and have forgotten how I fixed this). As a result of this the XML docs will be like this : /// /// Appender that logs to a database. /// causing csc to output warnings Hope this helps, Gert PS. Please do not cross-post to both the user and dev mailing lists. From: "Denis, Rich" <[EMAIL PROTECTED]> To: "Log4NET User" ; "Log4NET Dev" Sent: Saturday, August 21, 2004 1:33 AM Subject: Building using NAnt Hello, I have gotten the latest source files for log4net and tried using the latest source from NAnt(0.85.1684.0) to build the project. Something seems to go wrong when I build. Can anyone look at this and tell me why it is failing. It seems to be an XML doc related issue. You will see the Summary tag not matching as the error throughout. Any help would be greatly appreciated. Thanks. Here is the output generated. NAnt 0.85 (Build 0.85.1684.0; net-1.0.win32; dev; 8/11/2004) Copyright (C) 2001-2004 Gerry Shaw http://nant.sourceforge.net Buildfile: file:///C:/Development/OpenSource/logging-log4net/log4net.build Target(s) specified: compile-all check-current-build-config: set-build-configuration: set-debug-build-configuration: check-current-build-config: set-build-configuration-flags: check-current-build-config: set-framework-configuration: check-bin-dir: check-doc-dir: check-sdkdoc-dir: check-sdkdoc-debug: check-current-build-config: check-build-debug: check-build-defines: set-net-1.1-runtime-configuration: compile-all: [echo] Compiling all build configurations for all runtime configurations. set-debug-build-configuration: check-current-build-config: set-build-configuration-flags: compile-build: [echo] Compiling all framework versions for the debug build configuration. check-bin-dir: check-doc-dir: check-sdkdoc-dir: check-sdkdoc-debug: check-current-build-config: check-build-debug: check-build-defines: set-netcf-1.0-runtime-configuration: check-log4net-basedir: check-current-bin-dir: clean-current-bin-dir: [echo] Cleaning the bin/netcf/1.0/debug binaries directory. [delete] Deleting directory 'C:\Development\OpenSource\logging-log4net\bin\ne tcf\1.0\debug'. [mkdir] Creating directory 'C:\Development\OpenSource\logging-log4net\bin\ne tcf\1.0\debug'. compile-netcf-1.0: [csc] Compiling 178 files to 'C:\Development\OpenSource\logging-log4net\bi n\netcf\1.0\debug\log4net.dll'. [csc] c:\Development\OpenSource\logging-log4net\src\Appender\AdoNetAppende r.cs(285,9): error CS1570: XML comment on 'log4net.Appender.AdoNetAppender.AdoNe tAppender()' has badly formed XML -- 'End tag 'remarks' does not match the start tag 'member'. [csc] [csc] c:\Development\OpenSource\logging-log4net\src\Appender\AdoNe tAppender.cs(673,9): error CS1570: XML comment on 'log4net.Appender.AdoNetAppend er.ActivateOptions()' has badly formed XML -- 'End tag 'remarks' does not match the start tag 'member'. [csc] [csc] c:\Development\OpenSource\logging-log4net\src\Appender\AdoNe tAppender.cs(735,9): error CS1570: XML comment on 'log4net.Appender.AdoNetAppend er.OnClose()' has badly formed XML -- 'End tag 'remarks' does not match the star t tag 'member'. [csc] [csc] c:\Development\OpenSource\logging-log4net\src\Appender\AdoNe tAppender.cs(793,9): error CS1570: XML comment on 'log4net.Appender.AdoNetAppend er.SendBuffer(log4net.Core.LoggingEvent[])' has badly formed XML -- 'End tag 're marks' does not match the start tag 'member'. [csc] [csc] c:\Development\OpenSource\logging-log4net\src\Appender\AdoNe tAppender.cs(911,9): error CS1570: XML comment on 'log4net.Appender.AdoNetAppend er.AddParameter(log4net.Appender.AdoNetAppenderParameter)' has badly formed XML -- 'End tag 'remarks' does not match the start tag 'member'. [csc] [csc] c:\Development\OpenSource\logging-log4net\src\Appender\AdoNe tAppender.cs(951,9): error CS1570: XML comment on 'log4net.Appender.AdoNetAppend er.SendBuffer(System.Data.IDbTransaction, log4net.Core.LoggingEvent[])' has badl y formed XML -- 'End tag 'remarks' does not match the start tag 'member'. [csc] [csc] c:\Development\OpenSource\logging-log4net\src\Appender\AdoNe tAppender.cs(1077,9): error CS1570: XML comment on 'log4net.Appender.AdoNetAppen der.GetLogStatement(log4net.Core.LoggingEvent)' has badly formed XML -- 'End tag 'returns' does not match the start tag 'member'. [csc] [csc] c:\Development\OpenSource\logging-log4net\src\Appender\AdoNe tAppender.cs(1113,9): error CS1570: XML comment on 'log4net.Appender.AdoNetAppen der.InitializeDatabaseConnection()' has badly formed XML -- 'End tag 'summary' d oes not match the start tag 'member'. [csc] [csc] c:\Development\OpenSource\logging-log4net\src\Appender\AdoNe tAppender.cs(1215,9): error CS1570: XML comment on 'log4net.Appender.AdoNetAppen der.InitializeDatabaseCommand()' has badly formed X
Re: Build problems with CVS code
Try using a recent nightly build of NAnt : http://nant.sourceforge.net/nightly/builds Gert - Original Message - From: "Shai Berger" <[EMAIL PROTECTED]> To: Sent: Sunday, September 12, 2004 7:51 PM Subject: Build problems with CVS code Hi guys, I'm trying to evaluate log4net for use in a project here, and I encountered some problems in the first attempts to build; I hope to get some advice from the more experienced folks here. I checked out the source from CVS, and first tried to build it with NAnt. This failed miserably; the latest stable NAnt (0.84) cannot read the build files, because the syntax they use for (test="...") is not (no longer?) supported. NAnt expects to see , and the files have . What version of NAnt are these files written for? Are the developers aware that the build files don't work? Or have I misunderstood something? Then I found the solution file, and successfully built Log4Net in VS.NET 2003 (after an automatic conversion of the solution and project files). I understand that Log4Net was tested in Framework 1.1, but was it built with VS.NET 2003? Should I expect problems? Also, if I understand correctly, having transformed the project files will prevent me from following the development on CVS (at least inasmuch as project-file changes are involved). Is there a known solution to this problem? Thanks in advance, Shai. ** The contents of this email and any attachments are confidential. They are intended for the named recipient(s) only. If you have received this email in error please notify the system manager or the sender immediately and do not disclose the contents to anyone or make copies. ** TASE scanned this email for viruses, vandals and malicious content. ** **
Re: Calling target depending on current .NET version
Olivier,
You can either :
1. specify the .NET 1.0 requirement on the target itself, by using the "if"
or "unless" attributes
2. use an task to conditionally execute a set of tasks/targets
3.use an "if" or "unless" attribute on the task itself to
conditionally execute the target
The first solution is preferred when the target should ever only be executed
when targeting the .NET Framework 1.0.
If you need any further assistance, please post a message to the NAnt users
mailing list (nant-users@lists.sourceforge.net).
Hope this helps,
Gert
- Original Message -
From: "Nicko Cadell" <[EMAIL PROTECTED]>
To: "Log4NET User"
Sent: Monday, October 18, 2004 3:17 PM
Subject: RE: Calling target depending on current .NET version
Oliver,
This is probably a question best directed to the NAnt user mailing list!
Looking at the log4net NAnt build you can see that you can do:
You will need a recent nightly build of NAnt 0.85 to do this.
Nicko
> -Original Message-
> From: Oliver Wulff [mailto:[EMAIL PROTECTED]
> Sent: 15 October 2004 09:18
> To: log4net-user@logging.apache.org
> Subject: Calling target depending on current .NET version
>
>
>
>
>
> Hi
>
> I'm using the same build xml to build a project for .NET
> Framework 1.0 and 1.1.
>
> I control the .NET version with the following properties:
>
> value="net-${version.net.framework}"/>
>
> Now, I need to call a target only when .NET version 1.0 is
> active. Does there exists a property which is only set in this case?
>
> Thanks for help
> Oliver
>
>
>
>
>
>
>
> *** BITTE BEACHTEN *** Diese
> Nachricht (wie auch allfällige Anhänge dazu) beinhaltet
> möglicherweise vertrauliche oder gesetzlich geschützte Daten
> oder Informationen. Zum Empfang derselben ist (sind)
> ausschliesslich die
> genannte(n) Person(en) bestimmt. Falls Sie diese Nachricht
> irrtümlicherweise erreicht hat, sind Sie höflich gebeten,
> diese unter Ausschluss jeder Reproduktion zu zerstören und
> die absendende Person umgehend zu benachrichtigen. Vielen
> Dank für Ihre Hilfe.
>
>
Re: SourceSafe.Interop, or one of its dependencies, was not found
Rodney, Please post this message to the Nant users list. Gert - Original Message - From: "Woodruff, Rodney" <[EMAIL PROTECTED]> To: "Log4NET User" Sent: Tuesday, October 19, 2004 5:19 PM Subject: SourceSafe.Interop, or one of its dependencies, was not found Hello All, I am trying to use the vss task from nant contrib. My target is below: I am using the 'loadtasks' task to load tasks from the Nant.Contrib.Tasks.dll and the SourceSafe.Interop.dll. I didn't want to send a message to the developer list just yet because I figured that this is has already been solved. I searched the list archive, google and google groups but could not find a solution to this problem. Here is the output when I try to run this task: C:\Projects\ZDSURVEY\framework>nant vss NAnt 0.84 (Build 0.84.1455.0; net-1.0.win32; release; 12/26/2003) Copyright (C) 2001-2003 Gerry Shaw http://nant.sourceforge.net Buildfile: file:///C:/Projects/ZDSURVEY/framework/framework.build Target(s) specified: vss [loadtasks] Loading tasks from assembly C:\bin\nantcontrib.Tasks-0.84\bin\NAnt.Contrib.Tasks.dll. [loadtasks] Loading tasks from assembly C:\bin\nantcontrib.Tasks-0.84\bin\SourceSafe.Interop.dll. vss: BUILD FAILED INTERNAL ERROR System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.IO.FileNo tFoundException: File or assembly name SourceSafe.Interop, or one of its dependencies, was not found. File name: "SourceSafe.Interop" at NAnt.Contrib.Tasks.SourceSafe.BaseTask..ctor() at NAnt.Contrib.Tasks.SourceSafe.GetTask..ctor() === Pre-bind state information === LOG: DisplayName = SourceSafe.Interop, Version=5.1.0.0, Culture=neutral, PublicKeyToken=null (Fully-specified) LOG: Appbase = C:\bin\nant-0.84\bin\ LOG: Initial PrivatePath = NULL Calling assembly : NAnt.Contrib.Tasks, Version=0.84.1455.0, Culture=neutral, PublicKeyToken=null. === LOG: Policy not being applied to reference at this time (private, custom, partial, or location-based assembly bind). LOG: Post-policy reference: SourceSafe.Interop, Version=5.1.0.0, Culture=neutral, PublicKeyToken=null LOG: Attempting download of new URL file:///C:/bin/nant-0.84/bin/SourceSafe.Interop.DLL. LOG: Attempting download of new URL file:///C:/bin/nant-0.84/bin/SourceSafe.Interop/SourceSafe.Interop.DLL. LOG: Attempting download of new URL file:///C:/bin/nant-0.84/bin/SourceSafe.Interop.EXE. LOG: Attempting download of new URL file:///C:/bin/nant-0.84/bin/SourceSafe.Interop/SourceSafe.Interop.EXE. --- End of inner exception stack trace --- at System.RuntimeType.CreateInstanceImpl(Boolean publicOnly) at System.Activator.CreateInstance(Type type, Boolean nonPublic) at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Obj ect[] activationAttributes) at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture , Object[] activationAttributes) at System.Reflection.Assembly.CreateInstance(String typeName, Boolean ignoreCase, BindingFlags bindingAttr, Binder binder , Object[] args, CultureInfo culture, Object[] activationAttributes) at NAnt.Core.TaskBuilder.CreateTask() at NAnt.Core.TypeFactory.CreateTask(XmlNode taskNode, Project proj) at NAnt.Core.Target.Execute() at NAnt.Core.Project.Execute(String targetName, Boolean forceDependencies) at NAnt.Core.Project.Execute() at NAnt.Core.Project.Run() Please send bug report to [EMAIL PROTECTED] Total time: 0.1 seconds. Thanks in advance for your help. -- Rodney
RE: basic question on building log4net
> -Original Message- > From: Steve Burkett [mailto:[EMAIL PROTECTED] > Sent: vrijdag 22 oktober 2004 0:24 > To: Log4NET User > Subject: basic question on building log4net > > Hello, > > I have a basic question on building log4net. I'm running Win2k, SP2, > .Net 1.1, VS .Net 2003. > > I build log4net via: > nant compile-net-1.1 /f:log4net.build > > The stdout says it's doing .Net 1.1 but log4net.dll is built to (1.0 > directory): > > log4net\log4net-1.2.0-beta8\bin\net\1.0\debug > log4net\log4net-1.2.0-beta8\bin\net\1.0\release > > (1) How do I get it to build to 1.1 directory? It should indeed work by using the "compile-net-1.1" target, and it is indeed working just fine here (using latest cvs). What version of Nant are you using ? > (2) how do I build just release, or just debug? IF you build from cvs, then the "compile-net-1.1" target will, by default, build only the debug config. If you want it to build the release config you need to set the project.build.config property : nant -D:project.build.config=release /f:log4net.build compile-net-1.1 Gert
RE: Having trouble signing log4net.dll
Roy, To create a release build of log4net for a specific CLR, you can use the following command line: NAnt.exe -f:log4net.build -D:project.build.config=release compile- For example: to build log4net in a release configuration for .NET 1.1, you'd use NAnt.exe -f:log4net.build -D:project.build.config=release compile-net-1.1 Hope this helps, Gert > -Original Message- > From: Pardee, Roy [mailto:[EMAIL PROTECTED] > Sent: zaterdag 5 maart 2005 1:42 > To: log4net-user@logging.apache.org > Subject: Having trouble signing log4net.dll > > Hey All, > > I'd like to sign the log4net.dll assembly (version 1.2.0-beta8) w/a > locally generated .snk, and am having trouble. I'm not NANT-literate, > which is probably the issue. > > Here's what I've tried: > > Copied my snk file to the log4net basedir (in my case, > c:\DeleteMe\log4net-1.2.0-beta8) and renamed it to log4net.snk. > > Opened c:\DeleteMe\log4net-1.2.0-beta8\src\AssemblyInfo.cs, > and changed > the last few lines to this: > >#if STRONG >[assembly: AssemblyDelaySign(false)] >// [assembly: AssemblyKeyFile(@"..\..\..\log4net.snk")] >[assembly: > AssemblyKeyFile(@"c:\DeleteMe\log4net-1.2.0-beta8\log4net.snk")] >#endif > > Opened a command prompt & ran the BUILD.cmd batch file. > > (BTW--it looks like this builds everything everything--how would I get > this batch file to only build the .net v1.1 version w/the strong > naming?) > > I get a 'BUILD SUCCEEDED' (full output is appended below). The file > C:\DeleteMe\log4net-1.2.0-beta8\bin\net\1.1\debug\log4net.dll has the > expected fresh timestamp. > > But when I navigate over to > C:\DeleteMe\log4net-1.2.0-beta8\bin\net\1.1\debug and say: > >sn -v log4net.dll > > to verify the strong name I get: > >log4net.dll does not represent a strongly named assembly > > And further, when I try to build my project (having refreshed the > reference to log4net.dll) I get this build error: > > Unable to emit assembly: Referenced assembly 'log4net' does not have a > strong name > > Can anybody throw me a clue? > > Thanks! > > -Roy > > P.S. Here is the full text of the BUILD.cmd run, in case it's useful. > > C:\DeleteMe\log4net-1.2.0-beta8>build > LOG4NET_DIR is C:\DeleteMe\log4net-1.2.0-beta8 > BUILD_FILE is C:\DeleteMe\log4net-1.2.0-beta8\log4net.build > Buildfile: file:///C:/DeleteMe/log4net-1.2.0-beta8/log4net.build > > check-current-build-config: > > set-build-configuration: > > set-debug-build-configuration: > > set-build-configuration-flags: > > set-runtime-configuration: > > check-bin-dir: > > check-doc-dir: > > check-sdkdoc-dir: > > check-sdkdoc-debug: > > check-build-debug: > > check-build-defines: > > set-net-1.0-runtime-configuration: > > set-net-1.0-runtime-configuration: > > compile-all: > [echo] Compiling all build configurations for all runtime > configurations. > > set-debug-build-configuration: > > set-build-configuration-flags: > > compile-build: > [echo] Compiling all runtime configurations for the debug build > configurati > on. > > set-netcf-1.0-runtime-configuration: > > set-netcf-1.0-runtime-configuration: > > check-log4net-basedir: > > compile-netcf-1.0: > > check-current-bin-dir: > > clean-current-bin-dir: > [echo] Cleaning the bin/netcf/1.0/debug binaries directory. >[delete] Deleting directory > C:\DeleteMe\log4net-1.2.0-beta8\bin\netcf\1.0\deb > ug. > [mkdir] Creating directory > C:\DeleteMe\log4net-1.2.0-beta8\bin\netcf\1.0\deb > ug > [csc] Compiling 114 files to > C:\DeleteMe\log4net-1.2.0-beta8\bin\netcf\1.0 > \debug\log4net.dll > > set-net-1.0-runtime-configuration: > > set-net-1.0-runtime-configuration: > > compile-net-1.0: > > clean-current-bin-dir: > [echo] Cleaning the bin/net/1.0/debug binaries directory. >[delete] Deleting directory > C:\DeleteMe\log4net-1.2.0-beta8\bin\net\1.0\debug > . > [mkdir] Creating directory > C:\DeleteMe\log4net-1.2.0-beta8\bin\net\1.0\debug > > [csc] Compiling 127 files to > C:\DeleteMe\log4net-1.2.0-beta8\bin\net\1.0\d > ebug\log4net.dll > > set-net-1.1-runtime-configuration: > > set-net-1.1-runtime-configuration: > > compile-net-1.1: > > clean-current-bin-dir: > [echo] Cleaning the bin/net/1.1/debug binaries directory. >[delete] Deleting directory > C:\DeleteMe\log4net-1.2.0-beta8\bin\net\1.1\debug > . > [mkdir] Creating directory > C:\DeleteMe\log4net-1.2.0-beta8\bin\net\1.1\debug > > [csc] Compiling 127 files to > C:\DeleteMe\log4net-1.2.0-beta8\bin\net\1.1\d > ebug\log4net.dll > [echo] Mono 1.0 is not available. Build skipped. > [echo] SSCLI 1.0 is not available. Build skipped. > > set-release-build-configuration: > > set-build-configuration-flags: > > compile-build: > [echo] Compiling all runtime configurations for the release build > configura > tion. > > set-netcf-1.0-runtime-configuration: > > compile-netcf-1.0: > > clean-current-bin-dir: > [echo] Cleaning the bin/netcf/1.
RE: .net 1.0 and building examples
> -Original Message- > From: Castro, Yvette [mailto:[EMAIL PROTECTED] > Sent: donderdag 14 april 2005 21:01 > To: Log4NET User > Subject: .net 1.0 and building examples > > I have 1.1 installed on my computer. I'm building via nant, but the > builds will not complete since the default is 1.0. > > I got around it when running the initial build by altering the > nant.exe.config file to force it to point to 1.1, but I've been > encountering problems with other builds. You can either - install a newer version of NAnt (0.85), which will default to the runtime that is used to run NAnt or - specify the default framework on the command line using the -defaultframework option, eg. NAnt.exe -defaultframework:net-1.1 Hope this helps, Gert
RE: Problem to compile log4net 1.2.9
Julien, The NAnt build files for log4net do not yet support targeting the Mono 2.0 profile. I'll look into fixing this in svn (so it should work fine in the next release). Could it be that you're using an old version of Mono ? I think you're running into an issue that was fixed a while ago (in Mono). BTW, what version of NAnt are you using ? Gert > -Original Message- > From: Julien Sobrier [mailto:[EMAIL PROTECTED] > Sent: zaterdag 5 november 2005 6:40 > To: log4net-user@logging.apache.org > Subject: Problem to compile log4net 1.2.9 > > Hello, > I have to compile log4net 1.2.9 to make him use the 2.0.0.0 version of > System.Data. I use NAnt and lib/mono/2.0/gmcs.exe and Mono > 1.1.9.2/Linux > > I got the following error: > > compile-mono-1.0: > > [csc] Compiling 201 files to > '.../log4net/bin/mono/1.0/debug/log4net.dll'." > [csc] error CS0535: > `log4net.Config.Log4NetConfigurationSectionHandler' does not implement > interface member > `System.Configuration.IConfigurationSectionHandler.Create(object, > object, System.Xml.XmlNode)' > [csc] /usr/lib/mono/1.0/System.dll: > `System.Configuration.IConfigurationSectionHandler.Create(object, > object, System.Xml.XmlNode)' (name of symbol related to previous error > [csc] Compilation failed: 1 error(s), 0 warnings > > BUILD FAILED - 0 non-fatal error(s), 2 warning(s) > > Any idea to fix this? > > > Thank you > Julien >
Re: .net 2.0
John, I'm looking into that, but I can't promise an exact date on when it'll be compiling on .NET 2.0. Gert - Original Message - From: "John Cole" <[EMAIL PROTECTED]> To: "'Log4NET User'" Sent: Monday, November 14, 2005 5:02 PM Subject: .net 2.0 > I pulled the log4net source out of cvs and tried to compile it with .net > 2.0, but ran into a lot of errors. Are there instructions on how to get it > to compile, or better yet, a modified makefile/buildfile to get it working? > > Thanks, > > John Cole > > - > This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. >
