ASP.NET 5->.NET Execution Environment (DNX)->Create a New NuGet Package with DNX

• Create a new DNX project for your package (link to DNX projects article)
  • Various project.json properties map to package metadata: authors, description, version, etc
  • Package id will match the DNX project name (folder name by default, no way to change it yet)
  • Version can have -*. Set DNX_BUILD_VERSION env var on your build server to specify the replacement for the version wildcard.
  • Pointer to DNX commands article for creating command packages
• Targeting multiple frameworks
  • Each framework under frameworks maps to a folder under lib in your package that gets built for you by DNX automatically
  • Target framework specific dependencies are handled for you
  • Specify set of frameworks that you can target (.NET 2.0?, PCLs? Silverlight? etc)
• Building your package
  • dnu pack will do a build and create your package and symbol package
  • Dependencies/frameworkAssemblies will automatically get handled
  • Limitations:
    • One assembly per package
    • Can't add additional files yet (see aspnet/dnx#2561 (comment))
• Publishing your package
  • Upload to your favorite package feed (nuget.org, myget.org, internal company feed, etc)
  • Note: Uploading to nuget.org requires you to have a description . . .

ASP.NET 5->Runtime->Application Startup

• Accessing and using available runtime services during Startup
• Startup class conventions and discovery
  • Assembly determined by config (Hosting:Application), otherwise application name
  • Class named Startup in any namespace
  • Can be static (but then you get no DI)
