New features in NLog - please read and make comments

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

New features in NLog - please read and make comments

Jarek Kowalski
Administrator
Hi!

There are some new features in NLog, that have been added post v0.95. They
are all planned to go to v1.0 (to be expected soon). Note that the bugfixes
are not listed here, new features only.

The list is quite large, and because some new functions required changes to
be made to critical pieces of NLog, they require a lot of real-world
testing.

I'm considering the release of NLog v0.99 followed by 1.0 in a month or two
when things get stable. What do you think? (this can be also called NLog 1.0
RC1, if you like, as the API shouldn't change after this release and before
1.0)

As usual, the code can be grabbed from:
http://www.nlog-project.org/snapshots/

The documentation for the latest version is here:
http://www.nlog-project.org/snapshots/20060625/web/documentation.html

Here's the list, in no particular order. This is mostly a commented version
of the ChangeLog + some new explanation words made today.

1. Optimization to defer calling String.Format() until it's really needed.

It means that if you call a log method which contains parameter
placeholders, the String.Format() is not called until ${message} is actually
used. You can have filters and conditions that might prevent message from
being logged after it passes <rules> and this helps speed up things a lot.
Note that there are cases where you need to pre-calculate the
String.Format() because the parameters might do the logging themselves in
ToString(). Care has been taken about it, too.

2. Added InternalLogger.LogToConsoleError and their config file and
environment variable counterparts to send log output to Console.Error.

3. Added LayoutRenderer.IsAppDomainFixed() and an optimization to turn such
things into literals. So if you use "${basedir}/log.txt" this gets converted
into a literal which takes no time to recalculate.

4. Added LoggingConfiguration.GetConfiguredNamedTargets() API

5. BREAKING CHANGE - Completely restructured the way File target works.

The new structure is based on Streams instead of StreamWriters and enables
archiving (kind of similar to "rolling file appender" from log4net world,
but supporting multiple files at a time!)

Usage:

<target type="File" fileName="file.txt"
archiveFileName="archive/file.{#####}.txt" maxArchiveFiles="4"
archiveEvery="Day" archiveNumbering="Sequence|Rolling" />

This creates a new archive file in the archive directory every day.
Depending on archiveNumbering you get a different archive scheme.
Present-day log file is always "file.txt"

a) Sequence

Assuming you've just rolled onto the 101st file, you have:

archive/file.00096.txt
archive/file.00097.txt
archive/file.00098..txt
archive/file.00099.txt
archive/file.00100.txt

(00095 has just been deleted)

b) Rolling

The files are numbered in the opposite direction. The most recent is always
0

archive/file.00000.txt
archive/file.00001.txt
archive/file.00002.txt
archive/file.00003.txt
archive/file.00004.txt

Each time you pass the midnight, files are rolled:

day 0004 is deleted, 3 is moved to 4, 2 to 3, 1 to 2, 0 to 1 and file.txt is
moved to file.00000.txt

The good news it works with any fancy filenaming scheme you may invent. You
may use layout renderers in both file and archive names. The only
requirement is that archives for a single filename are kept in a single
directory.

<target type="File" fileName="file.${logger}.${level}.txt"
archiveName="archives/${level}/${logger}.logfile.{###}" />

Where you actually split one target into many files simultaneously being
written to.
The bad news is that archiving may slow file logging by as much as 30%, but
there are some tricks to overcome it.

6. BREAKING CHANGE - removed some properties which accepted strings. Now
replaced with enums for type safety.

7. Added caching to File target to optimize the number file open/close
operations.

The new options are called:

* openFileCacheSize - the number of files to keep open (note that you can
delete files even though they are kept open). By default this is 5 seconds.

* openFileCacheTimeout - maximum time to keep the file open (by default set
to 1 second). This causes NLog to close open log files every 1 second to let
other processes delete them.

8. Added an option for multiple processes to append to the same OPEN file n
a synchronized manner. Unixes get this for free, but Win32 requires you to
use mutexes to synchronize file access. This gives a nice performance boost.

9. Merged NLog.Win32.dll, NLog.DotNet.dll, NLog.Unix.dll and NLog.Mono.dll
into one assembly NLog.dll

10. Separate compilation of NLog for all supported frameworks. Starting with
NLog v1.0 I'll be publishing the following releases:

nlog-RELEASENAME-help.zip
nlog-RELEASENAME-mono-1.0.zip
nlog-RELEASENAME-mono-1.0-debug.zip
nlog-RELEASENAME-mono-2.0.zip
nlog-RELEASENAME-mono-2.0-debug.zip
nlog-RELEASENAME-net-1.0.zip
nlog-RELEASENAME-net-1.0-debug.zip
nlog-RELEASENAME-net-1.1.zip
nlog-RELEASENAME-net-1.1-debug.zip
nlog-RELEASENAME-net-2.0.zip
nlog-RELEASENAME-net-2.0-debug.zip
nlog-RELEASENAME-netcf-1.0.zip
nlog-RELEASENAME-netcf-1.0-debug.zip
nlog-RELEASENAME-netcf-2.0.zip
nlog-RELEASENAME-netcf-2.0-debug.zip
nlog-RELEASENAME-setup.exe
nlog-RELEASENAME-setup-debug.exe
nlog-RELEASENAME-src.zip

11. Added attributes which mark support for particular runtimes and OSes.
They are used for generating documentation and disabling particular
targets/layout renderers at runtime.

12. Added generation of NLog.xsd schema for Intellisense.

You get this installed by default, so Visual Studio gives you nice
configuration aid. You only need to add namespace declarations to <nlog>
tag:

    <nlog xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xmlns="http://www.nlog-project.org/schemas/NLog.xsd">
...
    </nlog>

and use "xsi:type" instead of "type" for specifying target type.

13. Added support for VC#Express and VBExpress to the installer.

14. Added VS2005 C# and VB.NET code snippet (nlogger) to quickly insert
logger creation statement

15. Added VS2005 item templates for NLog configuration. Updated the
installer. NLog now looks for "NLog.config" in addition to other config file
names.

16. Implemented AsyncWrapper for .NET CF using the Timer class

17. Refactored file watching - should speed up non-logging by 100%

18. Prepared ready-to-run example projects for VS2005 that describe most
targets.

19. Added WebService target supporting SOAP 1.1, SOAP 1.2, HTTP GET and HTTP
POST web service calls.

This is purely runtime and should talk to any web service method that
accepts a number of string parameters. Examples are here:

http://svn.nlog-project.org/repos/nlog/trunk/NLog/examples/targets/Configuration%20File/WebService/

20. Added deleteOldFileOnStartup to the File target

21. Added replaceFileContentsOnEachWrite to the File target

22. Added support for flags-type enumerations.

23. compilation, schema generation a and website building are supported on
Linux/Mono. All unit tests pass.

24. Added Layout.Escape() which escapes ${ with ${literal:text=${}

25. Added FileTarget.LineEnding

26. Added Logger.Log(LogEventInfo) overload

27. Added Logger.Log(Type,LogEventInfo) overload - useful for wrapping
NLog.Logger

28. Added LoggerReconfiguredDelegate and Logger.LoggerReconfigured events

29. Added <include file="..." ignoreErrors="true|false" />

30. Fixed autoReload to keep monitoring the file if the reloaded file has an
error

31. Implemented <targets><default-wrapper /> </targets> that wraps all
targets in <targets> section with the specified wrapper.

The usage is:

<targets>
    <default-wrapper xsi:type="AsyncWrapper" />
    <target name="f" type="File" ... />
    <target name="n" type="Network" ... />
</targets>

This creates "f" which is actually a AsyncWrapper(File) and "n" which is
AsyncWrapper(Network). Note that the original target names are renamed as
"f_wrapped" and "n_wrapped" respectively.

32. Added CSVFile target which does proper CSV formatting (multi-line and
special character quoting). This enables you to analyze your log files in MS
Excel.

So we have a nice number of (1<<6) new features, don't you think?

--
Jarek
http://blog.jkowalski.net/ 


Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Nlog-list mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nlog-list
NLog Blog
Reply | Threaded
Open this post in threaded view
|

Re: New features in NLog - please read and make comments

Jarek Kowalski
Administrator
>
> So we have a nice number of (1<<6) new features, don't you think?

Should be (1<<5) of course.

Jarek

Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Nlog-list mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nlog-list
NLog Blog
Reply | Threaded
Open this post in threaded view
|

Re: New features in NLog - please read and make comments

Andrew Doherty
In reply to this post by Jarek Kowalski
Nice list.

The integrated Framework 2.0 support is particularly useful to us as
we've been home brewing a native 2.0 version of 0.95 up until now. The
deployment changes in 9 and 10 are also very practical for us, but we
also like the file target option changes as that replicates some
functionality we lost moving away from our own (admittedly primitive)
logging framework.

I think that if you're not planning on having API changes between now
and 1.0, then you'd be best off moving to either 1.0 RC1 or a 1.0 beta
revision depending on how much real world testing you feel it needs
still.

Thanks, Andy.

-----Original Message-----
From: [hidden email]
[mailto:[hidden email]] On Behalf Of
[hidden email]
Sent: 25 June 2006 20:02
To: [hidden email]
Subject: Nlog-list Digest, Vol 1, Issue 139

Send Nlog-list mailing list submissions to
        [hidden email]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.sourceforge.net/lists/listinfo/nlog-list
or, via email, send a message with subject or body 'help' to
        [hidden email]

You can reach the person managing the list at
        [hidden email]

When replying, please edit your Subject line so it is more specific than
"Re: Contents of Nlog-list digest..."


Today's Topics:

   1. New features in NLog - please read and make comments
      (Jaroslaw Kowalski)
   2. Re: New features in NLog - please read and make comments
      (Jaroslaw Kowalski)


----------------------------------------------------------------------

Message: 1
Date: Sun, 25 Jun 2006 17:32:05 +0200
From: "Jaroslaw Kowalski" <[hidden email]>
Subject: [Nlog-list] New features in NLog - please read and make
        comments
To: <[hidden email]>
Message-ID: <002601c6986c$83b86eb0$2200a8c0@jaakntb>
Content-Type: text/plain; format=flowed; charset="iso-8859-2";
        reply-type=original

Hi!

There are some new features in NLog, that have been added post v0.95.
They are all planned to go to v1.0 (to be expected soon). Note that the
bugfixes are not listed here, new features only.

The list is quite large, and because some new functions required changes
to be made to critical pieces of NLog, they require a lot of real-world
testing.

I'm considering the release of NLog v0.99 followed by 1.0 in a month or
two when things get stable. What do you think? (this can be also called
NLog 1.0 RC1, if you like, as the API shouldn't change after this
release and before
1.0)

As usual, the code can be grabbed from:
http://www.nlog-project.org/snapshots/

The documentation for the latest version is here:
http://www.nlog-project.org/snapshots/20060625/web/documentation.html

Here's the list, in no particular order. This is mostly a commented
version of the ChangeLog + some new explanation words made today.

1. Optimization to defer calling String.Format() until it's really
needed.

It means that if you call a log method which contains parameter
placeholders, the String.Format() is not called until ${message} is
actually used. You can have filters and conditions that might prevent
message from being logged after it passes <rules> and this helps speed
up things a lot.
Note that there are cases where you need to pre-calculate the
String.Format() because the parameters might do the logging themselves
in ToString(). Care has been taken about it, too.

2. Added InternalLogger.LogToConsoleError and their config file and
environment variable counterparts to send log output to Console.Error.

3. Added LayoutRenderer.IsAppDomainFixed() and an optimization to turn
such things into literals. So if you use "${basedir}/log.txt" this gets
converted into a literal which takes no time to recalculate.

4. Added LoggingConfiguration.GetConfiguredNamedTargets() API

5. BREAKING CHANGE - Completely restructured the way File target works.

The new structure is based on Streams instead of StreamWriters and
enables archiving (kind of similar to "rolling file appender" from
log4net world, but supporting multiple files at a time!)

Usage:

<target type="File" fileName="file.txt"
archiveFileName="archive/file.{#####}.txt" maxArchiveFiles="4"
archiveEvery="Day" archiveNumbering="Sequence|Rolling" />

This creates a new archive file in the archive directory every day.
Depending on archiveNumbering you get a different archive scheme.
Present-day log file is always "file.txt"

a) Sequence

Assuming you've just rolled onto the 101st file, you have:

archive/file.00096.txt
archive/file.00097.txt
archive/file.00098..txt
archive/file.00099.txt
archive/file.00100.txt

(00095 has just been deleted)

b) Rolling

The files are numbered in the opposite direction. The most recent is
always 0

archive/file.00000.txt
archive/file.00001.txt
archive/file.00002.txt
archive/file.00003.txt
archive/file.00004.txt

Each time you pass the midnight, files are rolled:

day 0004 is deleted, 3 is moved to 4, 2 to 3, 1 to 2, 0 to 1 and
file.txt is moved to file.00000.txt

The good news it works with any fancy filenaming scheme you may invent.
You may use layout renderers in both file and archive names. The only
requirement is that archives for a single filename are kept in a single
directory.

<target type="File" fileName="file.${logger}.${level}.txt"
archiveName="archives/${level}/${logger}.logfile.{###}" />

