Comments (5)
@304NotModified do you think it would be a good idea to publish custom target XSD schemas, via PRs, under the schemas folder of your NLog site repo so that they will all have the url http://nlog-project.org/schemas/*.xsd
?
from nlog.targets.syslog.
Yes I like that idea!
Think we need to add the version also in the URL/filename?
from nlog.targets.syslog.
It would be useful if we used different versions for the schema and the target NuGet, but usually, as NLog and the Syslog target do, the schema NuGet version is updated to match the related software NuGet version, even if there are no changes.
This would require creating a lot of PR to your NLog site repo @304NotModified, therefore I suggest not appending the version to XSD files published in your schemas folder.
from nlog.targets.syslog.
I think users should use
<nlog xmlns="http://nlog-project.org/schemas/NLog.Targets.Syslog.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
Am I correct? Maybe we should update the example on readme
from nlog.targets.syslog.
This should be the correct set of XMLNSs:
<nlog xmlns="http://www.nlog-project.org/schemas/NLog.xsd"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:sl="http://www.nlog-project.org/schemas/NLog.Targets.Syslog.xsd">
from nlog.targets.syslog.
Related Issues (20)
- Name of wrapped target has "_wrapped" suffix HOT 3
- Infinite retries and potential log entries lost upon delivery failure HOT 2
- Delivery issues result in infinite retries HOT 1
- Delivery issues can result in lost log entries HOT 4
- UnobservedTaskException thrown on configuration reload HOT 3
- Superfluous catch of OperationCanceledException
- Support for .NET Framework not needed
- Multiple build services are used
- How to get started is missing HOT 1
- Extensions section missing in sample configuration HOT 1
- NLog version in README is wrong
- Build badges in README are not relevant
- NuGet publication fails with Powershell error
- NuGet publication unable to find packages
- Is the target compatible with the new NLog extension configuration? HOT 32
- Improper dependency handling with .NET Framework application HOT 5
- structured logging - Escaping special characters for ${all-event-properties} layout renderer HOT 1
- Syslog logging just randomly stops HOT 4
- Add support for TLS (TLS server certificate validation)
- Truncation not Working HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from nlog.targets.syslog.