System.Linq 4.0.0-beta-22416

Abstractions for reading `.deps` files.

Provides a class to dynamcially create proxy types that implement a specified interface and derive from a specified DispatchProxy type. Method invocations on the generated proxyinstance are dispatched to that DispatchProxy base type. Commonly Used Types: System.Reflection.DispatchProxy

High performance Redis client, incorporating both synchronous and asynchronous usage.

This package provides collections that are thread safe and guaranteed to never change their contents, also known as immutable collections. Like strings, any methods that perform modifications will not change the existing instance but instead return a new instance. For efficiency reasons, the implementation uses a sharing mechanism to ensure that newly created instances share as much data as possible with the previous instance while ensuring that operations have a predictable time complexity. Commonly Used Types: System.Collections.Immutable.ImmutableArray System.Collections.Immutable.ImmutableArray<T> System.Collections.Immutable.ImmutableDictionary System.Collections.Immutable.ImmutableDictionary<TKey,TValue> System.Collections.Immutable.ImmutableHashSet System.Collections.Immutable.ImmutableHashSet<T> System.Collections.Immutable.ImmutableList System.Collections.Immutable.ImmutableList<T> System.Collections.Immutable.ImmutableQueue System.Collections.Immutable.ImmutableQueue<T> System.Collections.Immutable.ImmutableSortedDictionary System.Collections.Immutable.ImmutableSortedDictionary<TKey,TValue> System.Collections.Immutable.ImmutableSortedSet System.Collections.Immutable.ImmutableSortedSet<T> System.Collections.Immutable.ImmutableStack System.Collections.Immutable.ImmutableStack<T>

This package provides collections that are thread safe and guaranteed to never change their contents, also known as immutable collections. Like strings, any methods that perform modifications will not change the existing instance but instead return a new instance. For efficiency reasons, the implementation uses a sharing mechanism to ensure that newly created instances share as much data as possible with the previous instance while ensuring that operations have a predictable time complexity. Commonly Used Types: System.Collections.Immutable.ImmutableArray System.Collections.Immutable.ImmutableArray<T> System.Collections.Immutable.ImmutableDictionary System.Collections.Immutable.ImmutableDictionary<TKey,TValue> System.Collections.Immutable.ImmutableHashSet System.Collections.Immutable.ImmutableHashSet<T> System.Collections.Immutable.ImmutableList System.Collections.Immutable.ImmutableList<T> System.Collections.Immutable.ImmutableQueue System.Collections.Immutable.ImmutableQueue<T> System.Collections.Immutable.ImmutableSortedDictionary System.Collections.Immutable.ImmutableSortedDictionary<TKey,TValue> System.Collections.Immutable.ImmutableSortedSet System.Collections.Immutable.ImmutableSortedSet<T> System.Collections.Immutable.ImmutableStack System.Collections.Immutable.ImmutableStack<T> - 1548494

NuGet's implementation of Semantic Versioning.

Provides a class to dynamically create proxy types that implement a specified interface and derive from a specified DispatchProxy type. Method invocations on the generated proxyinstance are dispatched to that DispatchProxy base type. Commonly Used Types: System.Reflection.DispatchProxy When using NuGet 3.x this package requires at least version 3.4.

An admin dashboard for Microsoft Orleans

Azure Key Vault enables users to store and use cryptographic keys within the Microsoft Azure environment. Azure Key Vault supports multiple key types and algorithms and enables the use of Hardware Security Modules (HSM) for high value customer keys. In addition, Azure Key Vault allows users to securely store secrets in a Key Vault; secrets are limited size octet objects and Azure Key Vault applies no specific semantics to these objects. A Key Vault may contain a mix of keys and secrets at the same time, and access control for the two types of object is independently controlled. Users, subject to appropriate authorization, may: 1) Manage cryptographic keys using Create, Import, Update, Delete and other operations 2) Manage secrets using Get, Set, Delete and other operations 3) Use cryptographic keys with Sign/Verify, WrapKey/UnwrapKey and Encrypt/Decrypt operations. Operations against Key Vaults are authenticated and authorized using Azure Active Directory.