background preloader

NuGet Gallery

NuGet Gallery

Inside F# Installing NuGet Visual Studio 2010, 2012 and 2013 For Visual Studio 2010, NuGet is available through the Visual Studio Extension Manager. The extension can be installed into the Professional, Premium, and Ultimate editions. Additionally, the extension can be installed into Visual Web Developer 2010 Express Starting with Visual Studio 2012, NuGet is included in every edition (except Team Foundation Server) by default. To check if your copy of Visual Studio already has the NuGet extension, look for Library Package Manager in the Tools menu of Visual Studio. To download the extension for Visual Studio 2010 and 2012 directly, it can be found on the Visual Studio Extension Gallery and for Visual Studio 2013 directly, it can be found here on the Visual Studio Extension Gallery. Command-Line Utility A command-line NuGet utility is also available. The latest version of the nuget.exe command-line tool is always available from our dist share. In Visual Studio, click Tools and then Extension Manager.

Symbol and Operator Reference (F#) This topic includes a table of symbols and operators that are used in the F# language. The following table describes symbols used in the F# language, provides links to topics that provide more information, and provides a brief description of some of the uses of the symbol. Symbols are ordered according to the ASCII character set ordering. The following table shows the order of precedence of operators and other expression keywords in the F# language, in order from lowest precedence to the highest precedence. Also listed is the associativity, if applicable. F# supports custom operator overloading. Reference Other Resources

Packages Json.NET 109,463,698 total downloads last updated a month ago Latest version: 11.0.1 json Json.NET is a popular high-performance JSON framework for .NET 18,787,141 total downloads last updated 6 days ago Latest version: 3.10.1 nunit test testing tdd framework fluent assert theory plugin addin NUnit features a fluent assert syntax, parameterized, generic and theory tests and is user-extensible. This package includes the NUnit 3 framework assembly, which is referenced by your tests. Bootstrap CSS 15,946,860 total downloads last updated 2 months ago Latest version: 4.0.0 css mobile-first responsive front-end framework web The most popular front-end framework for developing responsive, mobile first projects on the web. 45,689,927 total downloads last updated 2 months ago Latest version: 3.3.1 jQuery 6,770,027 total downloads last updated 15 days ago Latest version: 1.7.1 HTML parse crawler spider linq Microsoft ASP.NET MVC Selenium WebDriver Apache log4net

A Sample of the Memoization Pattern in F# - Don Syme's WebLog on F# and Related Topics - Site Home - MSDN Blogs Pieter Breed has been asking some useful questions on the F# list recently about using the "Map" type. I really appreciate it when people take the time to let us know when data structures are tricky to learn to use in F#. Looking at Pieter's blog made me think it might be instructive to show how the memoization pattern looks in F# (or at least one example of the pattern). #light open System open System.Text open System.Collections.Generic // Save computed results by using an internal dictionary.// Note that memoize is inferred to have type// memoize: ('a -> 'b) -> ('a -> 'b) let memoize f = let cache = Dictionary<_, _>() fun x -> if cache.ContainsKey(x) then cache. else let res = f x cache. res // An example, taken from Pieter's blog let memoizedAppend = memoize (fun input -> printfn "Working out the value for '%A'" input String.concat ", " [ for i in 0 .. 9 -> sprintf "%d: %s" i input ]) And using this in F# Interactive: Some things to note here: Update: Here's the single-lookup version of this: match (!

NuGet Docs F# Workshop docs.nuget NuGet is the package manager for the Microsoft development platform including .NET. The NuGet client tools provide the ability to produce and consume packages. The NuGet Gallery is the central package repository used by all package authors and consumers. Beginning with NuGet 3.0, a new model and interaction with project systems was introduced that uses the Project.Json package definition standard inside of new ASP.NET 5 and UWP projects. New capabilities are available for these project types that work with project.json packaging NuGet runs in all versions and SKUs of Visual Studio 2010, Visual Studio 2012, Visual Studio 2013, and Visual Studio 2015. Many developers like to omit binaries from their source control repository and NuGet Package Restore helps you with that. NuGet's configuration file allows for persisting configuration settings and changing default configuration values. Learn more about what NuGet can do for you.

Command Line Reference Installing The NuGet command line may be installed onto a machine in a few possible ways. Direct download of the executable from The executable may be placed anywhere on the file system, and in most cases should be placed in a directory that is listed in the PATH environment variable.Install the NuGet.CommandLine package from the NuGet Visual Studio client and either move nuget.exe to a common location or execute it in the context of your project.Install the NuGet.CommandLine Chocolatey package using the Chocolatey client. More information on Chocolatey can be found at [ Install Command Installs a package using the specified sources. Install Command Usage nuget install packageId|pathToPackagesConfig [options] Specify the id and optionally the version of the package to install. Install Command Options Install Command Examples nuget install elmah nuget install packages.config nuget install ninject -o c:\foo Update Command Update Command Usage

NuGet Config Defaults Overview Many companies are using NuGet internally, but have had a hard time setting up a build server or guiding their developers to use internal package sources instead of In addition to the standard NuGet Configuration File, NuGet 2.7 introduces a Configuration Defaults feature that allows machine-wide defaults to be specified for: Enabled package sourcesRegistered, but disabled-by-default package sourcesThe default nuget.exe push source Each of these can now be configured within a file located at %ProgramData%\NuGet\NuGetDefaults.config. While not required, we expect many companies to use Group Policy to deploy NuGetDefaults.config files to developers' machines. NoteThis feature will never cause a package source to be removed from a developer's NuGet configuration. NuGet Config Defaults File NuGet Config Defaults file, NuGetDefaults.config, is located under %ProgramData%\NuGet folder, which is machine-wide and typically requires Administrator permissions to modify.

NuGet Config File NuGet's configuration file allows for persisting configuration settings and changing default configuration values. Default Location The default location for NuGet's configuration file is %APPDATA%\NuGet\NuGet.Config (DOS) or $ENV:APPDATA\NuGet\NuGet.Config (PowerShell). The default configuration file can be changed through -ConfigFile option. Config file reference XML is used to store the configuration, and any text editor can be used to author it. NoteNuGet will silently ignore the entire configuration file if it encounters any XML parsing issues (such as mismatched begin/end nodes, invalid quotation, etc.); therefore an editor that reports parsing issues is recommended. NoteThe keys are case sensitive. Below an example of NuGet configuration file that specifies some of the available settings and is annotated with comments. Chaining multiple configuration files Current directory is defined as: The following rules are used to determine the actual configuration values: NuGet will load: