Changed all ReSharper annotations to internal (issue 292)
Merge pull request #349 from MichaelLogutov/master

Changed all ReSharper annotations to internal (issue 292)
Fix #71 : Removing invalid filename characters from created file

Adding a CleanUpFileName method to replace characters that are invalid
according to System.IO.Path.GetInvalidFileNameChars()
Changed an existing UnitTest that relied on an exception that would be
thrown when an invalid filename was used.
Obsolete added to LogException() method in Logger class.

In pull request #344 "Replacement for [LogLevel]Exception methods" the
Obsolete attribute was missed for the LogException(LogLevel, String,
Exception) method in Logger class.
Configuration to disable expensive flushing in NLogTraceListener
Remove public constructors from LogLevel

LogLevel class provided a public constructor LogLevel(String, Integer)
but most methods assumed that only certain values were acceptable,
similar to a enumeration.

For this reason the public constructors were hidden removing the
possibility of creating invalid LogLevel instances.

* Public constructors were turned into private.
* CompareTo(Object) method in LogLevel now handles null input.
* Significant number of unit tests added to increase coverage on
LogLevel class.
Added more escape code support for config file. Added option Regex replace parameter which enables replacement by group name from Regex pattern + additional tests.
Fixed issue causing failure of ThreadAgnosticAttributeTest.
Fix bug in ReplaceNamedGroup + added tests.
More testing
Made EndpointAddress virtual
Merge pull request #352 from ie-zero/LogLevelPrivateCtor

Remove public constructors from LogLevel
Merge pull request #351 from ie-zero/ObsoleteLogException

Obsolete added to LogException() method in Logger class.
Merge pull request #353 from robertvazan/remote-log-no-sync

Configuration to disable expensive flushing in NLogTraceListener
Merge pull request #358 from MikeChristensen/master

Made EndpointAddress virtual
Merge branch 'master' into umaster
Fix for #365

Parsing a [null] parameter in for example logger.Info("Testing null:
{0}", null); will result in not logging an event. A
System.NullReferenceException would be thrown causing the entire
logEvent  NOT to be logged. This behavior is different from prior
versions. This fix will restore the previous behavior.
Fixed wrong call site when NLog is called via Common.Logging.
Added test

Added unit test  for fix #365
Altered null check