forked from net-commons/common-logging
-
Notifications
You must be signed in to change notification settings - Fork 0
/
changelog.txt
230 lines (147 loc) · 6.92 KB
/
changelog.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
Common.Logging CHANGELOG
=====================================
http://github.com/net-commons/common-logging
http://netcommon.sf.net
Release 3.1.0, March 26, 2015
Summary: New Features and Bug Fix release
New Features
- support for NLog 3.2 added
- LogLevel enum now uses [Flags] attribute to support bitwise || operations when interrogating log levels
Bug Fixes
- ExceptionFormatter.OutputProperties ignores properties of Exception types with indexers (previously resulted in unhandled exception)
---------------------------
Release 3.0.0, January 11, 2015
Summary: New Features and Bug Fix release
New Features
- evolve PCL strategy to introduce Common.Logging.Portable assembly for PCL consumption and migrate only low-level abstractions into Common.Logging.Core PCL assembly
- introduce ILogManager interface in support of new PCL strategy
Bug Fixes
- misc xmldoc references using invalid <param key"..." /> syntax updated to use proper <param name="..." /> syntax for xml API doc generation
---------------------------
Release 2.3.1, November 1, 2014
Summary: Bug Fix release
Bug Fixes
- remove errant readme.txt file from reference in Common.Logging nuspec package definition
---------------------------
Release 2.3.0, November 1, 2014
Summary: New Features and Bug Fix release
New Features
- evolve PCL strategy to introduce new Common.Logging.Portable assembly
- colorized added to ConsoleOutLogger
- support for Log4NET 1.2.12 added
- support for Log4NET 1.2.13 added
- support for EntLib 6.0 added
- support for NLog 2.1 added
- support for NLog 3.0 added
- support for NLog 3.1 added
Bug Fixes
- missing [Serializable] attribute added to EntLibLogger class
---------------------------
Release 2.2.0, March 1 2014
Summary: New Features release
New Features
- Initial support of PCL scenarios (introduce Common.Logging.Core PCL assembly to compliment Common.Logging assembly)
---------------------------
Release 2.1.1, June 9 2012
Summary: New Features and Bug Fix release
Bug Fixes
[Issue 7] revert workaround introduced in 2.1.0 for a bug in ConfigurationManager accessing .config files on network shares under .NET 4;
the workaround introduced in Common.Logging 2.1.0 inadvertently prevents use of Common.Logging under IIS applications. If you have the
usage scenario mentioned in the KB article here http://support.microsoft.com/kb/2580188 you must apply the hotfix for .NET 4 as outlined
in the KB article.
---------------------------
Release 2.1.0, June 8 2012
Summary: New Features and Bug Fix release
IMPORTANT NOTE:
Starting with version 2.1.0, support for .NET versions 2.0 and 3.0 has been deprecated - if you need support
for those platforms please download Common.Logging 2.0. Common.Logging 2.1 now supports .NET 3.5 and .NET 4.
Breaking Changes
*) Beginning with Common.Logging 2.1, there are no longer any "unversioned-named" logging framework assemblies provided.
Instead, the names of all adapter assemblies now include the explicit logging framework version which they target.
As an example, the following assemblies are no longer provided:
* Common.Logging.Log4Net.dll
* Common.Logging.NLog.dll
* Common.Logging.EntLib.dll
In their place, _all_ assemblies now have specific version suffixes as in the following examples:
* Common.Logging.Log4Net1210.dll
* Common.Logging.Log4Net1211.dll
* Common.Logging.NLog10.dll
* Common.Logging.NLog20.dll
* Common.Logging.EntLib41.dll
* Common.Logging.EntLib50.dll
* etc.
The 'suffix' on the assembly name denotes the exact version of the logging framework which each adapter is targeting.
This is intended to assist developers in selecting the proper assembly for the correct version of the logging
framework which they are using. Note however that this means that 'upgrading' from past versions of Common.Logging
may now result in the need to reference an adapter assembly with a (slightly) different filename.
Feature Requests
- Add support for EntLib 5.0 logging
- Add support for Log4Net 1.2.11
- Add explicit compilation targets for .NET 4 binaries
- Automate creating and bundling of NuGet packages to ease release process
Bug Fixes
[Issue 7] workaround for a bug in ConfigurationManager accessing .config files on network shares under .NET 4
---------------------------
Release 2.0.0, April 26 2009
Summary: New Features and Bug Fix release
IMPORTANT NOTE:
starting with version 2.0 we dropped support for .NET versions 1.0 and 1.1. - if you need support
for those platforms please download Common.Logging 1.2
Breaking Changes
*) LogManager.ConfigurationReader is readonly now -> use LogManager.Reset() instead
Feature Requests
[2485203] - Add support for EntLib 4.1 logging
[2512017] - Provide base classes for implementing custom factoryAdapters
[1810787] - Add source code to distribution
[1826632] - Make Common.Logging ClsCompliant
[1970386] - Support for Enterprise Library 4.0
[1852882] - Add optimize flag + PdbOnly in release build
[1847554] - Add TraceListener to capture Diagnostics.Trace calls
[1710163] - Add xxxFormat methods to Common.Logging.ILog interface
[2545123] - Add LogManager.GetCurrentClassLogger()
[1810785] - Clean up code comments
Bug Fixes
[1683776] - Implementations of ILog are not serializable
[1683773] - Add log4net 1.2.9 .dll to distribution for .NET 1.0
[1683772] - Null Pointer Exception when passing in null value for msg
[1683774] - Add unit tests for Common.Logging
[1846258] - ConfigurationSectionHandler not case-insensitive in NET 2.0
---------------------------
Release 1.2.0, October 10 2007
Summary: New Features and Bug Fix release
Feature Requests
[1749338] - Only make .NET 1.0 build since nothing 1.1/2.0 specific
[1749340] - Add support for EntLib logging
[1807769] - Add Trace level method to ILog interface
Bug
[1792900] - NLog logging is not performed relative to correct callsite
Release 1.1.0, July 10 2007
Summary: New Features and Bug Fix release
Feature Requests
[1749332] - Add additonal unit tests
[1715338] - Add error reporting when can't load Factory Adapter
[1749329] - Add support for NLog
Bug
[1718812] - Simple adapters fail to initialize if no arguments are specifed in XML configuration.
---------------------------
Release 1.0.2, March 15 2007
Summary: Bug Fix Release
Bug
[CIL-4] - Implementations of ILog are now serializable
---------------------------
Release 1.0.1, March 1 2007
Summary: Bug Fix Release
Bug
[CIL-1] - Null Pointer Exception when passing in null value for message.
[CIL-2] - Add log4net 1.2.9 .dll to distribution for .NET 1.0
Improvement
[CIL-3] - Add simple NUnit test for Common.Logging
---------------------------
Release 1.0.0, February 27 2007
Summary: Initial Release
Release Notes
Contains support for log4net 1.2.10 and 1.2.9
Bug
Improvement
New Feature
Task