davidfowl

// Use Gists to store code you would like to remember later on
console.log(window); // log the "window" object to the console

davidfowl

public class Program
{
    public void Main()
    {
        var solution = new Directory
        {
            ["global.json"] = new JObject
            {
                ["projects"] = new JArray { "src", "test" }
            },

davidfowl

In the new ASP.NET 5 stack dependency injection is pervasive. We let users wire up their dependencies in the Startup class:

public class Startup
{
    public void ConfigureServices(IServiceCollection services)
    {
        services.AddTransient<IFoo, Foo>();
    }
    

davidfowl

using System;
using System.Collections.Generic;
using System.Linq;
using System.Threading.Tasks;
using Microsoft.AspNet.Builder;
using Microsoft.AspNet.Http;

namespace WebApplication58
{
    public class MapUseMiddleware

davidfowl

A (project) -> B (package)
     (build)-> CustomCompiler (project) (build)-> FSharpCompiler (project) -> System.Runtime (package)

public interface ILoadContextProvider {
    IAssemblyLoadContext GetLoadContext(Project project, FrameworkName targetFramework);
}

var loadContextProvider = ...

Compile(A)

davidfowl

RID (Runtime idetifier) specific dependencies

As nuget has expanded to support cross platform .NET code, they were features added to allow.

Today NuGet v3 supports a concept of lineup files. These files allow a suite of software to bring in RID specific dependencies. The intent of this feature is to allow package authors to split the API surface from runtime implementations.

Runtime IDs

https://github.com/dotnet/corefx/blob/master/pkg/Microsoft.NETCore.Platforms/runtime.json

runtime.json

davidfowl

Several commands have an --output parameter:

dotnet build

dotnet build --output /myoutputfolder

Output folder

davidfowl

xproj -> csproj redux

1. Adding a project reference will add an entry in the xproj file. There will be no check to see if the TFM for the csproj is compatible.
2. Running dotnet restore or nuget restore in the xproj folder will generate a lock file with project references to the csproj. NuGet walks the msbuild P2P graph in order to achieve this. The lock file will have entries for each of the projects in the graph, but will not have paths to assets. This will happen at compile time by dotnet build. This is because the output path can change based on arbitrary msbuild properties.
3. There an entry for the csproj reference in the project.json file.

{
"dependencies": {

davidfowl

MyApplication

Publish shared runtime

{
    "version": "1.0.0-*",
    "compilationOptions": {
        "emitEntryPoint": true
 },

davidfowl

public class MyAppContainer : ConsoleApp1.Container
{
    public MyAppContainer()
    {
    }

    public MyAppContainer(ConsoleApp1.Container container) : base(container)
    {
    }