Where you actually split one target into many files simultaneously being
written to.
The bad news is that archiving may slow file logging by as much as 30%,
but there are some tricks to overcome it.

6. BREAKING CHANGE - removed some properties which accepted strings. Now
replaced with enums for type safety.

7. Added caching to File target to optimize the number file open/close
operations.

The new options are called:

* openFileCacheSize - the number of files to keep open (note that you
can delete files even though they are kept open). By default this is 5
seconds.

* openFileCacheTimeout - maximum time to keep the file open (by default
set to 1 second). This causes NLog to close open log files every 1
second to let other processes delete them.

8. Added an option for multiple processes to append to the same OPEN
file n a synchronized manner. Unixes get this for free, but Win32
requires you to use mutexes to synchronize file access. This gives a
nice performance boost.

9. Merged NLog.Win32.dll, NLog.DotNet.dll, NLog.Unix.dll and
NLog.Mono.dll into one assembly NLog.dll

10. Separate compilation of NLog for all supported frameworks. Starting
with NLog v1.0 I'll be publishing the following releases:

nlog-RELEASENAME-help.zip
nlog-RELEASENAME-mono-1.0.zip
nlog-RELEASENAME-mono-1.0-debug.zip
nlog-RELEASENAME-mono-2.0.zip
nlog-RELEASENAME-mono-2.0-debug.zip
nlog-RELEASENAME-net-1.0.zip
nlog-RELEASENAME-net-1.0-debug.zip
nlog-RELEASENAME-net-1.1.zip
nlog-RELEASENAME-net-1.1-debug.zip
nlog-RELEASENAME-net-2.0.zip
nlog-RELEASENAME-net-2.0-debug.zip
nlog-RELEASENAME-netcf-1.0.zip
nlog-RELEASENAME-netcf-1.0-debug.zip
nlog-RELEASENAME-netcf-2.0.zip
nlog-RELEASENAME-netcf-2.0-debug.zip
nlog-RELEASENAME-setup.exe
nlog-RELEASENAME-setup-debug.exe
nlog-RELEASENAME-src.zip

11. Added attributes which mark support for particular runtimes and
OSes.
They are used for generating documentation and disabling particular
targets/layout renderers at runtime.

12. Added generation of NLog.xsd schema for Intellisense.

You get this installed by default, so Visual Studio gives you nice
configuration aid. You only need to add namespace declarations to <nlog>
tag:

    <nlog xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xmlns="http://www.nlog-project.org/schemas/NLog.xsd">
...
    </nlog>

and use "xsi:type" instead of "type" for specifying target type.

13. Added support for VC#Express and VBExpress to the installer.

14. Added VS2005 C# and VB.NET code snippet (nlogger) to quickly insert
logger creation statement

15. Added VS2005 item templates for NLog configuration. Updated the
installer. NLog now looks for "NLog.config" in addition to other config
file names.

16. Implemented AsyncWrapper for .NET CF using the Timer class

17. Refactored file watching - should speed up non-logging by 100%

18. Prepared ready-to-run example projects for VS2005 that describe most
targets.

19. Added WebService target supporting SOAP 1.1, SOAP 1.2, HTTP GET and
HTTP POST web service calls.

This is purely runtime and should talk to any web service method that
accepts a number of string parameters. Examples are here:

http://svn.nlog-project.org/repos/nlog/trunk/NLog/examples/targets/Confi
guration%20File/WebService/

20. Added deleteOldFileOnStartup to the File target

21. Added replaceFileContentsOnEachWrite to the File target

22. Added support for flags-type enumerations.

23. compilation, schema generation a and website building are supported
on Linux/Mono. All unit tests pass.

24. Added Layout.Escape() which escapes ${ with ${literal:text=${}

25. Added FileTarget.LineEnding

26. Added Logger.Log(LogEventInfo) overload

27. Added Logger.Log(Type,LogEventInfo) overload - useful for wrapping
NLog.Logger

28. Added LoggerReconfiguredDelegate and Logger.LoggerReconfigured
events

29. Added <include file="..." ignoreErrors="true|false" />

30. Fixed autoReload to keep monitoring the file if the reloaded file
has an error

31. Implemented <targets><default-wrapper /> </targets> that wraps all
targets in <targets> section with the specified wrapper.

The usage is:

<targets>
    <default-wrapper xsi:type="AsyncWrapper" />
    <target name="f" type="File" ... />
    <target name="n" type="Network" ... /> </targets>

This creates "f" which is actually a AsyncWrapper(File) and "n" which is
AsyncWrapper(Network). Note that the original target names are renamed
as "f_wrapped" and "n_wrapped" respectively.

32. Added CSVFile target which does proper CSV formatting (multi-line
and special character quoting). This enables you to analyze your log
files in MS Excel.

So we have a nice number of (1<<6) new features, don't you think?

--
Jarek
http://blog.jkowalski.net/ 




------------------------------

Message: 2
Date: Sun, 25 Jun 2006 18:25:03 +0200
From: "Jaroslaw Kowalski" <[hidden email]>
Subject: Re: [Nlog-list] New features in NLog - please read and make
        comments
To: "Jaroslaw Kowalski" <[hidden email]>,
        <[hidden email]>
Message-ID: <003c01c69873$e9ff1ff0$2200a8c0@jaakntb>
Content-Type: text/plain; format=flowed; charset="ISO-8859-1";
        reply-type=original

>
> So we have a nice number of (1<<6) new features, don't you think?

Should be (1<<5) of course.

Jarek



------------------------------

Using Tomcat but need to do more? Need to support web services,
security?
Get stuff done quickly with pre-integrated technology to make your job
easier Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

------------------------------

_______________________________________________
Nlog-list mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nlog-list


End of Nlog-list Digest, Vol 1, Issue 139
*****************************************

________________________________________________________________________
This e-mail has been scanned for all viruses by MessageLabs.

________________________________________________________________________
This email is for the intended addressee only. If you have received this in error, you must not copy, retain, disseminate or otherwise make use of it. Please notify the sender by return email. The views of the author may not necessarily constitute the views of N4 Solutions Limited. Unless previously agreed in writing nothing in this email shall bind N4 Solutions Limited in any contract or obligation.
________________________________________________________________________
This e-mail has been scanned for all viruses by MessageLabs.

Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Nlog-list mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nlog-list
Reply | Threaded
Open this post in threaded view
|

Intellisense don't work perfectly with VS.NET 2003

clab
In reply to this post by Jarek Kowalski
Hi,
I use VS.NET 2003 and I tried to use Intellisense in Nlog config file.
Your setup install (correctly) NLog.xsd into C:\Program Files\Microsoft Visual Studio .NET 2003\Common7\Packages\schemas\xml, but after I write any config keyword (target, rules... etc.) intellisense suggest only "name" attribute and all keyword has underlined zig-zag (allow me italian neologism please :o).

I tried with VSNET 2005 and it work correctly, but I can't pass to 2.0 framework now.

Below my Nlog.config file content.

Any suggestion ?

Thank's for your job, Jarek

Claudio

-------------------
<?xml version="1.0" encoding="utf-8" ?>
<nlog autoReload="true" xmlns="http://www.nlog-project.org/schemas/NLog.xsd" 
                        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
        <targets>
                <target xsi:type="File" name="file" layout="${longdate} ${processtime} ${threadid} ${logger} ${level:uppercase=true} ${message}"
                        filename="C:\\LOG\XNetCommService_${date:format=yyyy-MM-dd}.txt" keepfileopen="false"
                        encoding="iso-8859-2" />
                <target name="exceptionfile" xsi:type="File" layout="${longdate} ${threadid} ${logger} EXCEPTION ${message} ${exception:format=type,method,sourceFile,sourceLineNumber,stacktrace}"
                        filename="C:\\LOG\XNetCommService_${date:format=yyyy-MM-dd}.txt" keepfileopen="false"
                        encoding="iso-8859-2" />
                <target name="console" xsi:type="ColoredConsole" layout="${processtime} ${threadid} ${logger} ${level:uppercase=true} ${message}" />
                <target name="debugger" xsi:type="Debugger" layout="${processtime} ${threadid} ${logger} ${level:uppercase=true} ${message}" />
                <target name="exceptionlog" xsi:type="EventLog" layout="${longdate} ${threadid} EXCEPTION ${message} ${exception:format=type,method,sourceFile,sourceLineNumber,stacktrace}"
                        source="XNet Com Service" log="XNet Com Service" />
                <target name="eventlog" xsi:type="EventLog" layout="${longdate} ${threadid} ${logger} ${level:uppercase=true} ${newline} ${message}"
                        source="XNet Com Service" log="XNet Com Service" />
        </targets>
        <rules>
                <logger name="*" minlevel="Trace" writeTo="console,debugger" />
                <logger name="ExceptionLogger" writeTo="exceptionlog,exceptionfile" final="true" />
                <logger name="*" minlevel="Debug" writeTo="file" />
                <logger name="*" minlevel="Info" writeTo="eventlog" />
        </rules>
</nlog>
Reply | Threaded
Open this post in threaded view
|

Re: Intellisense don't work perfectly with VS.NET 2003

Jarek Kowalski
Administrator

Earlier versions of VS had much weaker support for XSD-based Intellisense
and Visual Studio 2005 made a great progress here, so I'm afraid there's
nothing that can be done for a moment other than waiting for MS to release a
Service Pack for VS.NET 2003 to correct this behaviour.

Perhaps filing a bug report is a good idea. Microsoft has a feedback page
available at:
http://lab.msdn.microsoft.com/

You may also try other XML editors (XML Spy for example) if it's an option,
or use Visual C#/VB.NET Express Edition 2005 which is free and works very
well.

Did you know that there's "Open With" option available when you right-click
on a file in VS.NET Solution Explorer? You can click "Add", enter this path:

"C:\Program Files\Microsoft Visual Studio 8\Common7\IDE\devenv.exe"

end enjoy Visual Studio 2005 launching whenever you open your config file.
Not sure if it helps, though.

Jarek

----- Original Message -----
From: "clab" <[hidden email]>
To: <[hidden email]>
Sent: Friday, June 30, 2006 2:26 PM
Subject: [Nlog-list] Intellisense don't work perfectly with VS.NET 2003


>
> Hi,
> I use VS.NET 2003 and I tried to use Intellisense in Nlog config file.
> Your setup install (correctly) NLog.xsd into C:\Program Files\Microsoft
> Visual Studio .NET 2003\Common7\Packages\schemas\xml, but after I write
> any
> config keyword (target, rules... etc.) intellisense suggest only "name"
> attribute and all keyword has underlined zig-zag (allow me italian
> neologism
> please :o).
>
> I tried with VSNET 2005 and it work correctly, but I can't pass to 2.0
> framework now.
>
> Below my Nlog.config file content.
>
> Any suggestion ?
>
> Thank's for your job, Jarek
>
> Claudio
>
> -------------------
> <?xml version="1.0" encoding="utf-8" ?>
> <nlog autoReload="true"
> xmlns="http://www.nlog-project.org/schemas/NLog.xsd"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
> <targets>
> <target xsi:type="File" name="file" layout="${longdate} ${processtime}
> ${threadid} ${logger} ${level:uppercase=true} ${message}"
> filename="C:\\LOG\XNetCommService_${date:format=yyyy-MM-dd}.txt"
> keepfileopen="false"
> encoding="iso-8859-2" />
> <target name="exceptionfile" xsi:type="File" layout="${longdate}
> ${threadid} ${logger} EXCEPTION ${message}
> ${exception:format=type,method,sourceFile,sourceLineNumber,stacktrace}"
> filename="C:\\LOG\XNetCommService_${date:format=yyyy-MM-dd}.txt"
> keepfileopen="false"
> encoding="iso-8859-2" />
> <target name="console" xsi:type="ColoredConsole" layout="${processtime}
> ${threadid} ${logger} ${level:uppercase=true} ${message}" />
> <target name="debugger" xsi:type="Debugger" layout="${processtime}
> ${threadid} ${logger} ${level:uppercase=true} ${message}" />
> <target name="exceptionlog" xsi:type="EventLog" layout="${longdate}
> ${threadid} EXCEPTION ${message}
> ${exception:format=type,method,sourceFile,sourceLineNumber,stacktrace}"
> source="XNet Com Service" log="XNet Com Service" />
> <target name="eventlog" xsi:type="EventLog" layout="${longdate}
> ${threadid} ${logger} ${level:uppercase=true} ${newline} ${message}"
> source="XNet Com Service" log="XNet Com Service" />
> </targets>
> <rules>
> <logger name="*" minlevel="Trace" writeTo="console,debugger" />
> <logger name="ExceptionLogger" writeTo="exceptionlog,exceptionfile"
> final="true" />
> <logger name="*" minlevel="Debug" writeTo="file" />
> <logger name="*" minlevel="Info" writeTo="eventlog" />
> </rules>
> </nlog>
>
> --
> View this message in context:
> http://www.nabble.com/New-features-in-NLog---please-read-and-make-comments-tf1844701s6167.html#a5119528
> Sent from the NLog-list forum at Nabble.com.
>
>
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
> easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Nlog-list mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/nlog-list
>


Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Nlog-list mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nlog-list
NLog Blog