Skip to content

Conversation

@jafin
Copy link

@jafin jafin commented Jan 21, 2014

Updated references from NLog 2.0 to 2.1

@ferventcoder
Copy link
Owner

This closes #8

@ferventcoder
Copy link
Owner

Thanks, I will try to pull this in this week and update all of the packages...

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did anything change here or was it just nuget doing the same crap, different day in reformatting my .config files?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pretty sure It was just a XML reformat. I probably shouldn't of committed
it, sorry.
On 22 Jan 2014 02:38, "Rob Reynolds" notifications@github.com wrote:

In LoggingExtensions.NLog.Sample/App.config:

   </target>
  •  <target name="errorSmtp" type="Mail"
    
  •       layout="${longdate} ${threadid} [${level:uppercase=true}] ${logger} - ${message}"
    
  •       subject="this.Log Sample Console Errors - LOCAL DEBUG"
    
  •       to="noone@noreply.org"
    
  •       from="this.Log.sample@noreply.org"
    
  •       smtpServer="localhost"
    
  •         />
    
  •  <target name="errorSmtp" type="Mail" layout="${longdate} ${threadid} [${level:uppercase=true}] ${logger} - ${message}" subject="this.Log Sample Console Errors - LOCAL DEBUG" to="noone@noreply.org" from="this.Log.sample@noreply.org" smtpServer="localhost" />
    

Did anything change here or was it just nuget doing the same crap,
different day in reformatting my .config files?


Reply to this email directly or view it on GitHubhttps://github.com//pull/9/files#r9043174
.

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No worries, I can rip it back out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants