-
-
-
- ${aspnet-application:variable=myvariable} - produces "123"
- ${aspnet-application:variable=anothervariable} - produces "01/01/2006 00:00:00"
- ${aspnet-application:variable=anothervariable:culture=pl-PL} - produces "2006-01-01 00:00:00"
- ${aspnet-application:variable=myvariable:padding=5} - produces " 123"
- ${aspnet-application:variable=myvariable:padding=-5} - produces "123 "
- ${aspnet-application:variable=stringvariable:upperCase=true} - produces "AAA BBB"
-
-
- ${aspnet-request:item=v}
- ${aspnet-request:querystring=v}
- ${aspnet-request:form=v}
- ${aspnet-request:cookie=v}
- ${aspnet-request:serverVariable=v}
-
-
-
-
-
- ${aspnet-session:variable=myvariable} - produces "123"
- ${aspnet-session:variable=anothervariable} - produces "01/01/2006 00:00:00"
- ${aspnet-session:variable=anothervariable:culture=pl-PL} - produces "2006-01-01 00:00:00"
- ${aspnet-session:variable=myvariable:padding=5} - produces " 123"
- ${aspnet-session:variable=myvariable:padding=-5} - produces "123 "
- ${aspnet-session:variable=stringvariable:upperCase=true} - produces "AAA BBB"
-
- - To set up the target in the configuration file, - use the following syntax: -
-- You can use a single target to write to multiple queues (similar to writing to multiple files with the File target). -
-- The above examples assume just one target and a single rule. - More configuration options are described here. -
-- To set up the log target programmatically use code like this: -
-${longdate}|${level:uppercase=true}|${logger}|${message}
- - Typically this target is used in cooperation with PostFilteringTargetWrapper - to provide verbose logging for failing requests and normal or no logging for - successful requests. We need to make the decision of the final filtering rule - to apply after all logs for a page have been generated. -
-- To use this target, you need to add an entry in the httpModules section of - web.config: -
-
-
-
-
-
-
-
-
- ]]>
-
- To set up the ASP.NET Buffering target wrapper configuration file, put
- the following in
- This assumes just one target and a single rule. More configuration - options are described here. -
-
- To configure the target programmatically, put the following
- piece of code in your
- Fully working C# project can be found in the
-
-
- .
-
-
- .
-
-
- .
-
-
- .
-
-
- .
-
-
- .
-
-
- HKLM\Key\Full\Name -
- HKEY_LOCAL_MACHINE\Key\Full\Name -
- HKCU\Key\Full\Name -
- HKEY_CURRENT_USER\Key\Full\Name -
-
-
- ApplicationData - roaming application data for current user. -
- CommonApplicationData - application data for all users. -
- MyDocuments - My Documents -
- DesktopDirectory - Desktop directory -
- LocalApplicationData - non roaming application data -
- Personal - user profile directory -
- System - System directory -
${longdate}|${level:uppercase=true}|${logger}|${message}
- - To set up the target in the configuration file, - use the following syntax: -
-- This assumes just one target and a single rule. More configuration - options are described here. -
-- To set up the log target programmatically use code like this: -
-- NOTE: If your receiver application is ever likely to be off-line, don't use TCP protocol - or you'll get TCP timeouts and your application will crawl. - Either switch to UDP transport or use AsyncWrapper target - so that your application threads will not be blocked by the timing-out connection attempts. -
-- To set up the target in the configuration file, - use the following syntax: -
-- This assumes just one target and a single rule. More configuration - options are described here. -
-- To set up the log target programmatically use code like this: -
-- NOTE: If your receiver application is ever likely to be off-line, don't use TCP protocol - or you'll get TCP timeouts and your application will crawl. - Either switch to UDP transport or use AsyncWrapper target - so that your application threads will not be blocked by the timing-out connection attempts. -
-- To set up the target in the configuration file, - use the following syntax: -
-- This assumes just one target and a single rule. More configuration - options are described here. -
-- To set up the log target programmatically use code like this: -
-- To print the results, use any application that's able to receive messages over - TCP or UDP. NetCat is - a simple but very powerful command-line tool that can be used for that. This image - demonstrates the NetCat tool receiving log messages from Network target. -
-
- - NOTE: If your receiver application is ever likely to be off-line, don't use TCP protocol - or you'll get TCP timeouts and your application will crawl. - Either switch to UDP transport or use AsyncWrapper target - so that your application threads will not be blocked by the timing-out connection attempts. -
-- There are two specialized versions of the Network target: Chainsaw - and NLogViewer which write to instances of Chainsaw log4j viewer - or NLogViewer application respectively. -
-${longdate}|${level:uppercase=true}|${logger}|${message}
- -
-
- tcp://host:port - TCP (auto select IPv4/IPv6) -
- tcp4://host:port - force TCP/IPv4 -
- tcp6://host:port - force TCP/IPv6 -
- udp://host:port - UDP (auto select IPv4/IPv6, not supported on Silverlight) -
- udp4://host:port - force UDP/IPv4 (not supported on Silverlight) -
- udp6://host:port - force UDP/IPv6 (not supported on Silverlight) -
${longdate}|${level:uppercase=true}|${logger}|${message}
- ${longdate}|${level:uppercase=true}|${logger}|${message}
- ${longdate}|${level:uppercase=true}|${logger}|${message}
- | Condition | -Foreground Color | -Background Color | -
|---|---|---|
| level == LogLevel.Fatal | -Red | -NoChange | -
| level == LogLevel.Error | -Yellow | -NoChange | -
| level == LogLevel.Warn | -Magenta | -NoChange | -
| level == LogLevel.Info | -White | -NoChange | -
| level == LogLevel.Debug | -Gray | -NoChange | -
| level == LogLevel.Trace | -DarkGray | -NoChange | -
- To set up the target in the configuration file, - use the following syntax: -
-- This assumes just one target and a single rule. More configuration - options are described here. -
-- To set up the log target programmatically use code like this: -
--
-
System.Data.SqlClient -SQL Sever Client
- System.Data.SqlServerCe.3.5 -SQL Sever Compact 3.5
- System.Data.OracleClient -Oracle Client from Microsoft (deprecated in .NET Framework 4)
- Oracle.DataAccess.Client -ODP.NET provider from Oracle
- System.Data.SQLite -System.Data.SQLite driver for SQLite
- Npgsql -Npgsql driver for PostgreSQL
- MySql.Data.MySqlClient -MySQL Connector/Net
-
-
-
sqlserver ,mssql ,microsoft ormsde - SQL Server Data Provider
- oledb - OLEDB Data Provider
- odbc - ODBC Data Provider
-
- To set up the target in the configuration file, - use the following syntax: -
-- This assumes just one target and a single rule. More configuration - options are described here. -
-- To set up the log target programmatically use code like this: -
-- To set up the target in the configuration file, - use the following syntax: -
-- This assumes just one target and a single rule. More configuration - options are described here. -
-- To set up the log target programmatically use code like this: -
-${longdate}|${level:uppercase=true}|${logger}|${message}
- - To set up the target in the configuration file, - use the following syntax: -
-- This assumes just one target and a single rule. More configuration - options are described here. -
-- To set up the log target programmatically use code like this: -
-${longdate}|${level:uppercase=true}|${logger}|${message}
- ${basedir}/${level}.log
- All - a random value between 0 and 20 milliseconds - 2nd attempt
- a random value between 0 and 40 milliseconds - 3rd attempt
- a random value between 0 and 80 milliseconds - 4th attempt
- ... - and so on. -
- Caution: Enabling this option can considerably slow down your file
- logging in multi-process scenarios. If only one process is going to
- be writing to the file, consider setting
- To set up the target in the configuration file, - use the following syntax: -
-- The result is: -
-
- - To set up the log target programmatically similar to above use code like this: -
-${longdate}|${level:uppercase=true}|${logger}|${message}
- - To set up the target in the configuration file, - use the following syntax: -
-- This assumes just one target and a single rule. More configuration - options are described here. -
-- To set up the log target programmatically use code like this: -
-- Mail target works best when used with BufferingWrapper target - which lets you send multiple log messages in single mail -
-- To set up the buffered mail target in the configuration file, - use the following syntax: -
-- To set up the buffered mail target programmatically use code like this: -
-${longdate}|${level:uppercase=true}|${logger}|${message}
- - To set up the target in the configuration file, - use the following syntax: -
-- This assumes just one target and a single rule. More configuration - options are described here. -
-- To set up the log target programmatically use code like this: -
-${longdate}|${level:uppercase=true}|${logger}|${message}
- - To set up the target in the configuration file, - use the following syntax: -
-- This assumes just one target and a single rule. More configuration - options are described here. -
-- The result is a message box: -
-
- - To set up the log target programmatically use code like this: -
-${longdate}|${level:uppercase=true}|${logger}|${message}
- - To set up the target in the configuration file, - use the following syntax: -
-- This assumes just one target and a single rule. More configuration - options are described here. -
-- To set up the log target programmatically use code like this: -
-- To set up the target in the configuration file, - use the following syntax: -
-- This assumes just one target and a single rule. More configuration - options are described here. -
-- To set up the log target programmatically use code like this: -
-- To set up the target in the configuration file, - use the following syntax: -
-- This assumes just one target and a single rule. More configuration - options are described here. -
-- To set up the log target programmatically use code like this: -
-- To set up the target in the configuration file, - use the following syntax: -
-- This assumes just one target and a single rule. More configuration - options are described here. -
-- To set up the log target programmatically use code like this: -
-- To set up the target in the configuration file, - use the following syntax: -
-
- - The result is: -
- To set up the target with coloring rules in the configuration file, - use the following syntax: -
-
-
-
- - The result is: -
- To set up the log target programmatically similar to above use code like this: -
-
- ,
-
-
- for RowColoring,
-
-
- for WordColoring
- ${longdate}|${level:uppercase=true}|${logger}|${message}
- ${longdate}|${level:uppercase=true}|${logger}|${message}
- - To set up the target in the configuration file, - use the following syntax: -
-- This assumes just one target and a single rule. More configuration - options are described here. -
-- To set up the log target programmatically use code like this: -
-- To set up the target in the configuration file, - use the following syntax: -
-- This assumes just one target and a single rule. More configuration - options are described here. -
-- To set up the log target programmatically use code like this: -
-The example web service that works with this example is shown below
-- Asynchronous target wrapper allows the logger code to execute more quickly, by queueing - messages and processing them in a separate thread. You should wrap targets - that spend a non-trivial amount of time in their Write() method with asynchronous - target to speed up logging. -
-- Because asynchronous logging is quite a common scenario, NLog supports a - shorthand notation for wrapping all targets with AsyncWrapper. Just add async="true" to - the <targets/> element in the configuration file. -
-
-
- ... your targets go here ...
-
- ]]>
- - To set up the target in the configuration file, - use the following syntax: -
-- The above examples assume just one target and a single rule. See below for - a programmatic configuration that's equivalent to the above config file: -
-- To set up the target in the configuration file, - use the following syntax: -
-- The above examples assume just one target and a single rule. See below for - a programmatic configuration that's equivalent to the above config file: -
-${longdate}|${level:uppercase=true}|${logger}|${message}
- This example causes the messages to be written to server1, - and if it fails, messages go to server2.
-- To set up the target in the configuration file, - use the following syntax: -
-- The above examples assume just one target and a single rule. See below for - a programmatic configuration that's equivalent to the above config file: -
-This example causes the messages not contains the string '1' to be ignored.
-- To set up the target in the configuration file, - use the following syntax: -
-- The above examples assume just one target and a single rule. See below for - a programmatic configuration that's equivalent to the above config file: -
-- This example works like this. If there are no Warn,Error or Fatal messages in the buffer - only Info messages are written to the file, but if there are any warnings or errors, - the output includes detailed trace (levels >= Debug). You can plug in a different type - of buffering wrapper (such as ASPNetBufferingWrapper) to achieve different - functionality. -
-- To set up the target in the configuration file, - use the following syntax: -
-- The above examples assume just one target and a single rule. See below for - a programmatic configuration that's equivalent to the above config file: -
-This example causes the messages to be written to either file1.txt or file2.txt - chosen randomly on a per-message basis. -
-- To set up the target in the configuration file, - use the following syntax: -
-- The above examples assume just one target and a single rule. See below for - a programmatic configuration that's equivalent to the above config file: -
-This example causes each log message to be repeated 3 times.
-- To set up the target in the configuration file, - use the following syntax: -
-- The above examples assume just one target and a single rule. See below for - a programmatic configuration that's equivalent to the above config file: -
-This example causes each write attempt to be repeated 3 times, - sleeping 1 second between attempts if first one fails.
-- To set up the target in the configuration file, - use the following syntax: -
-- The above examples assume just one target and a single rule. See below for - a programmatic configuration that's equivalent to the above config file: -
-This example causes the messages to be written to either file1.txt or file2.txt. - Each odd message is written to file2.txt, each even message goes to file1.txt. -
-- To set up the target in the configuration file, - use the following syntax: -
-- The above examples assume just one target and a single rule. See below for - a programmatic configuration that's equivalent to the above config file: -
-This example causes the messages to be written to both file1.txt or file2.txt -
-- To set up the target in the configuration file, - use the following syntax: -
-- The above examples assume just one target and a single rule. See below for - a programmatic configuration that's equivalent to the above config file: -
--
-
-
-
TvdbEpisodeBanner -Each episode may contain a small image that should be an non-spoiler action shot from the episode (http://thetvdb.com/wiki/index.php/Episode_Images) -
- -
-
TvdbFanartBanner -Fan Art is high quality artwork that is displayed in the background of HTPC menus (http://thetvdb.com/wiki/index.php/Fan_Art) -
- -
-
TvdbSeasonBanner -Banner for each season of a series, dvd-style (400 x 578) or banner style (758 x 140) (http://thetvdb.com/wiki/index.php/Wide_Season_Banners) -
- -
-
TvdbSeriesBanner -Wide banner for each series (758 x 140), comes in graphical, text or blank style. For further information see http://thetvdb.com/wiki/index.php/Series_Banners -
- -
-
TvdbPosterBanner -Newest addition to the tvdb graphical section (680px x 1000px) and not smaller than 500k (http://thetvdb.com/wiki/index.php/Posters) -
-
-
- Those are:
- 332179
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- - ]]> - Additionally the banner image is stored -
- 1. Absolute Episode Order
- 2. DVD Release Order
-
- More information on the topic can be found at: http://thetvdb.com/wiki/index.php/Category:Episodes -
- Author of the original java version : John Leuner -
setInput(input, 0, input.length).
- setDictionary(dict, 0, dict.Length).
- -
Author of the original java version : Jochen Hoenicke -
- using System;
- using System.Text;
- using System.IO;
-
- using ICSharpCode.SharpZipLib.Zip;
-
- class MainClass
- {
- public static void Main(string[] args)
- {
- using ( ZipInputStream s = new ZipInputStream(File.OpenRead(args[0]))) {
-
- ZipEntry theEntry;
- while ((theEntry = s.GetNextEntry()) != null) {
- int size = 2048;
- byte[] data = new byte[2048];
-
- Console.Write("Show contents (y/n) ?");
- if (Console.ReadLine() == "y") {
- while (true) {
- size = s.Read(data, 0, data.Length);
- if (size > 0) {
- Console.Write(new ASCIIEncoding().GetString(data, 0, size));
- } else {
- break;
- }
- }
- }
- }
- }
- }
- }
-
- public Inflater(bool noHeader) passing true
- if there is no Zlib header information
-
- The usage is as following. First you have to set some input with
- SetInput(), then Inflate() it. If inflate doesn't
- inflate any bytes there may be three reasons:
- -
-
- IsNeedingInput() returns true because the input buffer is empty.
- You have to provide more input with
SetInput(). - NOTE: IsNeedingInput() also returns true when, the stream is finished. -
- - IsNeedingDictionary() returns true, you have to provide a preset
- dictionary with
SetDictionary().
- - IsFinished returns true, the inflater has finished. -
getValue. The complete checksum object can also be reset
- so it can be used again with new data.
- -
Author of the original java version : Jochen Hoenicke -
-
- Bit 0: If set, indicates the file is encrypted
- Bit 1-2 Only used for compression type 6 Imploding, and 8, 9 deflating
- Imploding:
- Bit 1 if set indicates an 8K sliding dictionary was used. If clear a 4k dictionary was used
- Bit 2 if set indicates 3 Shannon-Fanno trees were used to encode the sliding dictionary, 2 otherwise
-
- Deflating:
- Bit 2 Bit 1
- 0 0 Normal compression was used
- 0 1 Maximum compression was used
- 1 0 Fast compression was used
- 1 1 Super fast compression was used
-
- Bit 3: If set, the fields crc-32, compressed size - and uncompressed size are were not able to be written during zip file creation - The correct values are held in a data descriptor immediately following the compressed data.
- Bit 4: Reserved for use by PKZIP for enhanced deflating
- Bit 5: If set indicates the file contains compressed patch data
- Bit 6: If set indicates strong encryption was used.
- Bit 7-10: Unused or reserved
- Bit 11: If set the name and comments for this entry are in unicode.
- Bit 12-15: Unused or reserved
-
-
-
- 0 - MS-DOS and OS/2 (FAT / VFAT / FAT32 file systems) -
- 1 - Amiga -
- 2 - OpenVMS -
- 3 - Unix -
- 4 - VM/CMS -
- 5 - Atari ST -
- 6 - OS/2 HPFS -
- 7 - Macintosh -
- 8 - Z-System -
- 9 - CP/M -
- 10 - Windows NTFS -
- 11 - MVS (OS/390 - Z/OS) -
- 12 - VSE -
- 13 - Acorn Risc -
- 14 - VFAT -
- 15 - Alternate MVS -
- 16 - BeOS -
- 17 - Tandem -
- 18 - OS/400 -
- 19 - OS/X (Darwin) -
- 99 - WinZip AES -
- remainder - unused -
- 1.0 - Default value
- 1.1 - File is a volume label
- 2.0 - File is a folder/directory
- 2.0 - File is compressed using Deflate compression
- 2.0 - File is encrypted using traditional encryption
- 2.1 - File is compressed using Deflate64
- 2.5 - File is compressed using PKWARE DCL Implode
- 2.7 - File is a patch data set
- 4.5 - File uses Zip64 format extensions
- 4.6 - File is compressed using BZIP2 compression
- 5.0 - File is encrypted using DES
- 5.0 - File is encrypted using 3DES
- 5.0 - File is encrypted using original RC2 encryption
- 5.0 - File is encrypted using RC4 encryption
- 5.1 - File is encrypted using AES encryption
- 5.1 - File is encrypted using corrected RC2 encryption
- 5.1 - File is encrypted using corrected RC2-64 encryption
- 6.1 - File is encrypted using non-OAEP key wrapping
- 6.2 - Central directory encryption (not confirmed yet)
- 6.3 - File is compressed using LZMA
- 6.3 - File is compressed using PPMD+
- 6.3 - File is encrypted using Blowfish
- 6.3 - File is encrypted using Twofish
-
- Authors of the original java version : Tom Tromey, Jochen Hoenicke -
def.deflate() until all bytes from the input buffers
- are processed.
- -
- Those are as follows:
-
- - Base information:
-
-
- 73739
- |Malcolm David Kelley|Jorge Garcia|Maggie Grace|...|
- Thursday
- 9:00 PM
- TV-14
- 2004-09-22
- |Action and Adventure|Drama|Science-Fiction|
- tt0411008
- en
- ABC
- After Oceanic Air flight 815...
- 8.9
- 60
- 24313
- Lost
- Continuing
- graphical/24313-g2.jpg
- fanart/original/73739-1.jpg
- 1205694666
- SH672362
-
-
- - Banner information - - Episode information
- - Extended actor information
-
- Each of those can be downloaded seperately. If the information is downloaded as - zipped file, everything is downloaded at once -
NeedsInput()
- returns true
-
- strstart + MAX_MATCH <= window.length.
- prev[index & WMASK] points to the previous index that has the
- same hash code as the string starting at index. This way
- entries with the same hash code are in a linked list.
- Note that the array should really be unsigned short, so you need
- to and the values with 0xffff.
-