113 packages tagged with “output”
The xUnit test output sink for Serilog
Allows you to print out objects in a table view in a console application. Should be helpful for the diehard console fans.
Library for interacting with command-line interfaces
Style your C# console output!
Treats the "output" folder in an dependend nuget package as an additional special folder and copies it's content to the build folder
Framework for enabling time-series data processing services including hosted input, action and output adapter implementations.
Provides services for the data import/export (input/output). Typically used areas and classes/interfaces/services: - DataStreams: IDataStreamReader, IDataStreamWriter. - Export: IDataExportService. - Import: IDataImportService, IDataImportBehavior. Kephas Framework ("stone" in aramaic) aims to deliver a solid infrastructure for applications and application ecosystems.
Basic html output minifier for Razor View Engine. Based on work of https://github.com/meleze/Meleze.Web & https://github.com/Chebur9tina/HtmlOptimizerMvc4
Write colorful messages to the console using simple to use syntax
Make `Microsoft.Extensions.Logging` easier on the eyes!
Prints your POCO collections in the table view in a console. Supports multi-line data, attributes settings, output customization.
Formatted Output Traces
Pixie is a C# library that prints beautifully formatted output to the console. You describe your layout using a high-level API and Pixie turns it into neatly-formatted text.
Package Description
Library to convert a list of values into a "table" (ASCII-styled, markdown, csv)
A cross platform console enhancement library for .NET NetStandard core.
High performance, ultra-low-latency, allocation-free, feature rich and easy to use wrap over System.Console
A very simple logger for .NET programs
Easy and seamless caching implementation of any virtual method in any class.
A collection of core enhancing tools, including Inversion of Control (IoC) container, command line processor, console output renderer, and more.
When you call stored procedure with select and output parameters and you don't select on some conditions (for example, you're just returning an error code) — you get a mapping EntityCommandExecutionException. This package fixes this annoying behavior of EF by returning empty data set and letting you read output parameters. Example: Consider you have this sql procedure: CREATE PROCEDURE [dbo].[Foo] @Condition int = NULL, @ResultCode Int = NULL OUTPUT AS BEGIN IF @Condition IS NULL BEGIN SET @ResultCode = 1; -- return 1 if condition = null RETURN; END SELECT 1 as 'One', 2 as 'Two'; -- select otherwise SET @ResultCode = 0; END Calling this procedure in EF: var resultCodeParameter = new ObjectParameter("ResultCode", typeof(int)); var result = db.Foo(null, resultCodeParameter).FirstOrDefault(); var resultCode = resultCodeParameter.Value; will throw an exception: System.Data.Entity.Core.EntityCommandExecutionException: The data reader is incompatible with the specified 'xxx.Foo_Result'. A member of the type, 'One', does not have a corresponding column in the data reader with the same name. Calling EntityFix.Load() once on your application start will fix this bug.
Pixie is a C# library that prints beautifully formatted output to the console. You describe your layout using a high-level API and Pixie turns it into neatly-formatted text. This package contains Pixie.Loyc, a library that translates Loyc diagnostics to Pixie markup nodes.
A simple way to format table data when printing to the console
Extends standard console providing more features like colored output. Add this package to your core library, so it would get the source code of this module without installing a binary dependency. Then proceed with using corresponding functionality from Atom.Util namespace, like if it was installed using binary assembly. Check out GitHub for more docs and usage examples.
A WPF Canvas which allows easy connecting elements. Each element on the canvas can have zero or multiple in and outputs. These inputs and outputs will snap together.
Library providing functionality to help when creating .NET Console applications.
Output module for Gemini, providing a buffered output tool pane.
NChronicle is an extensible logging and output library allowing centralized management and distribution of log messages to a number of logging destinations (known as 'Libraries'). NChronicle.Core is the core functionality and abstraction layer for all of these Libraries. NChronicle.Core supports multiple levels of logging (Success, Info, Debug, Warning, Error, and Critical) and custom tagging of messages so logs are more findable and manageable. NChronicle allows configuration programmatically or via a live monitored XML configuration file. NChronicle.Console is available as a highly configurable NChronicle Library dispatching log messages to STDOUT / the Console. NChronicle.File is also available as a extensive NChronicle Library writing log message to a file with flexible retention controls. NChronicle.SMTP is a comprehensive SMTP email NChronicle Library sending log messages in customizable email messages. Further Libraries planned for the NChronicle logging framework include NChronicle.EventVwr, NChronicle.API and NChronicle.Owin.
A small debugging helper-class for developers that helps tidying your timing-output.
This library provides extended cache capabilities to the ASP.NET applications. It includes the MongoDB and SQL Server output cache providers extending ASP.NET Output Cache capabilities by allowing to store cached data outside of the application process that is especially important in web-farm scenario. This library provides "Session-On-Demand" functionality - ability to separate ASP.NET Session data to subsets that can be stored outside of the main ASP.NET session and loaded on demand when it's really used rather on every request. This optimizes the out-of-proc ASP.NET session management and increases the overall site performance. These subsets of data can also be stored either in MongoDB and SQL Server. As an additional functionality, the library provides "Cache-On-Demand" that functions as an external out-of-process cache shared by all servers on web-farm. This cached data can be stored either in MongoDB and SQL Server. All functionality is highly configurable and extendable. The FlexiCache 1.1 has ability automatically collect meta data (metatags) for each cached resource or accept custom meta tags. This provides further functionality to remove the cached data by using application meaningful information embedded in the metatags. The removal process is based on application business logic. The Output Cache Provider is able to automatically build meta tags collection from query string and form parameters. The result metatags have the following format: "userid=12345", where UserId was a form or query string parameter that was supplied with the request.