• ConfigureServices
  • Link to DI (#65)
  • Can return IServiceProvider for wiring up 3rd party IoC (reference DI topic)
  • Analogous to app.UseServices(services => { services.AddMvc(); ... })
• Configure
  • Must be public and return void
  • Used to construct a middleware pipeline using IApplicationBuilder
    • Link to Middleware (#109) topic
• Link to Environments content with

ASP.NET 5->.NET Execution Environment (DNX)->Creating a Cross-Platform Console App with DNX

• Create a Console Application (Package)
• Building and publishing your cross-platform console app
• Running your cross-platform app

Noel's booked until later in April when he expects to write this article.

ASP.NET 5->.NET Execution Environment (DNX)->Using Commands

• What is a command?
• Using commands in your project
  • Examples: web, kestrel, test, ef?
• Running commands using dnx.exe
  • dnx [command]
  • dnx run
• Global commands
  • Installing
    • Done by package ID
    • Note: only global NuGet.Config is used
    • Option to override (--overwrite)
  • Running
    • Always run with the active DNX
  • Uninstalling
    • Done by command name
  • Built-in global commands (user-secrets, sqlservercache)
• Building and publishing global commands
  • Create a new DNX Console app (ref existing article)
  • Define a command in commands section
  • Build as a package (dnu pack or option in VS)
  • Publish to your feed

ASP.NET 5->.NET Execution Environment->Working with DNX Projects

• Creating a new project
• Targeting multiple frameworks
• Adding dependencies
• Restoring packages
• Project lock file
• Referencing other projects
• Adding package metadata

Expect some churn in this area after beta4.

http://www.asp.net/mvc/overview/getting-started/introduction/getting-started

Need to research IdentiySample.Mvc. Also, hoping the revised project template will include feature parity with the MVC 5 project template, in terms of managing user information (forgot password, etc.)

Details on new project template auth: https://github.com/aspnet/Templates/tree/release/src/Rules/StarterWeb

ASP.NET 5->Runtime->Working with Static Files

• Servicing static files
  • Use the static file middleware (package: Microsoft.AspNet.StaticFiles)
  • Web root defined in project.json
  • Populate with your static files
  • Link to how to setup with bower (http://docs.asp.net/en/latest/client-side/bower.html)
• Directory browsing
• Default files
  • URL rewrite to point to default files (ex index.html) if they exist
  • Generally used in conjunction with static file middleware
• File Server = Static files + directory browsing + default files
• Common options
  • Custom IFileProvider (ex service files from location other than web root or from embedded assembly resources)
  • "Request path" specifies a common prefix in the URL to handle
• General notes
  • Generally configure early in pipeline - everything falls through if the file/dir doesn't exist

port my DI doc from HTML to reStructuredText

• Migrating HttpConfiguration logic to the MvcOptions pattern
• Migrating message handlers to middleware
• Migrating formatters to the new formatter model
• Using the Microsoft.AspNet.Mvc.WebApiCompatShim package if you are porting a lot of Web API 2 code and you want to use the Web API 2 patterns (method overloading, HTTP verb convention based on method name, HttpRequestMessage/HttpResponseMessage programming model, etc.). #1811

Getting Started->Conceptual Overview->Basics of Web Development

• HTML
• JavaScript
• CSS

Getting Started->Installation->Installing on Mac

ASP.NET 5->.NET Execution Environment->Project.json reference

On hold until SignalR is updated for ASP.NET 5.

http://www.asp.net/mvc/overview/getting-started/introduction/getting-started

Getting Started->Installation->Installing on Linux

Configuration is a big topic. In a common web app on old ASP.NET we'd have roughly the following stuff in web.config:

• appSettings with simple key-value settings of the app and libs
• standard sections from .NET like system.diagnostics
• settings for asp.net - system.web
• settings for web server - system.webServer
• custom sections - sections of 3rd party registered in configSections element (please pay attention that these libs can be not related with asp.net at all, just some libs)

The article only talks about the first one - appSettings. Yeah, they are easily converted to anything as it's just key-value pair.
But what to do with the others?

The most unclear thing for me is custom sections. Just imagine you used some library. And that library supports configuration - it uses ConfigurationManager which just uses "system configuration file". And now it's empty. We could say something like "do not expect the lib to configure itself from configuration file, configure it on your own via its api". It makes sense indeed. But it breaks my app. It breaks any app. Moreover the lib could not support the same abilities via Api as via config.

I'm not sure that here is a good place to discus the design "deprecating System.Configuration". But anyway consequences of that design should be clearly stated in the docs.
Thanks.

Getting Started -> Tutorials -> Building Music Store

Getting Started->Conceptual Overview->The .NET Execution Environment (DNX)

• What is the .NET Execution Environment (DNX)?
• Why build DNX?
• Projects
• Dependencies
• Packages and feeds
• Commands
• Application Host
• Meta programming
• Dependency injection
• Publishing
• DNX Version Manager

Getting Started->Conceptual Overview->Introduction to ASP.NET 5

• What is ASP.NET 5?
• Why build ASP.NET 5?
• Modern Web apps in the Cloud
• Application lifecycle
• Middleware
• Configuration
• Dependency injection
• Options
• Hosting
• Servers
• Web root
• Client-side development

ASP.NET 5->Fundamentals->Servers

• Servers accept incoming requests and make them available to the application pipeline
• Built-in servers (list request features and configuration parameters supported, process model, .NET flavor and OS support)
  • IIS
  • WebListener
  • Kestrel
• Guidance on when to use which server
  • Prefer Windows optimized servers (IIS, WebListener) on Windows.
  • Use IIS for general web hosting and WebListener for custom hosting in your own process or service.
  • Use Kestrel for non-Windows environments
• Server specific programmatic configuration using IApplicationBuilder.Server
  • Downcast and configure
• Custom
  • Implement IServerFactory
  • Create a feature collection per request and invoke the provided application delegate
    • Mandatory features: IHttpRequestFeature and IHttpResponseFeature
    • All other features are optional
  • See #58 for details on how to use a custom server with ASP.NET Hosting

Getting Started->Installation->Installing on Windows

• Areas
• Global Filters
• DI
• Attribute routing

Getting Started -> Tutorials -> Your First ASP.NET 5 Application on a Mac

• Dev setup
• Scaffold app using Yeoman
• Run locally using Kestrel
• Publish to Azure (Kudu? Linux VM? Docker?)

ASP.NET 5->Runtime->Hosting

• Setting up a server environment
• Multi-tenant hosting
• Servicing
• Directory Structure
• Http PlatformHandler
• Isolation by AppPools
• Data Protection
• Hosting off UNC shares
• Log redirection

• Grunt and Gulp Task Runners
• Bower Package Manager
• Bootstrap Responsive Web Framework
• LESS, SASS, Font Awesome,
• TypeScript
• Knockout.js
• Backbone.js
• Angular.js
• React.js

I am ready to translate to pt_BR.

Where are the rules for translation?
It would be nice to have it in the project wiki.

ASP.NET 5->.NET Execution Environment->Global.json Reference

To let people not familiar with sphinx build these docs, add that python 2, pip, sphinx and the "sphinx_rtd_theme" module must be installed to the README. The theme is installed like so:

sudo pip install sphinx_rtd_theme

ASP.NET 5->.NET Execution Environment (DNX)->Migrating an Existing NuGet Pacakge to Support .NET Core

• Why use DNX to build your NuGet packages?
• Cross-compilation
• Adding support for .NET Core
• Building portable libraries