Microsoft.Bcl.Build 1.0.14

Helper library for claims-based identity, System.IdentityModel, JSON Web Tokens, OAuth 2.0 and OpenID Connect client

This package includes HttpClient for sending requests over HTTP, as well as HttpRequestMessage and HttpResponseMessage for processing HTTP messages. This package is not supported in Visual Studio 2010, and is only required for projects targeting .NET Framework 4.5, Windows 8, or Windows Phone 8.1 when consuming a library that uses this package. Supported Platforms: - .NET Framework 4 - Windows 8 - Windows Phone 8.1 - Windows Phone Silverlight 7.5 - Silverlight 4 - Portable Class Libraries

This packages enables projects targeting down-level platforms to use some of the types added in later versions including: - CallerMemberNameAttribute - CallerLineNumberAttribute - CallerFilePathAttribute - Tuple<T1, T2, ...> - IProgress<T> - IStructuralComparable - IStructuralEquatable - Task - InvalidDataException These types are "unified" to their later version equivalent. For example, when running on .NET Framework 4.5, IProgress<T> from this package will be seen by the runtime as the same type as the one already available in the platform. Supported Platforms: - .NET Framework 4 (with KB2468871) - Windows 8 - Windows Phone 8.1 - Windows Phone Silverlight 7.5 - Silverlight 4 - Portable Class Libraries This package is only required for projects targeting .NET Framework 4.5, Windows 8, Windows Phone Silverlight 8, or Windows Phone 8.1 when consuming a library that uses this package.

Application Logger utilizing Entity Framework and Enterprise Library

Application Logger utilizing Entity Framework and Enterprise Library

Application Logger utilizing Entity Framework and Enterprise Library

High performance Redis client, incorporating both synchronous and asynchronous usage; the notional successor to BookSleeve

High performance Redis client, incorporating both synchronous and asynchronous usage; the notional successor to BookSleeve

High performance Redis client, incorporating both synchronous and asynchronous usage; the notional successor to BookSleeve. If you prefer a version without a strong-name, try StackExchange.Redis

High performance Redis client, incorporating both synchronous and asynchronous usage; the notional successor to BookSleeve. If you require a strong-named version, try StackExchange.Redis.StrongName

High performance Redis client, incorporating both synchronous and asynchronous usage; the notional successor to BookSleeve. If you prefer a version without a strong-name, try StackExchange.Redis

High performance Redis client, incorporating both synchronous and asynchronous usage; the notional successor to BookSleeve. If you require a strong-named version, try StackExchange.Redis.StrongName

High performance Redis client, incorporating both synchronous and asynchronous usage; the notional successor to BookSleeve. If you prefer a version without a strong-name, try StackExchange.Redis

High performance Redis client, incorporating both synchronous and asynchronous usage; the notional successor to BookSleeve. If you require a strong-named version, try StackExchange.Redis.StrongName

High performance Redis client, incorporating both synchronous and asynchronous usage; the notional successor to BookSleeve. If you require a strong-named version, try StackExchange.Redis.StrongName

High performance Redis client, incorporating both synchronous and asynchronous usage; the notional successor to BookSleeve

High performance Redis client, incorporating both synchronous and asynchronous usage; the notional successor to BookSleeve. If you require a strong-named version, try StackExchange.Redis.StrongName

High performance Redis client, incorporating both synchronous and asynchronous usage; the notional successor to BookSleeve

High performance Redis client, incorporating both synchronous and asynchronous usage; the notional successor to BookSleeve

High performance Redis client, incorporating both synchronous and asynchronous usage; the notional successor to BookSleeve. If you prefer a version without a strong-name, try StackExchange.Redis