initial content checkin

CONTRIBUTING.md

@@ -0,0 +1,84 @@
+# Contributing to a Microsoft Cloud Workshop
+
+Welcome, and thank you for your interest in contributing to our Microsoft Cloud Workshop!
+
+There are many ways that you can contribute, beyond writing or coding. The goal of this document is to provide a high-level overview of how you can get involved.
+
+## Contributing
+
+This project welcomes contributions and suggestions.  Most contributions require you to agree to a
+Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us
+the rights to use your contribution. For details, visit https://cla.microsoft.com.
+
+When you submit a pull request, a CLA-bot will automatically determine whether you need to provide
+a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions
+provided by the bot. You will only need to do this once across all repos using our CLA.
+
+This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
+For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or
+contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.
+
+## Asking Questions
+
+Have a question? Open an issue using the question template and the `question` label.  
+
+The active community will be eager to assist you. Your well-worded question will serve as a resource to others searching for help.
+
+## Providing Feedback
+
+Your comments and feedback are welcome, and the project team is available via handful of different channels.
+
+## Reporting Issues
+
+Have you identified a reproducible problem in a workshop? Have a feature request? We want to hear about it! Here's how you can make reporting your issue as effective as possible.
+
+### Identify Where to Report
+
+The MSW project is distributed across multiple repositories. Try to file the issue against the correct workshop. Check the list of [Related Projects](https://github.com/Microsoft/MSW/wiki/Related-Projects) if you aren't sure which repo is correct.
+
+### Look For an Existing Issue
+
+Before you create a new issue, please do a search in [open issues](https://github.com/Microsoft/MSW/issues) to see if the issue or feature request has already been filed.
+
+Be sure to scan through the [most popular](https://github.com/Microsoft/MSW/issues?q=is%3Aopen+is%3Aissue+label%3Afeature-request+sort%3Areactions-%2B1-desc) feature requests.
+
+If you find your issue already exists, make relevant comments and add your [reaction](https://github.com/blog/2119-add-reactions-to-pull-requests-issues-and-comments). Use a reaction in place of a "+1" comment:
+
+* 👍 - upvote
+* 👎 - downvote
+
+
+If you cannot find an existing issue that describes your bug or feature, create a new issue using the guidelines below.
+
+### Writing Good Bug Reports and Feature Requests
+
+File a single issue per problem and feature request. Do not enumerate multiple bugs or feature requests in the same issue.
+
+Do not add your issue as a comment to an existing issue unless it's for the identical input. Many issues look similar, but have different causes.
+
+The more information you can provide, the more likely someone will be successful reproducing the issue and finding a fix.  Please use the template for each issue.
+
+### Final Checklist
+
+Please remember to do the following:
+
+* [ ] Search the issue repository to ensure your report is a new issue
+
+* [ ] Recreate the issue after disabling all extensions
+
+* [ ] Simplify your code around the issue to better isolate the problem
+
+Don't feel bad if the developers can't reproduce the issue right away. They will simply ask for more information!
+
+### Follow Your Issue
+
+Once submitted, your report will go into the [issue tracking](https://github.com/Microsoft/vscode/wiki/Issue-Tracking) work flow. Be sure to understand what will happen next, so you know what to expect, and how to continue to assist throughout the process.
+
+## Contributing Fixes
+
+If you are interested in writing code to fix issues,
+please see [How to Contribute](https://github.com/Microsoft/MSW/wiki/How-to-Contribute) in the wiki.
+
+# Thank You!
+
+Your contributions to open source, large or small, make great projects like this possible. Thank you for taking the time to contribute.

HOL/Setup.md

@@ -0,0 +1,135 @@
+# Mobile app innovation setup
+
+1.  Using the same Microsft.com account:
+
+    -   Azure Subscription
+
+    -   Visual Studio Team Services Subscription
+
+    -   Account in Mobile Center
+
+2.  Virtual Machine
+
+    -   Please note, do **NOT** use a VM for this lab. You will not be able to run the simulated mobile app from a virtual machine.
+
+3.  Local machine configured with (**complete the day before the lab!**):
+
+    -   Windows
+
+        i.  Workstation with VT-X Support w/Hyper-V Disabled (under Programs and Features in Windows Settings)
+
+        ii. Intel HAXM Support installed
+
+        Instructions: <https://developer.xamarin.com/guides/android/getting_started/installation/android-emulator/hardware-acceleration/>
+
+        iii. Windows 10 (Fall Creators Update recommended)
+
+        iv. Visual Studio 2017 (15.5.5 Required)
+
+    -   Mac
+
+        v.  Visual Studio for Mac (latest stable release)
+
+        vi. Xcode 9.2 (or current latest stable release)
+
+4.  Android SDKs (21, 22, 23, 24, 25, 26, 27)
+
+5.  NET Framework 4.7.1 runtime (or higher)
+
+    -   <https://www.microsoft.com/net/download/windows>
+
+
+## Before the hands-on lab
+
+**Duration**: 60 minutes
+
+Completing this lab will require accounts for Azure, Visual Studio Team Services, and Visual Studio App Center, as well as an up-to-date installation of Visual Studio on Windows 10. In this exercise, we will walk through the steps needed for each of these tasks and set up your environment to complete this lab.
+
+### Task 1: Create an account, and sign into the Azure portal
+
+Throughout this lab, you will utilize an Azure subscription, and a Microsoft account. If you do not already have an Azure subscription, please follow the instructions at <https://azure.microsoft.com/en-us/free/> to set up your account. If you already have an account in <https://portal.azure.com>, then you can continue to the next task.
+
+### Task 2: Sign into Visual Studio Team Services, and create a new account
+
+1.  Browse to <https://visualstudio.com>, and sign in with the Microsoft account used to access the Azure Portal in the previous step.
+
+2.  If you have not already created an account in Visual Studio Team services, select the button to create a new app.
+
+    ![Create new account icon](images/Setup/image3.png "Create new account icon")
+    
+3.  Choose a name for your project (it will need to be unique), and choose "Git" as the source control mechanism.
+
+4.  Select **Continue**.
+
+    ![On the Visual Studio Team services project creation page, contosoair is entered in the box next to .visualstudio.com under Host my projects at, Git is selected below Manage code using, and Continue is selected at the bottom of the page.](images/Setup/image4.png "Create a new app")
+
+After a few minutes, your new account will be created, and a new project (MyFirstProject) will be automatically created. We won't use this project for the app, but you can just ignore it and leave it in your account.
+
+### Task 3: Sign into Visual Studio App Center
+
+In addition to the Azure portal, you will utilize Visual Studio App Center for building and monitoring your mobile app. Please browse to <https://appcenter.ms>/apps and sign in with the same Microsoft account you used in the previous task. This will ensure that you can utilize things like data export between App Center and Application Insights in Azure.
+
+### Task 4: Update VS 2017 to 15.5.5
+
+1.  Launch Visual Studio 2017
+
+2.  Select **Tools \> Extensions and Updates**
+
+3.  Expand **Updates** in the left-hand menu, then select **Product Updates**.
+
+4.  If you see an option for Visual Studio Update, select **Update**.
+
+5.  Follow the prompts to start the update to VS 2017 15.5.5 or greater.
+    **WARNING**: This update process can take up to an hour to complete.
+
+![In Visual Studio 2017, Updates and Product Updates are selected on the left, Update is highlighted next to Visual Studio Update in the middle, and Current Version and New Version are highlighted on the right.](images/Setup/image5.png "Update Visual Studio 2017")
+
+6.  After the update is complete, you'll need to install the **Xamarin SDK Manager** extension.
+
+    -   Launch Visual Studio Installer. You can find the installer in the Windows Start menu.
+        
+        ![Visual Studio Installer is highlighted in the Windows Start menu.](images/Setup/image6.png "Run the Visual Studio installer")
+
+    -   Select the **Modify** button.
+        
+        ![The Modify button is highlighted under Visual Studio 2017 15.5.7 Installed.](images/Setup/image7.png "Select Modify")
+
+    -   Select the **Individual components** tab.
+
+    -   Scroll down to the **Development Activities** section. Make sure the **Xamarin SDK Manager** box is checked, and then select the **Modify** button in the bottom right corner of the dialog to proceed.
+
+> ![Xamarin SDK Manager is highlighted in the Development Activities section.](images/Setup/image8.png "Verify that Xamarin SDK Manager is selected")
+
+e.  Once all updates are completed installing, restart your VM.
+
+### Task 5: Update Android SDKs
+
+To complete these exercises, you will need to make sure you have all the correct Android SDKs. This requires some additional steps after completing the upgrade.
+
+1.  Launch Visual Studio 2017.
+
+2.  Select **Tools \> Android \> Android SDK Manager**.
+
+3.  Select each of the Android SDK platforms from 5.0 (Lollipop) -- 8.0 (Oreo).
+
+-   API Levels 21, 22, 23, 24, 25, 26
+
+4.  Select **Apply Changes** to download and install the selected API levels.
+
+    ![Each of the Android SDK platforms from 5.0 (Lollipop) -- 8.0 (Oreo) are selected on the Platform tab of the Android SDKs and Tools dialog box.](images/Setup/image9.png "Select the Android SDK platforms")
+
+5.  Choose the **Tools** tab.
+
+6.  Make sure that a version 27.0.x of Android SDK Platform-Tools and Android SDK Build-Tools are installed.
+
+    ![Android SDK Platform-Tools and Android SDK Build-Tools are selected on the Tools tab of the Android SDKs and Tools dialog box.](images/Setup/image10.png "Verify that Android SDK Tools and Android SDK Build Tools are selected")
+
+7.  If the available Android SDK Platform-Tools version is less than 27.0.x, select the **Updates Available** button on the bottom-left corner of the dialog.
+
+    ![Android SDK Platform-Tools and Android SDK Build-Tools are selected on the Tools tab of the Android SDKs and Tools dialog box, Version 25.0.3 is highlighted next to Android SDK Platform-Tools, and the Updates Available button is highlighted at the bottom.](images/Setup/image11.png "Update the Android SDK Platform-Tools version if necessary")
+
+8.  After installing the updates, you may need to re-select the **Android SDK Build Tools** and **Platform-Tools.**
+
+9.  Select **Apply Changes**.
+
+You should follow all steps provided *before* attending the Hands-on lab.