Donovan Brown

Steps:

1. Intro
2. VSO
3. Docker
4. xUnit
5. Build
6. Back end
7. Selenium
8. Docker
9. Release Management
10. Testing

Microsoft Visual Studio has tooling that eases the creation and deployment of Docker hosts. In this post we are going install the extensions and configure our Docker host. Be sure to check that all your tools and extensions are up to date by visiting the Notifications in Visual Studio.

Once your IDE is up to date we can install the needed extensions.

For this demo we are going to need Tools for Docker , SQL Server Data Tools , and ASP.NET and Web Tools .  The tools for Docker enable the deployment of ASP.NET 5 applications to Docker containers running on Linux or Windows VMs. Make sure you have at least version 0.7.1.

1. Install Web Tools Extensions
   1. Visit Microsoft ASP.NET and Web Tools 2015 download page
   2. Click Download
   3. Check DotNetVersionManager-x64.msi
   4. Check WebToolsExtensionsVS14.msi
   5. Click Next
   6. Click Run on both the msis and install one after the other
2. Install Tools for Docker
   1. Visit Tools for Docker download page
   2. Click Download button
   3. Click Run
   4. Install
3. Update SSDT
   1. From the Tools menu, select Extensions and Updates
   2. SSDT should already be installed but still verify there are no updates needed
   3. If you find any, install them before you proceed

   SQL Server Data Tools is one of Microsoft’s best kept secrets.  If you are developing for SQL Server, you owe it to yourself to at least research the power in SSDT.  SSDT enables the management of your database schema just like every other project in your solution and deploys your changes without writing a single line of SQL and without losing a single line of data.

   To make sure everything is set up correctly, let's create the ASP.NET 5 application we are going to use in this demo.

4. Create ASP.NET 5 app
   1. From the File menu select New / Project…
   2. From the Visual C# section select Web
   3. Select the ASP.NET Web Application template
   4. Enter PeopleTracker.Preview as the name
   5. Enter PeopleTracker as the solution name
   6. Check the Add to source control check box
   7. Click OK
   8. Select Web Application from the ASP.NET 5 Preview Templates
   9. Change the Authentication to No Authentication
      1. Click Change Authentication
      2. Select No Authentication
      3. Click OK
   10. Uncheck Host in the cloud check box
   11. Click OK
   12. Select Git
       1. This demo would also work if we selected TFVC. However, for this demo I wanted to show how to work with our new Pull Request feature, so I selected Git. TFVC is not going away and is still a valid source control choice.
   13. Click OK

   Once the project creation is complete, compile and run the application to make sure everything is working as expected.

5. Create Dev Docker Host
   1. Right-click project
   2. Select Publish...
   3. Select Docker Containers
      
   4. Click the New... button
   5. Select Subscription
   6. Select Location
   7. Enter DNS name for Dev Docker Host
   8. Select Ubuntu Server 15.04 for image
   9. Enter Username
   10. Enter Password
   11. Confirm Password
   12. Click OK
   13. Click OK on Virtual Machine Creation Started dialog

   A PublishScripts folder will be added to your solution with a Scripts and Templates folders. For each host you create you will get a PowerShell script and two json files. You can monitor the progress from the Output window or from the Azure Portal. When the deployment of the template is complete you will have a folder created that has all the certs needed to connect to the host. We will reuse theses certs when we create the additional Docker Hosts. Each Docker Host will be created in its own Resource Group and will include the following:

   • Virtual Machine
   • Network Adapter
   • Public IP
   • Virtual Network
   • Storage Account

6. Publish to your Dev Docker Host
   1. Right-click project
   2. Select Publish
      1. This time, the Publish dialog will open on the Connection tab.
   3. Click Validate Connection
   4. Click Next
   5. Click Publish

   Leave the Dockerfile text box empty so it will be auto generated for us and click Publish. Visual Studio will create a dockerfile and add it to your project. It will also build, package, and deploy our application to our Docker Host and launch our default browser so we can use our site. Once the publish is complete a browser will open with your application running.

   At Ignite I deployed to three environments so I repeated the process to provision my QA and Prod hosts as well.

7. Create QA Docker Host
   1. Right-click project
   2. Select Publish...
   3. Click Profile Tab
   4. Select Docker Containers
   5. Click the New... button
   6. Change DNS name for QA Docker Host
   7. Click OK
   8. Click OK on Virtual Machine Creation Started dialog
8. Publish to your QA Docker Host
   1. Right-click project
   2. Select Publish...
      1. This time, the Publish dialog will open on the Connection tab.
   3. Click Validate Connection
   4. Click Next
   5. Click Publish
9. Create Prod Docker Host
   1. Right-click project
   2. Select Publish...
   3. Click Profile Tab
   4. Select Docker Containers
   5. Click the New... button
   6. Change DNS name for Prod Docker Host
   7. Click OK
   8. Click OK on Virtual Machine Creation Started dialog
10. Publish to your Prod Docker Host
    1. Right-click project
    2. Select Publish...
       1. This time, the Publish dialog will open on the Connection tab.
    3. Click Validate Connection
    4. Click Next
    5. Click Publish

    The final step is to use Team Explorer to commit and push your changes to VSO.

11. Commit and Push your changes
    1. Open Team Explorer
    2. Open Changes
       1. If you have not already, click the Configure link to configure your user name and email address and return to the Changes tab.
    3. Review the Untracked Files and make sure everything is included in the commit except the openssl tools.
    4. Enter comment
    5. Select Commit and Push
       

    This will take you to the Synchronization page so we can enter the URL to our VSO Git repo. Visit the Code page of your VSO team project and copy the value presented under the “to clone this repository” section. Paste that value into the text box on the Synchronization page and click publish. When the publish is complete, return the VSO code page and press F5 to see your code in VSO. In the next post we will add xUnit test to our project.