csharptest.net
NuGet publisher profile
Packages (13)
OpenPop.NET
OpenPop.NET is an open source implementation of a POP3 client and a robust MIME parser written in C#. It allows developers easy access to email on a POP3 server in a matter of minutes. The project is backed by several hundred test cases and is therefore believed to be very robust. If you find a bug, please report this by sending an email to [email protected]. POP3 Client Features - Easy to use POP3 client - Support for plain TCP or TLS/SSL connections - Authentication methods supported - - Plain - - APOP - - CRAM-MD5 (RFC 2195) - CAPA capabilities command supported (RFC 2449) MIME Parsing Features - Preserves the MIME email hierarchy - Easy access to different MediaType parts of the email - Headers are parsed into strong types and are easy to examine - Includes robust decoders for - - QuotedPrintable - - Base64 - - EncodedWord - - Continuation and encoding of header fields (RFC 2231) - Emails are fully persistable
Google.ProtocolBuffers
Protocol Buffers is a binary serialization format and technology, released to the open source community by Google in 2008. Its primary use is to produce small fast binary representations of a 'message' or object for serialization or transportation. There are various implementations of Protocol Buffers in .NET. This project is a fairly close port of the Google Java implementation. There are two main parts: tools/protoc.exe, which takes the textual representation of the protocol buffer and turns it into a binary representation for use with ProtoGen.exe. tools/ProtoGen.exe, which takes binary representations of protocol buffer descriptors (as generated by the "stock" protoc binary supplied by Google) and creates C# source code. This is only required at build time. lib/*/Google.ProtocolBuffers.dll, which is a supporting library. This is required at execution time. lib/*/Google.ProtocolBuffers.Serialization.dll, a supplementary library that provides extensions for reading and writing protocol buffers to xml, json, and others. LINKS: Project Home - http://code.google.com/p/protobuf-csharp-port Online Help - http://help.protobuffers.net Developer Guide - http://code.google.com/apis/protocolbuffers/docs/overview.html Language Guide - http://code.google.com/apis/protocolbuffers/docs/proto.html
CSharpTest.Net.Collections
==CSharpTest.Net.Collections== * BPlusTree - a fairly full featured IDictionary backed by a B+Tree on disk. * BTreeDictionary - a fully in-memory IDictionary implemented by a B+Tree. * BTreeList - an in-memory IList using a B+Tree for storage and access. * LurchTable - Least Used Recently Concurrent Hash Table, LinkedHashMap but thread-safe. * MergeSort - Provides a memory-efficient sort for arrays. * OrderedEnumeration & OrderedKeyValuePairs - Ordered enum of large volumes of key-values. * OrdinalList - A simple byte[] based bit-mask collection supporting set operations.
Google.ProtocolBuffersLite
Protocol Buffers is a binary serialization format and technology, released to the open source community by Google in 2008. Its primary use is to produce small fast binary representations of a 'message' or object for serialization or transportation. There are various implementations of Protocol Buffers in .NET. This project is a fairly close port of the Google Java implementation. There are two main parts: tools/protoc.exe, which takes the textual representation of the protocol buffer and turns it into a binary representation for use with ProtoGen.exe. tools/ProtoGen.exe, which takes binary representations of protocol buffer descriptors (as generated by the "stock" protoc binary supplied by Google) and creates C# source code. This is only required at build time. lib/*/Google.ProtocolBuffersLite.dll, which is a supporting library. This is required at execution time. lib/*/Google.ProtocolBuffersLite.Serialization.dll, a supplementary library that provides extensions for reading and writing protocol buffers to xml, json, and others. LINKS: Project Home - http://code.google.com/p/protobuf-csharp-port Online Help - http://help.protobuffers.net Developer Guide - http://code.google.com/apis/protocolbuffers/docs/overview.html Language Guide - http://code.google.com/apis/protocolbuffers/docs/proto.html
CSharpTest.Net.Library
==DEPRECATED== Source moved/split into several repositories/packages: https://www.nuget.org/packages/CSharpTest.Net.Collections/ https://www.nuget.org/packages/CSharpTest.Net.Commands/ https://www.nuget.org/packages/CSharpTest.Net.RpcLibrary/ https://www.nuget.org/packages/CSharpTest.Net.Tools/ Repositories are located under the following account: https://github.com/csharptest
CSharpTest.Net.BPlusTree
==CSharpTest.Net.BPlusTree== This library is a fairly full featured IDictionary<TKey, TValue> implementation backed by a B+Tree on disk. The instance is thread-safe and supports a form of MVCC (Multi Version Concurancy Control) to support non-blocking reads. Great for storing a local cache or use it as a completly local stand-alone database. DEPRECATED: Source moved to: https://github.com/csharptest/CSharpTest.Net.Collections Package moved to: https://www.nuget.org/packages/CSharpTest.Net.Collections
Freshbooks.Library
freshbooks-api provides a single assembly wrapper library around the Freshbooks API. Freshbooks.Library.dll exposes a class 'FreshbooksApi' that ecapsulates the OAuth 1.0a negotiation as well as exposing service interfaces for all the supported entities in the Freshbooks API. For more information please see the project site at http://code.google.com/p/freshbooks-api/
CSharpTest.Net.RpcLibrary
==CSharpTest.Net.RpcLibrary== Simply one of the fastest and most robust inter-process communcations available on the Windows platform. WinRPC is the building block of DCOM and probably the most used remote proceedure call in Windows. In plain words it is the fastest, most stable, secure transport available. Use it for authenticated or anonymous communications over LRPC, named-pipes, or tcp/ip. This assembly provides all the interop nessessary to start a server or client; however, it is a transport only implementation. In other words, it provides no more than moving a byte[] back and forth with the remote endpoint. A protocol is usually layered on top of this to turn raw bytes into meaningful messages.
CSharpTest.Net.Tools
==CSharpTest.Net.Tools== CmdTool.exe - provides a Visual Studio code generation integration to any command-line application. see also http://help.csharptest.net/?CmdToolOverview.html CSharpTest.Net.Generators.exe - provides a command-line replacement for ResX code generation with support for message files (.mc) and rich exception classes. see also http://help.csharptest.net/?CSharpTest.Net.GeneratorsOverview.html StampCopyright.exe - provides a means to ensure all source code is automagically stamped with a copyright message header. see also http://help.csharptest.net/?StampCopyrightOverview.html StampVersion.exe - provides the ability to scan for and replace versions in AssemblyInfo.cs files. see also http://help.csharptest.net/?StampVersionOverview.html AssemblyFileProcessor.exe - provides the ability to replace assembly attribute values in AssemblyInfo.cs files.
CSharpTest.Net.Commands
Provides an easy to use means of exposing a set of public class methods as a console program. Parses and converts the arguments to the appropriate types and invokes the method. Can run as a full interpreter with support for piping IO between commands. Built in help command for your class methods as well as exporting full help to html.
Google.ProtocolBuffers.Rpc
Google.ProtocolBuffers.Rpc uses the Win32 RPC Interop library, CSharpTest.Net.RpcLibrary, as a primary transport for Protobuffer services. Extremely fast, secure, extensible, and reliable.
Google.ProtocolBuffersLite.Rpc
Google.ProtocolBuffersLite.Rpc uses the Win32 RPC Interop library, CSharpTest.Net.RpcLibrary, as a primary transport for Protobuffer services. Extremely fast, secure, extensible, and reliable. This version depends on Google.ProtocolBuffersLite version (optimize_for = LITE_RUNTIME).
CSharpTest.Net.Logging
==CSharpTest.Net.Logging== A simple and fast logging that is as easy to use as calling "Log.Error(x)". Just add a reference and go, there is no required configuration necessary, and no namespace to include or object to create. Provides events that can be used to write to other log apis or destinations.