Update ci build for ubuntu (dotnet#891)

* update self-contained builds to build on ubuntu

We use that runtime on the CI build server.

* whitespace change to force a build

* whitespace changes.

* update for CI Build

* Ready for a CI build test.

* Move LINQ samples.

* update references to LINQ samples.

* move the getting started with Core on Mac OS tutorial

* move the console-linq sample and references.

* move the console teleprompter sample

* move the console webapiclient sample.

* move the weather microservice sample.

* move the delegates-and-events sample.

* move the event samples.

* move the expression trees sample.

* mv the indexers samples.

* move the iterators sample

* move the unit testing sample.

* mv the console apps core sample

* update console-apps links

* move the migration samples.

* move new-library back under core.

And fix links

* Update contributing to match sample locations

Author: BillWagner

.gitignore

@@ -205,8 +205,8 @@ samples/AngularSample/src/AngularSample/wwwroot/lib
 project.lock.json
 samples/WebApplication1/src/WebApplication1/wwwroot/lib/
 
-/samples/linq/csharp/aggregate/*.xproj
-/samples/linq/csharp/aggregate/*.sln
+/samples/core/linq/csharp/aggregate/*.xproj
+/samples/core/linq/csharp/aggregate/*.sln
 
 _site/
 api_ref/

CONTRIBUTING.md

@@ -110,25 +110,21 @@ All samples should be complete applications or libraries. Where the sample creat
 it should include unit tests or an application that lets readers run the code.
 
 The samples are organized in directories that match the directories under
-docs in this repo:
+docs in this repo.
 
-- `getting-started` contains getting started samples. 
+- `core` contains .NET Core samples. These are referenced by topics under `/docs/core`.
 
-   * Each top-level section of our documentation contains a "getting-started" or "tutorials" section.  These topics and their associated samples represent the first look(s) at a topic area. If your sample's goal is to help beginners get started with the platform or the technology, place your sample under `samples/getting-started`. There should be a directory that matches the section for your tutorial (such as `samples/getting-started/csharp`), but if not, simply create a new folder.
+   * The `core` directory contains samples that highlight .NET Core. The purpose of your sample should be to teach developers something about .NET Core. This includes the framework packaging, the new tooling, or the cross-platform experience. Our CI buid server builds these samples on multiple supported platforms. Therefore, every sample must be configured to build on Linux, Mac, and Windows.
 
-- `core-projects` contains .NET Core samples. These are referenced by topics under `/docs/core`.
+- `csharp` contains C# language samples. These are referenced by topics under `docs/csharp`.
 
-   * The `core-projects` directory contains samples that highlight .NET Core. The purpose of your sample should be to teach developers something about .NET Core. This includes the framework packaging, the new tooling, or the cross-platform experience.
+   * The `csharp` directory contains samples where the purpose is to explain the C# language. While these samples will use frameworks and libraries, their focus is on the C# language. Our CI buid server builds these samples on multiple supported platforms. Therefore, every sample must be configured to build on Linux, Mac, and Windows.
 
-- `csharp-language` contains C# language samples. These are referenced by topics under `docs/csharp`.
+- `framework` contains .NET Framework samples. These are referenced by topics under many different locations in the documentation. However, what is significant about these samples is that they buid only on Windows where the .NET framework, and Visual Studio are installed.
 
-   * The `csharp-language` directory contains samples where the purpose is to explain the C# language. While these samples will use frameworks and libraries, their focus is on the C# language.
+   * The `framework` directory contains samples that highlight .NET with platform dependencies. These may include migration samples, platform specific samples, or other samples that require the framework or the Windows based tools. Our CI buid server builds these samples on Windows only. Do not place any samples here that should be checked for cross-platform builds.
 
- - `linq` contains all the 101 LINQ samples that were originally created when LINQ was developed. These don't have topics associated with them yet.
-
-   * The `linq` directory contains samples that are specific to understanding the concepts and implementation behind Language Integrated Query (LINQ). These samples should be focused on the language support and library methods that are specific to LINQ. Other samples my use the LINQ libraries, but unless they are focused on explaining LINQ concepts, they should be in one of the other directories.
-
-We will expand these directories as the core-docs repository adds new content. 
+We will expand these directories as the core-docs repository adds new content. For example, we will add Xamarin directories, like `xamarin-ios` and `xamarin-android` directories. 
 
 Sample code may fit more than one of these areas. In those cases, place the sample so it matches
 the topics you are covering in your documents. Ask yourself what readers will learn from reading

docs/core/porting/project-structure.md

@@ -100,18 +100,18 @@ Please see [.NET Core porting documentation][porting-doc] for more guidance on m
 
 [porting-doc]: index.md
 [example-initial-project]: media/project-structure/project.png "Existing project"
-[example-initial-project-code]: https://github.com/dotnet/core-docs/tree/master/samples/core-projects/libraries/migrate-library/
+[example-initial-project-code]: https://github.com/dotnet/core-docs/tree/master/samples/framework/libraries/migrate-library/
 
 [example-xproj]: media/project-structure/project.xproj.png "Create an xproj that targets multiple frameworks"
-[example-xproj-code]: https://github.com/dotnet/core-docs/tree/master/samples/core-projects/libraries/migrate-library-xproj/
-[example-xproj-projectjson]: https://github.com/dotnet/core-docs/tree/master/samples/core-projects/libraries/migrate-library-xproj/src/Car/project.json
-[example-xproj-projectjson-test]: https://github.com/dotnet/core-docs/tree/master/samples/core-projects/libraries/migrate-library-xproj/tests/Car.Tests/project.json
+[example-xproj-code]: https://github.com/dotnet/core-docs/tree/master/samples/framework/libraries/migrate-library-xproj/
+[example-xproj-projectjson]: https://github.com/dotnet/core-docs/tree/master/samples/framework/libraries/migrate-library-xproj/src/Car/project.json
+[example-xproj-projectjson-test]: https://github.com/dotnet/core-docs/tree/master/samples/framework/libraries/migrate-library-xproj/tests/Car.Tests/project.json
 
 [example-xproj-different-folder]: media/project-structure/project.xproj.different.png ".NET Core project with existing PCL in different folder"
-[example-xproj-different-code]: https://github.com/dotnet/core-docs/tree/master/samples/core-projects/libraries/migrate-library-xproj-keep-csproj/
+[example-xproj-different-code]: https://github.com/dotnet/core-docs/tree/master/samples/framework/libraries/migrate-library-xproj-keep-csproj/
 
 [example-pcl]: media/project-structure/project.pcl.png "PCL Targeting .NET Core"
-[example-pcl-code]: https://github.com/dotnet/core-docs/tree/master/samples/core-projects/libraries/migrate-library-pcl
+[example-pcl-code]: https://github.com/dotnet/core-docs/tree/master/samples/framework/libraries/migrate-library-pcl
 
 [option-xproj]: #replace-existing-projects-with-a-multi-targeted-net-core-project-xproj
 [option-pcl]: #create-a-portable-class-library-pcl-to-target-net-core

docs/core/testing/unit-testing-with-dotnet-test.md

@@ -16,7 +16,7 @@ ms.assetid: bdcdb812-6f13-4f20-9e90-0c0977937142
 
 By [Steve Smith](http://ardalis.com) and [Bill Wagner](https://github.com/BillWagner)
 
-[View or download sample code](https://github.com/dotnet/core-docs/tree/master/samples/core-projects/unit-testing/using-dotnet-test)
+[View or download sample code](https://github.com/dotnet/core-docs/tree/master/samples/core/getting-started/unit-testing-using-dotnet-test)
 
 ## Creating the Projects
 
@@ -138,7 +138,7 @@ not in the NuGet feed. Without this key, you might download
 a package with the same name as your internal library.
 
 You can see the entire file in the
-[samples repository](https://github.com/dotnet/core-docs/blob/master/samples/core-projects/unit-testing/using-dotnet-test/test/PrimeService.Tests/project.json) 
+[samples repository](https://github.com/dotnet/core-docs/blob/master/samples/core/getting-started/unit-testing-using-dotnet-test/test/PrimeService.Tests/project.json) 
 on GitHub.
 
 After this initial structure is in place, you can write your first test.
@@ -242,9 +242,9 @@ Now, these tests all pass.
 You continue to iterate by adding more tests, more theories,
 and more code in the main library. You'll quickly end up
 with the
-[finished version of the tests](https://github.com/dotnet/core-docs/blob/master/samples/core-projects/unit-testing/using-dotnet-test/test/PrimeService.Tests/PrimeServie_IsPrimeShould.cs)
+[finished version of the tests](https://github.com/dotnet/core-docs/blob/master/samples/core/getting-started/unit-testing-using-dotnet-test/test/PrimeService.Tests/PrimeServie_IsPrimeShould.cs)
 and the
-[complete implementation of the library](https://github.com/dotnet/core-docs/blob/master/samples/core-projects/unit-testing/using-dotnet-test/src/PrimeService/PrimeService.cs).
+[complete implementation of the library](https://github.com/dotnet/core-docs/blob/master/samples/core/getting-started/unit-testing-using-dotnet-test/src/PrimeService/PrimeService.cs).
 
 You've built a small library and a set of unit tests for that library.
 You've structured this solution so that adding new packages and tests

docs/core/tutorials/using-on-macos.md

@@ -42,7 +42,7 @@ You can find the links to all of these at the [.NET home page](http://dot.net).
 ## Getting Started
 
 The source for this tutorial is available on
-[GitHub](https://github.com/dotnet/core-docs/tree/master/samples/getting-started/golden).
+[GitHub](https://github.com/dotnet/core-docs/tree/master/samples/core/getting-started/golden).
 
 Start Visual Studio Code. Press Ctrl + '\`' (the back-quote character) to open
 an embedded terminal in VS Code. (Alternatively, you can use a separate

docs/core/tutorials/using-with-xplat-cli.md

@@ -24,7 +24,7 @@ Before you begin, ensure you have the [latest .NET Core CLI tooling](https://www
 
 ## Hello, Console App!
 
-First, navigate to or create a new folder with a name you like.  "Hello" is the name chosen for the sample code, which can be found [here](https://github.com/dotnet/core-docs/tree/master/samples/core-projects/console-apps/Hello).
+First, navigate to or create a new folder with a name you like.  "Hello" is the name chosen for the sample code, which can be found [here](https://github.com/dotnet/core-docs/tree/master/samples/core/console-apps/Hello).
 
 Open up a command prompt and type the following:
 
@@ -99,7 +99,7 @@ Let's try compiling a self-contained application instead of a portable applicati
 
 You need to make some changes to your `project.json`
 file to direct the tools to build a self-contained application. You can see these in the
-[HelloNative](https://github.com/dotnet/core-docs/tree/master/samples/core-projects/console-apps/HelloNative)
+[HelloNative](https://github.com/dotnet/core-docs/tree/master/samples/core/console-apps/HelloNative)
 project in the samples directory.
 
 The first change is to remove the `"type": "platform"` element from all dependencies. 
@@ -258,7 +258,7 @@ Now the fun part: making the new file do something!
 
 ### Example: A Fibonacci Sequence Generator
 
-Let's say you want to build off of the previous [Fibonacci example](https://github.com/dotnet/core-docs/tree/master/samples/core-projects/console-apps/Fibonacci) by caching some Fibonacci values and add some recursive flair.  Your code for a [better Fibonacci example](https://github.com/dotnet/core-docs/tree/master/samples/core-projects/console-apps/FibonacciBetter) might look something like this:
+Let's say you want to build off of the previous [Fibonacci example](https://github.com/dotnet/core-docs/tree/master/samples/core/console-apps/Fibonacci) by caching some Fibonacci values and add some recursive flair.  Your code for a [better Fibonacci example](https://github.com/dotnet/core-docs/tree/master/samples/core/console-apps/FibonacciBetter) might look something like this:
 
 ```csharp
 using System;
@@ -373,7 +373,7 @@ Say you wanted to introduce some new types to do work on.  You can do this by ad
 |__project.json
 ```
 
-This works great when the size of your project is relatively small.  However, if you have a larger app with many different data types and potentially multiple layers, you may wish to organize things logically.  This is where folders come into play.  You can either follow along with [the NewTypes sample project](https://github.com/dotnet/core-docs/tree/master/samples/core-projects/console-apps/NewTypes) that this guide covers, or create your own files and folders.
+This works great when the size of your project is relatively small.  However, if you have a larger app with many different data types and potentially multiple layers, you may wish to organize things logically.  This is where folders come into play.  You can either follow along with [the NewTypes sample project](https://github.com/dotnet/core-docs/tree/master/samples/core/console-apps/NewTypes) that this guide covers, or create your own files and folders.
 
 To begin, create a new folder under the root of your project.  `/Model` is chosen here.
 
@@ -552,7 +552,7 @@ You'll probably be wanting to test your projects at some point.  Here's a good w
 
 ### Example: Extending the NewTypes project
 
-Now that the project system is in place, you can create your test project and start writing tests!  From here on out, this guide will use and extend [the sample Types project](https://github.com/dotnet/core-docs/tree/master/samples/core-projects/console-apps/NewTypes).  Additionally, it will use the [Xunit](https://xunit.github.io/) test framework.  Feel free to follow along or create your own multi-project system with tests.
+Now that the project system is in place, you can create your test project and start writing tests!  From here on out, this guide will use and extend [the sample Types project](https://github.com/dotnet/core-docs/tree/master/samples/core/console-apps/NewTypes).  Additionally, it will use the [Xunit](https://xunit.github.io/) test framework.  Feel free to follow along or create your own multi-project system with tests.
 
 
 The whole project structure should look like this:

docs/csharp/expression-trees-building.md

@@ -203,7 +203,7 @@ we'd like to avoid in our everyday coding tasks.
 
 For this section, I've also updated the visitor code to visit every node in this expression
 tree and write out information about the nodes that are created in this sample. You can see
-the code in [the samples section](https://github.com/dotnet/core-docs/tree/master/samples/csharp-language/expression-trees).
+the code in [the samples section](https://github.com/dotnet/core-docs/tree/master/samples/csharp/expression-trees).
 You can experiment for yourself: build it and run the samples.
 
 ## Examining the APIs

docs/csharp/indexers.md

@@ -76,7 +76,7 @@ Let's walk through some of the common scenarios for using *indexers*.
 The code for all the samples is available at the core-docs [GitHub
 repository](https://github.com/dotnet/core-docs). Or, you can
 access the 
-[sample folder](https://github.com/dotnet/core-docs/tree/master/samples/csharp-language/indexers)
+[sample folder](https://github.com/dotnet/core-docs/tree/master/samples/csharp/indexers)
 directly.
 
 ### Arrays and Vectors

docs/csharp/tutorials/console-teleprompter.md

@@ -80,8 +80,8 @@ namespace TeleprompterConsole
 ## Reading and Echoing the File
 The first feature to add is to read a text file, and display all that text
 to the console. First, let’s add a text file. Copy the 
-[sampleQuotes.txt](https://github.com/dotnet/core-docs/blob/master/samples/getting-started/csharp/console-teleprompter/sampleQuotes.txt)
-file from the GitHub repository for this [sample](https://github.com/dotnet/core-docs/tree/master/samples/getting-started/csharp/console-teleprompter) into your project directory. 
+[sampleQuotes.txt](https://github.com/dotnet/core-docs/blob/master/samples/csharp/getting-started/console-teleprompter/sampleQuotes.txt)
+file from the GitHub repository for this [sample](https://github.com/dotnet/core-docs/tree/master/samples/csharp/csharp/console-tconsole-teleprompter) into your project directory. 
 This will serve as the script for your
 application.
 

docs/csharp/tutorials/console-webapiclient.md

@@ -485,7 +485,7 @@ Console.WriteLine(repo.LastPush);
 ```
 
 Your version should now match the finished version located
-[here](https://github.com/dotnet/core-docs/tree/master/samples/getting-started/csharp/console-webapiclient).
+[here](https://github.com/dotnet/core-docs/tree/master/samples/csharp/getting-started/console-webapiclient).
 
 ## Conclusion
 

docs/csharp/tutorials/microservices.md

@@ -32,7 +32,7 @@ Along the way, you'll also see some C# language features:
 * How to process incoming HTTP Requests and generate the HTTP Response
 * How to work with nullable value types
 
-You can retrieve the code from our [GitHub repository.](https://github.com/dotnet/core-docs/tree/master/samples/getting-started/csharp/WeatherMicroservice)
+You can retrieve the code from our [GitHub repository.](https://github.com/dotnet/core-docs/tree/master/samples/csharp/getting-started/WeatherMicroservice)
 
 ### Why Docker?
 

docs/csharp/tutorials/working-with-linq.md

@@ -38,7 +38,7 @@ You'll also compare the updated order to the original order.
 
 This tutorial has multiple steps. After each step, you can run the
 application and see the progress. You can also see the completed
-sample in our [GitHub repository.](https://github.com/dotnet/core-docs/blob/master/samples/getting-started/csharp/console-linq)
+sample in our [GitHub repository.](https://github.com/dotnet/core-docs/blob/master/samples/csharp/getting-started/console-linq)
 
 
 ## Prerequisites