Found 42 packages
Provides classes that allow a compiler or tool to emit metadata and optionally generate a PE file on disk. The primary clients of these classes are script engines and compilers. Commonly Used Types: System.Reflection.Emit.AssemblyBuilder System.Reflection.Emit.FieldBuilder System.Reflection.Emit.TypeBuilder System.Reflection.Emit.MethodBuilder System.Reflection.Emit.ConstructorBuilder System.Reflection.Emit.GenericTypeParameterBuilder System.Reflection.Emit.ModuleBuilder System.Reflection.Emit.PropertyBuilder System.Reflection.Emit.AssemblyBuilderAccess System.Reflection.Emit.EventBuilder When using NuGet 3.x this package requires at least version 3.4.
Provides the System.IO.FileSystemWather class, which listens to the file system change notifications and raises events when a directory, or a file in a directory, changes. Commonly Used Types: System.IO.FileSystemWatcher System.IO.WatcherChangeTypes System.IO.FileSystemEventArgs System.IO.RenamedEventArgs System.IO.FileSystemEventHandler System.IO.RenamedEventHandler System.IO.NotifyFilters System.IO.ErrorEventArgs System.IO.ErrorEventHandler System.IO.WaitForChangedResult When using NuGet 3.x this package requires at least version 3.4.
Library for parsing SEL (Schweitzer Engineering Laboratories) event files
The Semantic Logging Application Block provides a set of destinations (sinks) to persist application events published using a subclass of the EventSource class from the System.Diagnostics.Tracing namespace. Sinks include Azure table storage, SQL Server databases, file, console and rolling files with several formats and you can extend the block by creating your own custom formatters and sinks. The console sink is part of this nuget package. Other Sinks mentioned above are available as separate nuget packages. For the sinks that can store structured data, the block preserves the full structure of the event payload in order to facilitate analysing or processing the logged data. An out-of-proc Windows Service is available as a separate NuGet package (EnterpriseLibrary.SemanticLogging.Service).
.NET Core event sourcing framework
The easiest logging library to use to send log messages to syslog, the console, or the file system. It's. REALLY. Easy.
Reliable, real-time file system monitoring with an intuitive API that developers everywhere love.
Topshelf.FileSystemWatcher wraps the .NET FileSystemWatcher class behind a configurator, to make it possible to easily listen for FileSystem change events whithin your Topshelf Service.
A wrapper of FileSystemWatcher to standardize the events and avoid false change notifications, used in ImageGlass project (https://imageglass.org). This project is based on the VSCode FileWatcher: https://github.com/Microsoft/vscode-filewatcher-windows.
FileSystem based EventStore Implementation for testing purpose only!
This is a simple multithread WebServer supporting simple controller and event based calls. Perfect for .NET nanoFramework REST API based project. Support all type of Http Methods. Perfect for simple embedded web pages, with Support of file on a storage (USB, SD Card, in Memory). Supports both HTTPS and HTTP. Use this version if you want to serve local files and have support for System.IO.FileSystem on your device. Otherwise use 'nanoFramework.WebServer' nuget.
The Semantic Logging Application Block provides a set of destinations (sinks) to persist application events published using a subclass of the EventSource class from the System.Diagnostics.Tracing namespace. Sinks include Azure table storage, SQL Server databases, file, console and rolling files with several formats and you can extend the block by creating your own custom formatters and sinks. The console sink is part of this nuget package. Other Sinks mentioned above are available as separate nuget packages. For the sinks that can store structured data, the block preserves the full structure of the event payload in order to facilitate analysing or processing the logged data. This library contains a class library that targets .Net Core 2.0 & .Net Standard 2.0.
AdvancedFileSystemWatcher try to resolve FileSystemWatcher changed event from raising multiple times by adding detailed information(BeginWrite/EndWrite) in Changed handler. Example: void watcher_Changed(object sender, SoftMade.FileSystemEventArgs e) { if (e.ChangeType == SoftMade.WatcherChangeTypes.BeginWrite) { //do what you want when file is begin writed } else if (e.ChangeType == SoftMade.WatcherChangeTypes.EndWrite) { //do what you want when file is writed } }
Implements a very simple unoptimized store for the file system.
Configuration settings for some common .NET Framework System.Diagnostics trace listeners and sources, including console, rolling file, Windows event log and XML listeners (for viewing using the Service Trace Viewer). This configuration file is maintained as part of the Essential.Diagnostics project that provides guidance and examples on using System.Diagnostics, as well as additional listeners and extensions. See the Essential.Diagnostics project site on CodePlex for additional examples and documentation.
xUnit tests for netfx-Patterns.EventSourcing.SampleFileSystem
Created a new nuGetPackage for Event Log for logging events to Event Viewer and error Log/send email on exception dll. 1) Creates and saves event Log. 2) Sends email on errors. Sample event log: Event log can be written to Windows Event viewer or can also be saved to a text file [managed through settings in config file] ErrorLogHelper.WriteErrorLog("Window service Init"); Sample Error Log during exception: ErrorLogHelper.LogErrorandSendMail("Sample error, also pass the exception that occured", ex) This above exception can be written to an event log and also send an email by implementing below ErrorLogHelper.WriteErrorLog(ErrorLogHelper.LogErrorandSendMail("Window service failed to Initialize", ex), System.Diagnostics.EventLogEntryType.Error); Following are the config settings that need to be set that are specific for the app: Default implementation is to write it to a text file, but it can write to an event log and send an email by changing the following ConfigurationManager.AppSettings["LogEvent"] ConfigurationManager.AppSettings["SendErrorEmail"] Event Viewer Name = ConfigurationManager.AppSettings["EventViewerName"] text file file path ConfigurationManager.AppSettings["LogFilePath"] Email From and Display Name ConfigurationManager.AppSettings["EmailDisplayName"].ToString(), ConfigurationManager.AppSettings["EmailAddressFrom"] Email Subject: ConfigurationManager.AppSettings["EmailSubject"] Email To: ConfigurationManager.AppSettings["EmailAddress"]
Rolling file version of the XML trace listener extension for System.Diagnostics, along with required config sections. Writes E2ETraceEvent XML fragments to a text file, rolling to a new file based on a filename template (usually including the date). The E2ETraceEvent XML fragment format can be read by the Service Trace Viewer tool. Other Essential.Diagnostics packages extend the .NET Framework System.Diagnostics trace logging with additional trace listeners. Included are colored console (that allows custom formats), SQL database (including a tool to create tables), rolling file (with custom formats), rolling XML, email (per trace or batched), and an in-memory trace listener. The Essential.Diagnostics project also publishes a fluent client library that includes easy encapsulation of activity and logical operation scopes, as well as abstractions and templated classes for a simpler logging API and support for dependency injection frameworks. See the project site on CodePlex for examples and documentation.
A flexible event-driven pipeline for file system changes