diff --git a/WebSCR/NLog.config b/WebSCR/NLog.config index 13ec9f7..7a0f3aa 100644 --- a/WebSCR/NLog.config +++ b/WebSCR/NLog.config @@ -4,28 +4,27 @@ xsi:schemaLocation="http://www.nlog-project.org/schemas/NLog.xsd NLog.xsd" autoReload="true" throwExceptions="false" - internalLogLevel="Off" internalLogFile="c:\temp\nlog-internal.log" > + internalLogLevel="Off" internalLogFile="c:\temp\nlog-internal.log"> - - - - @@ -39,4 +38,4 @@ --> - \ No newline at end of file + diff --git a/WebSCR/NLog.xsd b/WebSCR/NLog.xsd index a719741..6b26042 100644 --- a/WebSCR/NLog.xsd +++ b/WebSCR/NLog.xsd @@ -42,7 +42,32 @@ - Pass NLog internal exceptions to the application. Default value is: false. + Throw an exception when there is an internal error. Default value is: false. + + + + + Throw an exception when there is a configuration error. If not set, determined by throwExceptions. + + + + + Gets or sets a value indicating whether Variables should be kept on configuration reload. Default value is: false. + + + + + Write internal NLog messages to the System.Diagnostics.Trace. Default value is: false. + + + + + Write timestamps for internal NLog messages. Default value is: true. + + + + + Use InvariantCulture as default culture instead of CurrentCulture. Default value is: false. @@ -169,7 +194,7 @@ - Name of the file to be included. The name is relative to the name of the current config file. + Name of the file to be included. You could use * wildcard. The name is relative to the name of the current config file. @@ -227,7 +252,6 @@ - @@ -240,41 +264,17 @@ - - - - - - - - - - - Name of the target. - - - - - Layout used to format log messages. - - - - - Indicates whether to add <!-- --> comments around all written texts. - - - - - + + @@ -286,6 +286,11 @@ Number of log events that should be processed in a batch by the lazy writer thread. + + + Limit of full s to write before yielding into Performance is better when writing many small batches, than writing a single large batch + + Action to be taken when the lazy writer thread request queue count exceeds the set limit. @@ -301,6 +306,11 @@ Time in milliseconds to sleep between batches. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -316,12 +326,30 @@ + + + Name of the target. + + + Delay the flush until the LogEvent has been confirmed as written + + + + + Condition expression. Log events who meet this condition will cause a flush on the wrapped target. + + + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -333,6 +361,7 @@ + @@ -354,6 +383,11 @@ Indicates whether to use sliding timeout. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -364,23 +398,26 @@ + + - - - - - + + + + + + @@ -397,6 +434,11 @@ Instance of that is used to format log messages. + + + End of line value if a newline is appended at the end of log message . + + Maximum message size in bytes. @@ -417,6 +459,11 @@ Action that should be taken if the message is larger than maxMessageSize. + + + Maximum current connections. 0 = no maximum. + + Indicates whether to keep connection open whenever possible. @@ -427,11 +474,6 @@ Size of the connection cache (number of connections which are kept alive). - - - Maximum current connections. 0 = no maximum. - - Network address. @@ -442,19 +484,24 @@ Maximum queue size. + + + Indicates whether to include stack contents. + + Indicates whether to include source info (file name and line number) in the information sent over the network. - + - NDC item separator. + Indicates whether to include NLog-specific extensions to log4j schema. - + - Indicates whether to include stack contents. + Indicates whether to include dictionary contents. @@ -467,16 +514,21 @@ AppInfo field. By default it's the friendly name of the current AppDomain. - + - Indicates whether to include NLog-specific extensions to log4j schema. + NDC item separator. - + Indicates whether to include dictionary contents. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -521,8 +573,10 @@ + + @@ -549,6 +603,11 @@ Indicates whether to use default row highlighting rules. + + + Indicates whether to auto-check if the console is available. - Disables console writing if Environment.UserInteractive = False (Windows Service) - Disables console writing if Console Standard Input is not available (Non-Console-App) + + The encoding for writing messages to the . @@ -559,6 +618,11 @@ Indicates whether the error stream (stderr) should be used instead of the output stream (stdout). + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -611,6 +675,7 @@ + @@ -634,6 +699,11 @@ Indicates whether to match whole words only. + + + Compile the ? This can improve the performance, but at the costs of more memory usage. If false, the Regex Cache is used. + + Background color. @@ -654,7 +724,9 @@ + + @@ -681,11 +753,21 @@ Indicates whether to send the log messages to the standard error instead of the standard output. + + + Indicates whether to auto-check if the console is available - Disables console writing if Environment.UserInteractive = False (Windows Service) - Disables console writing if Console Standard Input is not available (Non-Console-App) + + The encoding for writing messages to the . + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -694,77 +776,83 @@ - - - - - - - - + + + + + + + + + + - Name of the target. - - - Connection string. When provided, it overrides the values specified in DBHost, DBUserName, DBPassword, DBDatabase. - - - - - Name of the connection string (as specified in <connectionStrings> configuration section. - - - - - Database name. If the ConnectionString is not provided this value will be used to construct the "Database=" part of the connection string. - - - - - Database host name. If the ConnectionString is not provided this value will be used to construct the "Server=" part of the connection string. - - - - - Database password. If the ConnectionString is not provided this value will be used to construct the "Password=" part of the connection string. - - - - - Name of the database provider. - - - - - Database user name. If the ConnectionString is not provided this value will be used to construct the "User ID=" part of the connection string. - - - - - Indicates whether to keep the database connection open between the log events. - - Obsolete - value will be ignored! The logging code always runs outside of transaction. Gets or sets a value indicating whether to use database transactions. Some data providers require this. + + + Database user name. If the ConnectionString is not provided this value will be used to construct the "User ID=" part of the connection string. + + + + + Name of the database provider. + + + + + Database password. If the ConnectionString is not provided this value will be used to construct the "Password=" part of the connection string. + + + + + Indicates whether to keep the database connection open between the log events. + + + + + Database name. If the ConnectionString is not provided this value will be used to construct the "Database=" part of the connection string. + + + + + Name of the connection string (as specified in <connectionStrings> configuration section. + + + + + Connection string. When provided, it overrides the values specified in DBHost, DBUserName, DBPassword, DBDatabase. + + + + + Database host name. If the ConnectionString is not provided this value will be used to construct the "Server=" part of the connection string. + + Connection string using for installation and uninstallation. If not provided, regular ConnectionString is being used. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + Text of the SQL command to be run on each log level. @@ -856,6 +944,7 @@ + @@ -877,6 +966,11 @@ Footer. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -886,6 +980,7 @@ + @@ -897,6 +992,11 @@ Layout used to format log messages. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -911,7 +1011,11 @@ + + + + @@ -948,20 +1052,48 @@ Value to be used as the event Source. + + + Action to take if the message is larger than the option. + + Optional entrytype. When not set, or when not convertable to then determined by + + + Maximum Event log size in kilobytes. If null, the value won't be set. Default is 512 Kilobytes as specified by Eventlog API + + + + + Message length limit to write to the Event Log. + + + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + + + + + + + + + @@ -973,6 +1105,11 @@ Indicates whether to return to the first target after any successful write. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -990,10 +1127,15 @@ - + + + + + + @@ -1003,15 +1145,16 @@ - + + + - @@ -1063,19 +1206,24 @@ Size in bytes above which log files will be automatically archived. Warning: combining this with isn't supported. We cannot create multiple archive files, if they should have the same name. Choose: - - - Maximum number of archive files that should be kept. - - Indicates whether to compress archive files into the zip archive format. + + + Maximum number of archive files that should be kept. + + - Gets or set a value indicating whether a managed file stream is forced, instead of used the native implementation. + Gets or set a value indicating whether a managed file stream is forced, instead of using the native implementation. + + + + + Is the an absolute or relative path? @@ -1083,6 +1231,26 @@ Cleanup invalid values in a filename, e.g. slashes in a filename. If set to true, this can impact the performance of massive writes. If set to false, nothing gets written when the filename is wrong. + + + Whether or not this target should just discard all data that its asked to write. Mostly used for when testing NLog Stack except final write + + + + + Is the an absolute or relative path? + + + + + Value indicationg whether file creation calls should be synchronized by a system global mutex. + + + + + Indicates whether the footer should be written only when the file is archived. + + Name of the file to write to. @@ -1090,7 +1258,7 @@ - Value specifying the date format to use when archving files. + Value specifying the date format to use when archiving files. @@ -1128,9 +1296,9 @@ Indicates whether concurrent writes to the log file by multiple processes on the same host. - + - Delay in milliseconds to wait before attempting to write to the file again. + Indicates whether to keep log file open instead of opening and closing it on each logging event. @@ -1153,6 +1321,11 @@ Maximum number of seconds that files are kept open. If this number is negative the files are not automatically closed after a period of inactivity. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + Log file buffer size in bytes. @@ -1163,16 +1336,16 @@ Indicates whether to automatically flush the file buffers after each log message. + + + Delay in milliseconds to wait before attempting to write to the file again. + + Number of times the write is appended on the file before NLog discards the log message. - - - Indicates whether to keep log file open instead of opening and closing it on each logging event. - - @@ -1192,6 +1365,20 @@ + + + + + + + + + + + + + + @@ -1220,6 +1407,7 @@ + @@ -1231,6 +1419,11 @@ Condition expression. Log events who meet this condition will be forwarded to the wrapped target. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -1246,6 +1439,7 @@ + @@ -1287,6 +1481,11 @@ Username to change context to. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -1313,6 +1512,38 @@ + + + + + + + + + + + + Name of the target. + + + + + Interval in which messages will be written up to the number of messages. + + + + + Maximum allowed number of messages written per . + + + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + + + + @@ -1325,6 +1556,7 @@ + @@ -1361,6 +1593,11 @@ Indicates whether to use binary message encoding. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -1368,6 +1605,7 @@ + @@ -1380,11 +1618,16 @@ Name of the parameter. - + Type of the parameter. + + + Type of the parameter. Obsolete alias for + + @@ -1403,9 +1646,10 @@ - - + + + @@ -1481,9 +1725,9 @@ Sender's email address (e.g. joe@domain.com). - + - Indicates whether NewLine characters in the body should be replaced with tags. + Indicates the SMTP client timeout. @@ -1491,9 +1735,14 @@ Priority used for sending mails. - + - Indicates the SMTP client timeout. + Indicates whether NewLine characters in the body should be replaced with tags. + + + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit @@ -1564,6 +1813,7 @@ + @@ -1575,6 +1825,11 @@ Layout used to format log messages. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -1587,6 +1842,7 @@ + @@ -1617,6 +1873,11 @@ Indicates whether to check if a queue exists before writing to it. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + Indicates whether to create the queue if it doesn't exists. @@ -1648,6 +1909,7 @@ + @@ -1661,7 +1923,12 @@ - Method name. The method must be public and static. + Method name. The method must be public and static. Use the AssemblyQualifiedName , https://msdn.microsoft.com/en-us/library/system.type.assemblyqualifiedname(v=vs.110).aspx e.g. + + + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit @@ -1674,6 +1941,7 @@ + @@ -1683,6 +1951,7 @@ + @@ -1699,6 +1968,11 @@ Encoding to be used. + + + End of line value if a newline is appended at the end of log message . + + Maximum message size in bytes. @@ -1744,6 +2018,11 @@ Maximum queue size. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -1754,23 +2033,26 @@ + + - - - - - + + + + + + @@ -1787,6 +2069,11 @@ Instance of that is used to format log messages. + + + End of line value if a newline is appended at the end of log message . + + Maximum message size in bytes. @@ -1807,6 +2094,11 @@ Action that should be taken if the message is larger than maxMessageSize. + + + Maximum current connections. 0 = no maximum. + + Indicates whether to keep connection open whenever possible. @@ -1817,11 +2109,6 @@ Size of the connection cache (number of connections which are kept alive). - - - Maximum current connections. 0 = no maximum. - - Network address. @@ -1832,29 +2119,14 @@ Maximum queue size. - - - Indicates whether to include source info (file name and line number) in the information sent over the network. - - - - - NDC item separator. - - Indicates whether to include stack contents. - + - Indicates whether to include call site (class and method name) in the information sent over the network. - - - - - AppInfo field. By default it's the friendly name of the current AppDomain. + Indicates whether to include source info (file name and line number) in the information sent over the network. @@ -1867,6 +2139,31 @@ Indicates whether to include dictionary contents. + + + Indicates whether to include call site (class and method name) in the information sent over the network. + + + + + AppInfo field. By default it's the friendly name of the current AppDomain. + + + + + NDC item separator. + + + + + Indicates whether to include dictionary contents. + + + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -1877,6 +2174,7 @@ + @@ -1893,6 +2191,11 @@ Indicates whether to perform layout calculation. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -1902,6 +2205,7 @@ + @@ -1913,6 +2217,11 @@ Layout used to format log messages. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -1928,6 +2237,7 @@ + @@ -1969,6 +2279,11 @@ Performance counter instance name. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -2011,6 +2326,7 @@ + @@ -2022,6 +2338,11 @@ Default filter to be applied when no specific rule matches. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -2046,12 +2367,18 @@ + Name of the target. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -2060,6 +2387,7 @@ + @@ -2067,6 +2395,11 @@ Name of the target. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + Number of times to repeat each log message. @@ -2080,6 +2413,7 @@ + @@ -2088,6 +2422,11 @@ Name of the target. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + Number of retries that should be attempted on the wrapped target in case of a failure. @@ -2106,12 +2445,18 @@ + Name of the target. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -2120,12 +2465,18 @@ + Name of the target. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -2135,6 +2486,7 @@ + @@ -2146,6 +2498,11 @@ Layout used to format log messages. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -2156,11 +2513,16 @@ + + + + + @@ -2172,11 +2534,26 @@ Should we include the BOM (Byte-order-mark) for UTF? Influences the property. This will only work for UTF-8. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + Encoding. + + + Value whether escaping be done according to the old NLog style (Very non-standard) + + + + + Value whether escaping be done according to Rfc3986 (Supports Internationalized Resource Identifiers - IRIs) + + Web service method name. Only used with Soap. @@ -2197,6 +2574,16 @@ Web service URL. + + + Name of the root XML element, if POST of XML document chosen. If so, this property must not be null. (see and ). + + + + + (optional) root namespace of the XML document, if POST of XML document chosen. (see and ). + + @@ -2206,8 +2593,22 @@ + + + + + + + + + + + + + + @@ -2304,19 +2705,50 @@ + + + + + + + + List of property names to exclude when is true + + + + + Option to include all properties from the log events + + + + + Indicates whether to include contents of the dictionary. + + + + + Option to render the empty object value {} + + Option to suppress the extra spaces in the output json + + + Indicates whether to include contents of the dictionary. + + + @@ -2325,6 +2757,11 @@ Determines wether or not this attribute will be Json encoded. + + + Indicates whether to escape non-ascii characters + + Layout that will be rendered as the attribute's value. @@ -2365,7 +2802,26 @@ - + + + + + + + + Option to include all properties from the log events + + + + + Indicates whether to include contents of the dictionary. + + + + + Indicates whether to include contents of the dictionary. + + diff --git a/WebSCR/Web.config b/WebSCR/Web.config index b69a4e2..e7ee257 100644 --- a/WebSCR/Web.config +++ b/WebSCR/Web.config @@ -1,64 +1,64 @@ - + -
-
-
-
+
+
+
+
- - - - - - + + + + + + - - - + + + - - - - + + + + - - - - - + + + + + - - - - - - + + + + + + - - - + + + - + - + - + - + - - - + + + - - - + + + - + - + - + - + - + - + - - - + + + @@ -134,7 +134,7 @@ redisSerializerType = "" [String] /> --> - + @@ -143,19 +143,19 @@ Information Services 7.0. It is not necessary for previous version of IIS. --> - + - - - - + + + + - - - + + + @@ -163,12 +163,12 @@ See http://code.google.com/p/elmah/wiki/SecuringErrorLogPages for more information on remote access and securing ELMAH. --> - + - + - - @@ -39,4 +38,4 @@ --> - \ No newline at end of file + diff --git a/packages/NLog.Config.4.2.3/tools/Install.ps1 b/packages/NLog.Config.4.4.10/tools/Install.ps1 similarity index 100% rename from packages/NLog.Config.4.2.3/tools/Install.ps1 rename to packages/NLog.Config.4.4.10/tools/Install.ps1 diff --git a/packages/NLog.Schema.4.2.3/NLog.Schema.4.2.3.nupkg b/packages/NLog.Schema.4.2.3/NLog.Schema.4.2.3.nupkg deleted file mode 100644 index 4dc352c..0000000 Binary files a/packages/NLog.Schema.4.2.3/NLog.Schema.4.2.3.nupkg and /dev/null differ diff --git a/packages/NLog.Schema.4.4.10/NLog.Schema.4.4.10.nupkg b/packages/NLog.Schema.4.4.10/NLog.Schema.4.4.10.nupkg new file mode 100644 index 0000000..21ee2b7 Binary files /dev/null and b/packages/NLog.Schema.4.4.10/NLog.Schema.4.4.10.nupkg differ diff --git a/packages/NLog.Schema.4.2.3/content/NLog.xsd b/packages/NLog.Schema.4.4.10/content/NLog.xsd similarity index 79% rename from packages/NLog.Schema.4.2.3/content/NLog.xsd rename to packages/NLog.Schema.4.4.10/content/NLog.xsd index a719741..6b26042 100644 --- a/packages/NLog.Schema.4.2.3/content/NLog.xsd +++ b/packages/NLog.Schema.4.4.10/content/NLog.xsd @@ -42,7 +42,32 @@ - Pass NLog internal exceptions to the application. Default value is: false. + Throw an exception when there is an internal error. Default value is: false. + + + + + Throw an exception when there is a configuration error. If not set, determined by throwExceptions. + + + + + Gets or sets a value indicating whether Variables should be kept on configuration reload. Default value is: false. + + + + + Write internal NLog messages to the System.Diagnostics.Trace. Default value is: false. + + + + + Write timestamps for internal NLog messages. Default value is: true. + + + + + Use InvariantCulture as default culture instead of CurrentCulture. Default value is: false. @@ -169,7 +194,7 @@ - Name of the file to be included. The name is relative to the name of the current config file. + Name of the file to be included. You could use * wildcard. The name is relative to the name of the current config file. @@ -227,7 +252,6 @@ - @@ -240,41 +264,17 @@ - - - - - - - - - - - Name of the target. - - - - - Layout used to format log messages. - - - - - Indicates whether to add <!-- --> comments around all written texts. - - - - - + + @@ -286,6 +286,11 @@ Number of log events that should be processed in a batch by the lazy writer thread. + + + Limit of full s to write before yielding into Performance is better when writing many small batches, than writing a single large batch + + Action to be taken when the lazy writer thread request queue count exceeds the set limit. @@ -301,6 +306,11 @@ Time in milliseconds to sleep between batches. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -316,12 +326,30 @@ + + + Name of the target. + + + Delay the flush until the LogEvent has been confirmed as written + + + + + Condition expression. Log events who meet this condition will cause a flush on the wrapped target. + + + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -333,6 +361,7 @@ + @@ -354,6 +383,11 @@ Indicates whether to use sliding timeout. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -364,23 +398,26 @@ + + - - - - - + + + + + + @@ -397,6 +434,11 @@ Instance of that is used to format log messages. + + + End of line value if a newline is appended at the end of log message . + + Maximum message size in bytes. @@ -417,6 +459,11 @@ Action that should be taken if the message is larger than maxMessageSize. + + + Maximum current connections. 0 = no maximum. + + Indicates whether to keep connection open whenever possible. @@ -427,11 +474,6 @@ Size of the connection cache (number of connections which are kept alive). - - - Maximum current connections. 0 = no maximum. - - Network address. @@ -442,19 +484,24 @@ Maximum queue size. + + + Indicates whether to include stack contents. + + Indicates whether to include source info (file name and line number) in the information sent over the network. - + - NDC item separator. + Indicates whether to include NLog-specific extensions to log4j schema. - + - Indicates whether to include stack contents. + Indicates whether to include dictionary contents. @@ -467,16 +514,21 @@ AppInfo field. By default it's the friendly name of the current AppDomain. - + - Indicates whether to include NLog-specific extensions to log4j schema. + NDC item separator. - + Indicates whether to include dictionary contents. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -521,8 +573,10 @@ + + @@ -549,6 +603,11 @@ Indicates whether to use default row highlighting rules. + + + Indicates whether to auto-check if the console is available. - Disables console writing if Environment.UserInteractive = False (Windows Service) - Disables console writing if Console Standard Input is not available (Non-Console-App) + + The encoding for writing messages to the . @@ -559,6 +618,11 @@ Indicates whether the error stream (stderr) should be used instead of the output stream (stdout). + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -611,6 +675,7 @@ + @@ -634,6 +699,11 @@ Indicates whether to match whole words only. + + + Compile the ? This can improve the performance, but at the costs of more memory usage. If false, the Regex Cache is used. + + Background color. @@ -654,7 +724,9 @@ + + @@ -681,11 +753,21 @@ Indicates whether to send the log messages to the standard error instead of the standard output. + + + Indicates whether to auto-check if the console is available - Disables console writing if Environment.UserInteractive = False (Windows Service) - Disables console writing if Console Standard Input is not available (Non-Console-App) + + The encoding for writing messages to the . + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -694,77 +776,83 @@ - - - - - - - - + + + + + + + + + + - Name of the target. - - - Connection string. When provided, it overrides the values specified in DBHost, DBUserName, DBPassword, DBDatabase. - - - - - Name of the connection string (as specified in <connectionStrings> configuration section. - - - - - Database name. If the ConnectionString is not provided this value will be used to construct the "Database=" part of the connection string. - - - - - Database host name. If the ConnectionString is not provided this value will be used to construct the "Server=" part of the connection string. - - - - - Database password. If the ConnectionString is not provided this value will be used to construct the "Password=" part of the connection string. - - - - - Name of the database provider. - - - - - Database user name. If the ConnectionString is not provided this value will be used to construct the "User ID=" part of the connection string. - - - - - Indicates whether to keep the database connection open between the log events. - - Obsolete - value will be ignored! The logging code always runs outside of transaction. Gets or sets a value indicating whether to use database transactions. Some data providers require this. + + + Database user name. If the ConnectionString is not provided this value will be used to construct the "User ID=" part of the connection string. + + + + + Name of the database provider. + + + + + Database password. If the ConnectionString is not provided this value will be used to construct the "Password=" part of the connection string. + + + + + Indicates whether to keep the database connection open between the log events. + + + + + Database name. If the ConnectionString is not provided this value will be used to construct the "Database=" part of the connection string. + + + + + Name of the connection string (as specified in <connectionStrings> configuration section. + + + + + Connection string. When provided, it overrides the values specified in DBHost, DBUserName, DBPassword, DBDatabase. + + + + + Database host name. If the ConnectionString is not provided this value will be used to construct the "Server=" part of the connection string. + + Connection string using for installation and uninstallation. If not provided, regular ConnectionString is being used. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + Text of the SQL command to be run on each log level. @@ -856,6 +944,7 @@ + @@ -877,6 +966,11 @@ Footer. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -886,6 +980,7 @@ + @@ -897,6 +992,11 @@ Layout used to format log messages. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -911,7 +1011,11 @@ + + + + @@ -948,20 +1052,48 @@ Value to be used as the event Source. + + + Action to take if the message is larger than the option. + + Optional entrytype. When not set, or when not convertable to then determined by + + + Maximum Event log size in kilobytes. If null, the value won't be set. Default is 512 Kilobytes as specified by Eventlog API + + + + + Message length limit to write to the Event Log. + + + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + + + + + + + + + @@ -973,6 +1105,11 @@ Indicates whether to return to the first target after any successful write. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -990,10 +1127,15 @@ - + + + + + + @@ -1003,15 +1145,16 @@ - + + + - @@ -1063,19 +1206,24 @@ Size in bytes above which log files will be automatically archived. Warning: combining this with isn't supported. We cannot create multiple archive files, if they should have the same name. Choose: - - - Maximum number of archive files that should be kept. - - Indicates whether to compress archive files into the zip archive format. + + + Maximum number of archive files that should be kept. + + - Gets or set a value indicating whether a managed file stream is forced, instead of used the native implementation. + Gets or set a value indicating whether a managed file stream is forced, instead of using the native implementation. + + + + + Is the an absolute or relative path? @@ -1083,6 +1231,26 @@ Cleanup invalid values in a filename, e.g. slashes in a filename. If set to true, this can impact the performance of massive writes. If set to false, nothing gets written when the filename is wrong. + + + Whether or not this target should just discard all data that its asked to write. Mostly used for when testing NLog Stack except final write + + + + + Is the an absolute or relative path? + + + + + Value indicationg whether file creation calls should be synchronized by a system global mutex. + + + + + Indicates whether the footer should be written only when the file is archived. + + Name of the file to write to. @@ -1090,7 +1258,7 @@ - Value specifying the date format to use when archving files. + Value specifying the date format to use when archiving files. @@ -1128,9 +1296,9 @@ Indicates whether concurrent writes to the log file by multiple processes on the same host. - + - Delay in milliseconds to wait before attempting to write to the file again. + Indicates whether to keep log file open instead of opening and closing it on each logging event. @@ -1153,6 +1321,11 @@ Maximum number of seconds that files are kept open. If this number is negative the files are not automatically closed after a period of inactivity. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + Log file buffer size in bytes. @@ -1163,16 +1336,16 @@ Indicates whether to automatically flush the file buffers after each log message. + + + Delay in milliseconds to wait before attempting to write to the file again. + + Number of times the write is appended on the file before NLog discards the log message. - - - Indicates whether to keep log file open instead of opening and closing it on each logging event. - - @@ -1192,6 +1365,20 @@ + + + + + + + + + + + + + + @@ -1220,6 +1407,7 @@ + @@ -1231,6 +1419,11 @@ Condition expression. Log events who meet this condition will be forwarded to the wrapped target. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -1246,6 +1439,7 @@ + @@ -1287,6 +1481,11 @@ Username to change context to. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -1313,6 +1512,38 @@ + + + + + + + + + + + + Name of the target. + + + + + Interval in which messages will be written up to the number of messages. + + + + + Maximum allowed number of messages written per . + + + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + + + + @@ -1325,6 +1556,7 @@ + @@ -1361,6 +1593,11 @@ Indicates whether to use binary message encoding. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -1368,6 +1605,7 @@ + @@ -1380,11 +1618,16 @@ Name of the parameter. - + Type of the parameter. + + + Type of the parameter. Obsolete alias for + + @@ -1403,9 +1646,10 @@ - - + + + @@ -1481,9 +1725,9 @@ Sender's email address (e.g. joe@domain.com). - + - Indicates whether NewLine characters in the body should be replaced with tags. + Indicates the SMTP client timeout. @@ -1491,9 +1735,14 @@ Priority used for sending mails. - + - Indicates the SMTP client timeout. + Indicates whether NewLine characters in the body should be replaced with tags. + + + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit @@ -1564,6 +1813,7 @@ + @@ -1575,6 +1825,11 @@ Layout used to format log messages. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -1587,6 +1842,7 @@ + @@ -1617,6 +1873,11 @@ Indicates whether to check if a queue exists before writing to it. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + Indicates whether to create the queue if it doesn't exists. @@ -1648,6 +1909,7 @@ + @@ -1661,7 +1923,12 @@ - Method name. The method must be public and static. + Method name. The method must be public and static. Use the AssemblyQualifiedName , https://msdn.microsoft.com/en-us/library/system.type.assemblyqualifiedname(v=vs.110).aspx e.g. + + + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit @@ -1674,6 +1941,7 @@ + @@ -1683,6 +1951,7 @@ + @@ -1699,6 +1968,11 @@ Encoding to be used. + + + End of line value if a newline is appended at the end of log message . + + Maximum message size in bytes. @@ -1744,6 +2018,11 @@ Maximum queue size. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -1754,23 +2033,26 @@ + + - - - - - + + + + + + @@ -1787,6 +2069,11 @@ Instance of that is used to format log messages. + + + End of line value if a newline is appended at the end of log message . + + Maximum message size in bytes. @@ -1807,6 +2094,11 @@ Action that should be taken if the message is larger than maxMessageSize. + + + Maximum current connections. 0 = no maximum. + + Indicates whether to keep connection open whenever possible. @@ -1817,11 +2109,6 @@ Size of the connection cache (number of connections which are kept alive). - - - Maximum current connections. 0 = no maximum. - - Network address. @@ -1832,29 +2119,14 @@ Maximum queue size. - - - Indicates whether to include source info (file name and line number) in the information sent over the network. - - - - - NDC item separator. - - Indicates whether to include stack contents. - + - Indicates whether to include call site (class and method name) in the information sent over the network. - - - - - AppInfo field. By default it's the friendly name of the current AppDomain. + Indicates whether to include source info (file name and line number) in the information sent over the network. @@ -1867,6 +2139,31 @@ Indicates whether to include dictionary contents. + + + Indicates whether to include call site (class and method name) in the information sent over the network. + + + + + AppInfo field. By default it's the friendly name of the current AppDomain. + + + + + NDC item separator. + + + + + Indicates whether to include dictionary contents. + + + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -1877,6 +2174,7 @@ + @@ -1893,6 +2191,11 @@ Indicates whether to perform layout calculation. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -1902,6 +2205,7 @@ + @@ -1913,6 +2217,11 @@ Layout used to format log messages. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -1928,6 +2237,7 @@ + @@ -1969,6 +2279,11 @@ Performance counter instance name. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -2011,6 +2326,7 @@ + @@ -2022,6 +2338,11 @@ Default filter to be applied when no specific rule matches. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -2046,12 +2367,18 @@ + Name of the target. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -2060,6 +2387,7 @@ + @@ -2067,6 +2395,11 @@ Name of the target. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + Number of times to repeat each log message. @@ -2080,6 +2413,7 @@ + @@ -2088,6 +2422,11 @@ Name of the target. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + Number of retries that should be attempted on the wrapped target in case of a failure. @@ -2106,12 +2445,18 @@ + Name of the target. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -2120,12 +2465,18 @@ + Name of the target. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -2135,6 +2486,7 @@ + @@ -2146,6 +2498,11 @@ Layout used to format log messages. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + @@ -2156,11 +2513,16 @@ + + + + + @@ -2172,11 +2534,26 @@ Should we include the BOM (Byte-order-mark) for UTF? Influences the property. This will only work for UTF-8. + + + Target supports reuse of internal buffers, and doesn't have to constantly allocate new buffers Required for legacy NLog-targets, that expects buffers to remain stable after Write-method exit + + Encoding. + + + Value whether escaping be done according to the old NLog style (Very non-standard) + + + + + Value whether escaping be done according to Rfc3986 (Supports Internationalized Resource Identifiers - IRIs) + + Web service method name. Only used with Soap. @@ -2197,6 +2574,16 @@ Web service URL. + + + Name of the root XML element, if POST of XML document chosen. If so, this property must not be null. (see and ). + + + + + (optional) root namespace of the XML document, if POST of XML document chosen. (see and ). + + @@ -2206,8 +2593,22 @@ + + + + + + + + + + + + + + @@ -2304,19 +2705,50 @@ + + + + + + + + List of property names to exclude when is true + + + + + Option to include all properties from the log events + + + + + Indicates whether to include contents of the dictionary. + + + + + Option to render the empty object value {} + + Option to suppress the extra spaces in the output json + + + Indicates whether to include contents of the dictionary. + + + @@ -2325,6 +2757,11 @@ Determines wether or not this attribute will be Json encoded. + + + Indicates whether to escape non-ascii characters + + Layout that will be rendered as the attribute's value. @@ -2365,7 +2802,26 @@ - + + + + + + + + Option to include all properties from the log events + + + + + Indicates whether to include contents of the dictionary. + + + + + Indicates whether to include contents of the dictionary. + + diff --git a/packages/NLog.Web.4.1/NLog.Web.4.1.nupkg b/packages/NLog.Web.4.1/NLog.Web.4.1.nupkg deleted file mode 100644 index 2773eda..0000000 Binary files a/packages/NLog.Web.4.1/NLog.Web.4.1.nupkg and /dev/null differ diff --git a/packages/NLog.Web.4.1/lib/net35/NLog.Web.XML b/packages/NLog.Web.4.1/lib/net35/NLog.Web.XML deleted file mode 100644 index 2752215..0000000 --- a/packages/NLog.Web.4.1/lib/net35/NLog.Web.XML +++ /dev/null @@ -1,411 +0,0 @@ - - - - NLog.Web - - - - - ASP.NET Application variable. - - - Use this layout renderer to insert the value of the specified variable stored - in the ASP.NET Application dictionary. - - - You can set the value of an ASP.NET Application variable by using the following code: - - - - Example usage of ${aspnet-application}: - - ${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" - - - - - - Renders the specified ASP.NET Application variable and appends it to the specified . - - The to append the rendered data to. - Logging event. - - - - Gets or sets the variable name. - - - - - - ASP.NET Item variable. - - - Use this layout renderer to insert the value of the specified variable stored - in the ASP.NET HttpContext.Current.Items dictionary. - - - You can set the value of an ASP.NET Item variable by using the following code: - - - - Example usage of ${aspnet-item}: - - ${aspnet-item:variable=myvariable} - produces "123" - ${aspnet-item:variable=anothervariable} - produces "01/01/2006 00:00:00" - ${aspnet-item:variable=anothervariable:culture=pl-PL} - produces "2006-01-01 00:00:00" - ${aspnet-item:variable=myvariable:padding=5} - produces " 123" - ${aspnet-item:variable=myvariable:padding=-5} - produces "123 " - ${aspnet-item:variable=stringvariable:upperCase=true} - produces "AAA BBB" - - - - - - Renders the specified ASP.NET Item value and appends it to the specified . - - The to append the rendered data to. - Logging event. - - - - Gets or sets the item variable name. - - - - - - Gets or sets whether items with a dot are evaluated as properties or not - - - - - - ASP.NET Request variable. - - - Use this layout renderer to insert the value of the specified parameter of the - ASP.NET Request object. - - - Example usage of ${aspnet-request}: - - ${aspnet-request:item=v} - ${aspnet-request:querystring=v} - ${aspnet-request:form=v} - ${aspnet-request:cookie=v} - ${aspnet-request:serverVariable=v} - - - - - - Renders the specified ASP.NET Request variable and appends it to the specified . - - The to append the rendered data to. - Logging event. - - - - Gets or sets the item name. The QueryString, Form, Cookies, or ServerVariables collection variables having the specified name are rendered. - - - - - - Gets or sets the QueryString variable to be rendered. - - - - - - Gets or sets the form variable to be rendered. - - - - - - Gets or sets the cookie to be rendered. - - - - - - Gets or sets the ServerVariables item to be rendered. - - - - - - ASP.NET Session ID. - - - - - Renders the ASP.NET Session ID appends it to the specified . - - The to append the rendered data to. - Logging event. - - - - ASP.NET Session variable. - - - Use this layout renderer to insert the value of the specified variable stored - in the ASP.NET Session dictionary. - - - You can set the value of an ASP.NET Session variable by using the following code: - - - - Example usage of ${aspnet-session}: - - ${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" - - - - - - Renders the specified ASP.NET Session value and appends it to the specified . - - The to append the rendered data to. - Logging event. - - - - Gets or sets the session variable name. - - - - - - Gets or sets whether variables with a dot are evaluated as properties or not - - - - - - ASP.NET User variable. - - - - - Renders the specified ASP.NET User.Identity.AuthenticationType variable and appends it to the specified . - - The to append the rendered data to. - Logging event. - - - - ASP.NET User variable. - - - - - Renders the specified ASP.NET User.Identity.Name variable and appends it to the specified . - - The to append the rendered data to. - Logging event. - - - - IIS site name - printing - - - - - Append to target - - The to append the rendered data to. - Logging event. - - - - Get value of a property - - key - function to get a value with this key - evaluate as a nested property path. E.g. A.B is property B inside A. - value - - - - ASP.NET HttpModule that enables NLog to hook BeginRequest and EndRequest events easily. - - - - - Initializes the HttpModule. - - - ASP.NET application. - - - - - Disposes the module. - - - - - Event to be raised at the end of each HTTP Request. - - - - - Event to be raised at the beginning of each HTTP Request. - - - - - Writes log messages to the ASP.NET trace. - - Documentation on NLog Wiki - - Log entries can then be viewed by navigating to http://server/path/Trace.axd. - - - - - Writes the specified logging event to the ASP.NET Trace facility. - If the log level is greater than or equal to it uses the - System.Web.TraceContext.Warn method, otherwise it uses - System.Web.TraceContext.Write method. - - The logging event. - - - - Buffers log events for the duration of ASP.NET request and sends them down - to the wrapped target at the end of a request. - - Documentation on NLog Wiki - -

- 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 web.nlog file in your web application directory (this assumes - that PostFilteringWrapper is used to provide the filtering and actual logs go to - a file). -

- -

- 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 Application_OnStart() handler in Global.asax.cs - or some other place that gets executed at the very beginning of your code: -

- -

- Fully working C# project can be found in the Examples/Targets/Configuration API/ASPNetBufferingWrapper - directory along with usage instructions. -

- - - - - Initializes a new instance of the class. - - - - - Initializes a new instance of the class. - - The wrapped target. - - - - Initializes a new instance of the class. - - The wrapped target. - Size of the buffer. - - - - Initializes the target by hooking up the NLogHttpModule BeginRequest and EndRequest events. - - - - - Closes the target by flushing pending events in the buffer (if any). - - - - - Adds the specified log event to the buffer. - - The log event. - - - - Gets or sets the number of log events to be buffered. - - - - - - Gets or sets a value indicating whether buffer should grow as needed. - - A value of true if buffer should grow as needed; otherwise, false. - - Value of true causes the buffer to expand until is hit, - false causes the buffer to never expand and lose the earliest entries in case of overflow. - - - - - - Gets or sets the maximum number of log events that the buffer can keep. - - - - - diff --git a/packages/NLog.Web.4.1/lib/net35/NLog.Web.dll b/packages/NLog.Web.4.1/lib/net35/NLog.Web.dll deleted file mode 100644 index 997b416..0000000 Binary files a/packages/NLog.Web.4.1/lib/net35/NLog.Web.dll and /dev/null differ diff --git a/packages/NLog.Web.4.5.0/NLog.Web.4.5.0.nupkg b/packages/NLog.Web.4.5.0/NLog.Web.4.5.0.nupkg new file mode 100644 index 0000000..96e5cc9 Binary files /dev/null and b/packages/NLog.Web.4.5.0/NLog.Web.4.5.0.nupkg differ diff --git a/packages/NLog.Web.4.5.0/lib/net35/NLog.Web.XML b/packages/NLog.Web.4.5.0/lib/net35/NLog.Web.XML new file mode 100644 index 0000000..cdae6f9 --- /dev/null +++ b/packages/NLog.Web.4.5.0/lib/net35/NLog.Web.XML @@ -0,0 +1,828 @@ + + + + NLog.Web + + + + + Provides the HttpContext associated with the current request. + + + + + HttpContext of the current request. + + + + + Provides access to the HttpContext + + + + + HttpContext associated with the current request + + + + + ASP.NET Application variable. + + + Use this layout renderer to insert the value of the specified variable stored + in the ASP.NET Application dictionary. + + + You can set the value of an ASP.NET Application variable by using the following code: + + + + Example usage of ${aspnet-application}: + + ${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" + + + + + + Gets or sets the variable name. + + + + + + Renders the specified ASP.NET Application variable and appends it to the specified . + + The to append the rendered data to. + Logging event. + + + + ASP.NET Item variable. + + + Use this layout renderer to insert the value of the specified variable stored + in the ASP.NET HttpContext.Current.Items dictionary. + + + You can set the value of an ASP.NET Item variable by using the following code: + + + + Example usage of ${aspnet-item}: + + ${aspnet-item:variable=myvariable} - produces "123" + ${aspnet-item:variable=anothervariable} - produces "01/01/2006 00:00:00" + ${aspnet-item:variable=anothervariable:culture=pl-PL} - produces "2006-01-01 00:00:00" + ${aspnet-item:variable=myvariable:padding=5} - produces " 123" + ${aspnet-item:variable=myvariable:padding=-5} - produces "123 " + ${aspnet-item:variable=stringvariable:upperCase=true} - produces "AAA BBB" + + + + + + Initializes a new instance of the class. + + + + + Gets or sets the item variable name. + + + + + + Gets or sets whether items with a dot are evaluated as properties or not + + + + + + Gets or sets the culture used for rendering. + + + + + + Renders the specified ASP.NET Item value and appends it to the specified . + + The to append the rendered data to. + Logging event. + + + + Base class for ASP.NET layout renderers. + + + + + Initializes the . + + + + + Provides access to the current request HttpContext. + + + + + Validates that the HttpContext is available and delegates append to subclasses.. + + The to append the rendered data to. + Logging event. + + + + Implemented by subclasses to render request information and append it to the specified . + + Won't be called if of is null. + + The to append the rendered data to. + Logging event. + + + + Layout renderers for ASP.NET rendering multiple values. + + + + + Separator between item. Only used for + + + + + Separator between value and key. Only used for + + + + + Single item in array? Only used for + + Mutliple items are always in an array. + + + + + Determines how the output is rendered. Possible Value: FLAT, JSON. Default is FLAT. + + + + + Serialize multiple values + + The values with key and value. + Add to this builder. + + + + Append the value quoted, escape quotes when needed + + + + + + + ASP.NET MVC Controller Name. + + + Use this layout renderer to render the controller name. + + + + ${aspnet-mvc-controller} + + + + + + Renders the specified ASP.NET Application variable and appends it to the specified . + + The to append the rendered data to. + Logging event. + The current http context. + + + + ASP.NET MVC Controller Name. + + + Use this layout renderer to render the controller name. + + + + ${aspnet-mvc-action} + + + + + + Renders the specified ASP.NET Application variable and appends it to the specified . + + The to append the rendered data to. + Logging event. + The current http context. + + + + Base Class for ASP.NET MVC Renderer. + + + + + Renders the specified ASP.NET Application variable and appends it to the specified . + + The to append the rendered data to. + Logging event.s + + + + Renders the specified ASP.NET Application variable and appends it to the specified . + + The to append the rendered data to. + Logging event. + The current http context. + + + + ASP.NET Request variable. + + + Use this layout renderer to insert the value of the specified parameter of the + ASP.NET Request object. + + + Example usage of ${aspnet-request}: + + ${aspnet-request:item=v} + ${aspnet-request:querystring=v} + ${aspnet-request:form=v} + ${aspnet-request:cookie=v} + ${aspnet-request:header=h} + ${aspnet-request:serverVariable=v} + + + + + + Gets or sets the item name. The QueryString, Form, Cookies, or ServerVariables collection variables having the specified name are rendered. + + + + + + Gets or sets the QueryString variable to be rendered. + + + + + + Gets or sets the form variable to be rendered. + + + + + + Gets or sets the cookie to be rendered. + + + + + + Gets or sets the ServerVariables item to be rendered. + + + + + + Gets or sets the Headers item to be rendered. + + + + + + Renders the specified ASP.NET Request variable and appends it to the specified . + + The to append the rendered data to. + Logging event. + + + + Render the request IP for ASP.NET Core + + + + ${aspnet-request-ip} + + + + + + Render IP + + + + + ASP.NET Session ID. + + + + + Renders the ASP.NET Session ID appends it to the specified . + + The to append the rendered data to. + Logging event. + + + + ASP.NET Session variable. + + + Use this layout renderer to insert the value of the specified variable stored + in the ASP.NET Session dictionary. + + + You can set the value of an ASP.NET Session variable by using the following code: + + + + Example usage of ${aspnet-session}: + + ${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" + + + + + + Initializes a new instance of the class. + + + + + Gets or sets the session variable name. + + + + + + Gets or sets whether variables with a dot are evaluated as properties or not + + + + + + Gets or sets the culture used for rendering. + + + + + + Renders the specified ASP.NET Session value and appends it to the specified . + + The to append the rendered data to. + Logging event. + + + + ASP.NET User variable. + + + + + Renders the specified ASP.NET User.Identity.AuthenticationType variable and appends it to the specified . + + The to append the rendered data to. + Logging event. + + + + ASP.NET User variable. + + + + + Renders the specified ASP.NET User.Identity.Name variable and appends it to the specified . + + The to append the rendered data to. + Logging event. + + + + Overwrite the NLog.LayoutRenderers.AssemblyVersionLayoutRenderer + + + + + The (full) name of the assembly. If null, using the entry assembly. + + + + + Implemented by subclasses to render request information and append it to the specified . + + Won't be called if of is null. + + The to append the rendered data to. + Logging event. + + + + Rendering site name in IIS. + + + + + Append to target + + The to append the rendered data to. + Logging event. + + + + ASP.NET Request Referrer + + + Example usage of ${aspnet-request-referrer}: + + ${aspnet-request-referrer} - Produces - Referrer URL String from the Request. + + + + + + Renders the Referrer URL from the HttpRequest . + + The to append the rendered data to. + Logging event. + + + + ASP.NET Request URL + + Example usage of ${aspnet-request-url}: + + + ${aspnet-request-url:IncludeQueryString=true} - produces http://www.exmaple.com/?t=1 + ${aspnet-request-url:IncludeQueryString=false} - produces http://www.exmaple.com/ + ${aspnet-request-url:IncludePort=true} - produces http://www.exmaple.com:80/ + ${aspnet-request-url:IncludePort=false} - produces http://www.exmaple.com/ + ${aspnet-request-url:IncludePort=true:IncludeQueryString=true} - produces http://www.exmaple.com:80/?t=1 + + + + + + To specify whether to include / exclude the Query string. Default is false. + + + + + To specify whether to include /exclude the Port. Default is false. + + + + + To specify whether to exclude / include the host. Default is true. + + + + + Renders the Request URL from the HttpRequest + + The to append the rendered data to. + Logging event. + + + + ASP.NET User Agent + + Example usage of ${aspnet-request-useragent}: + + + ${aspnet-request-useragent} - Produces - User Agent String from the Request. + + + + + + Renders the ASP.NET User Agent + + The to append the rendered data to. + Logging event. + + + + ASP.NET Request Cookie + + Example usage of ${aspnet-request-cookie} + + + ${aspnet-request-cookie:OutputFormat=Flat} + ${aspnet-request-cookie:OutputFormat=Json} + + + + + + List Cookie Key as String to be rendered from Request. + + + + + Renders the ASP.NET Cookie appends it to the specified . + + The to append the rendered data to. + Logging event. + + + + ASP.NET host. + + + Use this layout renderer host. + + + + ${aspnet-host} + + + + + + Renders the specified ASP.NET Application variable and appends it to the specified . + + The to append the rendered data to. + Logging event. + + + + ASP.NET Request Cookie + + Example usage of ${aspnet-request-querystring}: + + + ${aspnet-request-querystring:OutputFormat=Flat} + ${aspnet-request-querystring:OutputFormat=Json} + + + + + + List Query Strings' Key to be rendered from Request. + If empty, then render all querystrings + + + + + Renders the specified ASP.NET Application variable and appends it to the specified . + + + + + + + ASP.NET Http Request Method. + + Example usage of ${aspnet-request-method}: + + + ${aspnet-request-method} - Produces - Post. + + + + + + ASP.NET Http Request Method + + The to append the rendered data to. + Logging event. + + + + Is the user authenticated? 0 = not authenticated, 1 = authenticated + + ${aspnet-user-isAuthenticated} + + + + + Render 0 or 1 + + + + + + + To control the Renderer Output formatting. + + + + + Use this format for rendering the output value as a flat string. + + + + + Use this format for rendering the output value as a json formatted string. + + + + + Get value of a property + + key + function to get a value with this key + evaluate as a nested property path. E.g. A.B is property B inside A. + value + + + + ASP.NET HttpModule that enables NLog to hook BeginRequest and EndRequest events easily. + + + + + Event to be raised at the end of each HTTP Request. + + + + + Event to be raised at the beginning of each HTTP Request. + + + + + Initializes the HttpModule. + + + ASP.NET application. + + + + + Disposes the module. + + + + + Writes log messages to the ASP.NET trace. + + Documentation on NLog Wiki + + Log entries can then be viewed by navigating to http://server/path/Trace.axd. + + + + + Initializes a new instance of the class. + + + The default value of the layout is: + + ${longdate}|${level:uppercase=true}|${logger}|${message} + + + + + + Writes the specified logging event to the ASP.NET Trace facility. + If the log level is greater than or equal to it uses the + System.Web.TraceContext.Warn method, otherwise it uses + System.Web.TraceContext.Write method. + + The logging event. + + + + Buffers log events for the duration of ASP.NET request and sends them down + to the wrapped target at the end of a request. + + Documentation on NLog Wiki + +

+ 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 web.nlog file in your web application directory (this assumes + that PostFilteringWrapper is used to provide the filtering and actual logs go to + a file). +

+ +

+ 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 Application_OnStart() handler in Global.asax.cs + or some other place that gets executed at the very beginning of your code: +

+ +

+ Fully working C# project can be found in the Examples/Targets/Configuration API/ASPNetBufferingWrapper + directory along with usage instructions. +

+ + + + + Initializes a new instance of the class. + + + + + Initializes a new instance of the class. + + The wrapped target. + + + + Initializes a new instance of the class. + + The wrapped target. + Size of the buffer. + + + + Gets or sets the number of log events to be buffered. + + + + + + Gets or sets a value indicating whether buffer should grow as needed. + + A value of true if buffer should grow as needed; otherwise, false. + + Value of true causes the buffer to expand until is hit, + false causes the buffer to never expand and lose the earliest entries in case of overflow. + + + + + + Gets or sets the maximum number of log events that the buffer can keep. + + + + + + Initializes the target by hooking up the NLogHttpModule BeginRequest and EndRequest events. + + + + + Closes the target by flushing pending events in the buffer (if any). + + + + + Adds the specified log event to the buffer. + + The log event. + + + diff --git a/packages/NLog.Web.4.5.0/lib/net35/NLog.Web.dll b/packages/NLog.Web.4.5.0/lib/net35/NLog.Web.dll new file mode 100644 index 0000000..3edbda6 Binary files /dev/null and b/packages/NLog.Web.4.5.0/lib/net35/NLog.Web.dll differ