5 |
4 |
5 |
31 |
32 | > **Talking Point**:
33 | First off, Visual Studio 2017 makes it very easy to bring in your previously built .NET Core projects with the preview tooling and migrate them for you. Let’s migrate an ASP.NET Core web project I had built with Visual Studio 2015. As you can see I get a standard project migration dialog when I open the project which will take a backup and migrate your solution.
34 |
35 | 3. Open project file. Right-click on project in Solution Explorer, select **Edit BikeSharing.Web.csproj**
36 |
37 | 
38 |
39 | > **Talking Point**:
40 | So what did the migration do exactly? All it did was take the project information in the previous project.json format and transform it into the new csproj format. Let’s take a look at it.
41 |
42 |
43 | 4. Scroll through the file, noting how significantly smaller it is.
44 |
45 | 
46 |
47 | > **Talking Point**:
48 | Notice when I say new format, I mean the NOT SUPER SCARY HUMAN
49 | UNREADABLE format. Notice we have no more GUIDS, Hint paths, no more listing each file individually that should be included! Any file we put in our solution folder will be picked up automatically.
50 |
51 | 5. Point out the new **References** section – now called **Dependencies** and how it groups them.
52 |
53 | 6. Expand **Projects** and **SDK** nodes as well.
54 |
55 | 7. Highlight Project reference node.
56 |
57 | 
58 |
59 | > **Talking Point**:
60 | Notice that our references are grouped a lot nicer here in the Solution Explorer too. We can now easily tell the difference between package references, project references and framework references.I should also mention that this data library project reference is using Entity Framework Core which is based on the .NET Standard library. The .NET Standard library defines a common API surface area across .NET implementation and makes our library portable. This means we could reference this from other project types, such as Xamarin, WPF, Unity or UWP, not just .NET Core projects.
61 |
62 |
63 | 8. In Solution Explorer, highlight the Dependencies / NuGet
64 |
65 | 
66 |
67 | > **Talking Point**:
68 | This is a great new UI but you don’t need to use it if we prefer to stay in the “CODE ZONE”. We can edit the csproj directly. Keep your eye on the NuGet packages node in solution explorer as I edit the csproj.
69 |
70 | 9. Remove a package reference (Ctrl+X). Save (Ctrl+S)
71 |
72 | 
73 |
74 | > **Talking Point**:
75 | Goodbye package.
76 |
77 |
78 | 10. Add the package back in (Ctrl+V)
79 |
80 | 11. Save (Ctrl+S)
81 |
82 | 
83 |
84 | > **Talking Point**:
85 | …and add it back again which triggers the package restore. You see that Visual Studio always stays in sync. Say goodbye to reloading the project when we change the csproj! WHOOO HOOOO
86 |
87 | 12. Right-click on dependencies and select Manage NuGet Packages
88 |
89 | 
90 |
91 | > **Talking Point**:
92 | This gives us the flexibility of using the editor or the UI to make project-level changes. As you can see we still have our NuGet UI.
93 |
94 | 13. Select BROWSE
95 |
96 | 14. Start typing **ApplicationInsights.Asp**
97 |
98 | 
99 |
100 | > **Talking Point**:
101 | I could add packages just like before of course.
102 | Say I’m looking at adding Application Insights to my ASP.NET Core app. This capability is new in ASP.NET Core. Application Insights provides powerful monitoring and diagnostics telemetry, plus the tooling to analyze it all. Typically, you can just install a package and start using it in your code, but this one it takes a little more work to add
103 | the instrumentation. Thankfully Visual Studio is here to help! Instead of manually installing the package here and configuring all the pieces, Visual Studio can do all of this for me with a much better experience than previous versions.
104 |
105 | 15. Add Connected Service
106 |
107 | 
108 |
109 | > **Talking Point**:
110 | I can just add a Connected Service and select Monitoring with Application Insights.
111 |
112 | 16. Click "*Monitoring with Application Insights*”
113 |
114 | 
115 |
116 | > **Talking Point**:
117 | The Connected Services experience in Visual Studio helps me add code *and* all the dependencies I need to get me quickly get up and running.
118 |
119 | 17. Click **Start Free**
120 |
121 | 
122 |
123 | > **Talking Point**:
124 | For Application Insights, we can choose to set up the data collection in Azure for free.
125 |
126 | **Point out the settings.**
127 |
128 | 18. Scroll down and mention you can also do this locally.
129 |
130 | 
131 |
132 | > **Talking Point**:
133 | Here is where I specify my Azure subscription details and can see what’s included. Notice that I don’t have to use Azure, I can also use App Insights in a local-only mode that will show me telemetry when debugging locally.
134 |
135 |
136 | 19. Select Resource drop-down, point out you can create a new Resource, but is better to select existing resource so you can have some data collected once you get to this point.
137 |
138 | 
139 |
140 | > **Talking Point**:
141 | Here Visual Studio can set up a new resource. However, I’m going to add this to an existing resource that’s attached to a copy of this app that I’ve already published so you can see some telemetry that’s been collecting there.
142 |
143 | 20. Click Register.
144 |
145 | > **Talking Point**:
146 | Now it’s setting up my telemetry resources in Azure by automatically adding the NuGet package, the scripts, and necessary code and configuration that I need. Then it will be ready to start collecting events. There are a bunch of events that will automatically collect and you can also add your own custom events as well.
147 |
148 |
149 | 21. Open Program.cs, add code to line 19.
150 |
151 | ```
152 | \`\`\` .UseApplicationInsignts() \`\`\`
153 | ```
154 |
155 | 
156 |
157 | > **Talking Point**:
158 | Last thing we need to do is make sure we add a line of code to the ASP.NET middleware pipeline.
159 |
160 |
161 | 22. Right-click, **publish**
162 |
163 | 
164 |
165 | > **Talking Point**:
166 | Of course, I will want to deploy this app in order to start collecting real events.
167 |
168 |
169 | 23. Click the arrow and scroll through the list of choices.
170 |
171 | 24. Select **Existing App Service**
172 |
173 | 25. Click **Publish**
174 |
175 | 
176 |
177 | > **Talking Point**:
178 | Notice we have a new publish experience and more choices to publish to. We can choose to publish this to Azure app service,which we can use for easily hosting web-based services and applications, IIS, a folder, we can even publish to a Virtual Machine right from here.
179 |
180 |
181 | 26. Select the app service you want to deploy to.
182 |
183 | 27. Click **OK**
184 |
185 | 
186 |
187 | > **Talking Point**:
188 | I’m going to select an existing App Service. This will kick off a release build (which is cool I didn’t have to remember that myself) and publish our application for us.Once it’s finished, we can see it in our browser.
189 |
190 | 28. Hit refresh a couple times to generate some recent requests.
191 |
192 | > **Talking Point**:
193 | Let’s create some recent events by hitting the website.
194 |
195 | 29. Click on Application Insights button.
196 |
197 | 
198 |
199 | > **Talking Point**:
200 | Now we’ll jump back to Visual Studio. Notice I have a button up here in the toolbar for Application Insights.
201 |
202 | 30. Change time range to “Last 3 Days”
203 |
204 | 31. Double-click one of the requests to show the properties.
205 |
206 | 
207 |
208 | > **Talking Point**:
209 | Here you can see the requests that it collected and we can drill into the details to see a bunch of information about the event like the operation, response time, codes, etc.
210 |
211 | 32. Scroll down and show how you can create an issue right here in VSTS
212 |
213 | 
214 |
215 | > **Talking Point**:
216 | And look, I can create and track issues in Visual Studio Team Services RIGHT HERE. Amazing!
217 |
218 | 
219 |
220 | > **Talking Point**:
221 | As we start to get a lot more information, we need a powerful way to look at the trends.
222 |
223 | 
224 |
225 | > **Talking Point**:
226 | Here we can start analyzing the trends, pinpointing issues, and learning how users are using our site. Notice that this points out anomalies as well, like in this case, performance degradation.Of course, this is all available in the Azure portal too. And you can also write your own queries to analyze the telemetry in interesting ways. As you can see, Visual Studio makes all this super simple to set up, not
227 | just for .NET Core apps but for any app. Why are you not using this on your apps today?! Go download Visual Studio 2017 now!
228 |
--------------------------------------------------------------------------------
/.gitignore:
--------------------------------------------------------------------------------
1 | ## Ignore Visual Studio temporary files, build results, and
2 | ## files generated by popular Visual Studio add-ons.
3 |
4 | # User-specific files
5 | *.suo
6 | *.user
7 | *.userosscache
8 | *.sln.docstates
9 |
10 | # User-specific files (MonoDevelop/Xamarin Studio)
11 | *.userprefs
12 |
13 | # Build results
14 | [Dd]ebug/
15 | [Dd]ebugPublic/
16 | [Rr]elease/
17 | [Rr]eleases/
18 | x64/
19 | x86/
20 | bld/
21 | [Bb]in/
22 | [Oo]bj/
23 | [Ll]og/
24 |
25 | # Visual Studio 2015 cache/options directory
26 | .vs/
27 | # Uncomment if you have tasks that create the project's static files in wwwroot
28 | #wwwroot/
29 |
30 | # MSTest test Results
31 | [Tt]est[Rr]esult*/
32 | [Bb]uild[Ll]og.*
33 |
34 | # NUNIT
35 | *.VisualState.xml
36 | TestResult.xml
37 |
38 | # Build Results of an ATL Project
39 | [Dd]ebugPS/
40 | [Rr]eleasePS/
41 | dlldata.c
42 |
43 | # DNX
44 | project.lock.json
45 | artifacts/
46 |
47 | *_i.c
48 | *_p.c
49 | *_i.h
50 | *.ilk
51 | *.meta
52 | *.obj
53 | *.pch
54 | *.pdb
55 | *.pgc
56 | *.pgd
57 | *.rsp
58 | *.sbr
59 | *.tlb
60 | *.tli
61 | *.tlh
62 | *.tmp
63 | *.tmp_proj
64 | *.log
65 | *.vspscc
66 | *.vssscc
67 | .builds
68 | *.pidb
69 | *.svclog
70 | *.scc
71 |
72 | # Chutzpah Test files
73 | _Chutzpah*
74 |
75 | # Visual C++ cache files
76 | ipch/
77 | *.aps
78 | *.ncb
79 | *.opendb
80 | *.opensdf
81 | *.sdf
82 | *.cachefile
83 | *.VC.db
84 | *.VC.VC.opendb
85 |
86 | # Visual Studio profiler
87 | *.psess
88 | *.vsp
89 | *.vspx
90 | *.sap
91 |
92 | # TFS 2012 Local Workspace
93 | $tf/
94 |
95 | # Guidance Automation Toolkit
96 | *.gpState
97 |
98 | # ReSharper is a .NET coding add-in
99 | _ReSharper*/
100 | *.[Rr]e[Ss]harper
101 | *.DotSettings.user
102 |
103 | # JustCode is a .NET coding add-in
104 | .JustCode
105 |
106 | # TeamCity is a build add-in
107 | _TeamCity*
108 |
109 | # DotCover is a Code Coverage Tool
110 | *.dotCover
111 |
112 | # NCrunch
113 | _NCrunch_*
114 | .*crunch*.local.xml
115 | nCrunchTemp_*
116 |
117 | # MightyMoose
118 | *.mm.*
119 | AutoTest.Net/
120 |
121 | # Web workbench (sass)
122 | .sass-cache/
123 |
124 | # Installshield output folder
125 | [Ee]xpress/
126 |
127 | # DocProject is a documentation generator add-in
128 | DocProject/buildhelp/
129 | DocProject/Help/*.HxT
130 | DocProject/Help/*.HxC
131 | DocProject/Help/*.hhc
132 | DocProject/Help/*.hhk
133 | DocProject/Help/*.hhp
134 | DocProject/Help/Html2
135 | DocProject/Help/html
136 |
137 | # Click-Once directory
138 | publish/
139 |
140 | # Publish Web Output
141 | *.[Pp]ublish.xml
142 | *.azurePubxml
143 | # TODO: Comment the next line if you want to checkin your web deploy settings
144 | # but database connection strings (with potential passwords) will be unencrypted
145 | *.pubxml
146 | *.publishproj
147 |
148 | # Microsoft Azure Web App publish settings. Comment the next line if you want to
149 | # checkin your Azure Web App publish settings, but sensitive information contained
150 | # in these scripts will be unencrypted
151 | PublishScripts/
152 |
153 | # NuGet Packages
154 | *.nupkg
155 | # The packages folder can be ignored because of Package Restore
156 | **/packages/*
157 | # except build/, which is used as an MSBuild target.
158 | !**/packages/build/
159 | # Uncomment if necessary however generally it will be regenerated when needed
160 | #!**/packages/repositories.config
161 | # NuGet v3's project.json files produces more ignoreable files
162 | *.nuget.props
163 | *.nuget.targets
164 |
165 | # Microsoft Azure Build Output
166 | csx/
167 | *.build.csdef
168 |
169 | # Microsoft Azure Emulator
170 | ecf/
171 | rcf/
172 |
173 | # Windows Store app package directories and files
174 | AppPackages/
175 | BundleArtifacts/
176 | Package.StoreAssociation.xml
177 | _pkginfo.txt
178 |
179 | # Visual Studio cache files
180 | # files ending in .cache can be ignored
181 | *.[Cc]ache
182 | # but keep track of directories ending in .cache
183 | !*.[Cc]ache/
184 |
185 | # Others
186 | ClientBin/
187 | ~$*
188 | *~
189 | *.dbmdl
190 | *.dbproj.schemaview
191 | *.pfx
192 | *.publishsettings
193 | node_modules/
194 | orleans.codegen.cs
195 |
196 | # Since there are multiple workflows, uncomment next line to ignore bower_components
197 | # (https://github.com/github/gitignore/pull/1529#issuecomment-104372622)
198 | #bower_components/
199 |
200 | # RIA/Silverlight projects
201 | Generated_Code/
202 |
203 | # Backup & report files from converting an old project file
204 | # to a newer Visual Studio version. Backup files are not needed,
205 | # because we have git ;-)
206 | _UpgradeReport_Files/
207 | Backup*/
208 | UpgradeLog*.XML
209 | UpgradeLog*.htm
210 |
211 | # SQL Server files
212 | *.mdf
213 | *.ldf
214 |
215 | # Business Intelligence projects
216 | *.rdl.data
217 | *.bim.layout
218 | *.bim_*.settings
219 |
220 | # Microsoft Fakes
221 | FakesAssemblies/
222 |
223 | # GhostDoc plugin setting file
224 | *.GhostDoc.xml
225 |
226 | # Node.js Tools for Visual Studio
227 | .ntvs_analysis.dat
228 |
229 | # Visual Studio 6 build log
230 | *.plg
231 |
232 | # Visual Studio 6 workspace options file
233 | *.opt
234 |
235 | # Visual Studio LightSwitch build output
236 | **/*.HTMLClient/GeneratedArtifacts
237 | **/*.DesktopClient/GeneratedArtifacts
238 | **/*.DesktopClient/ModelManifest.xml
239 | **/*.Server/GeneratedArtifacts
240 | **/*.Server/ModelManifest.xml
241 | _Pvt_Extensions
242 |
243 | # Paket dependency manager
244 | .paket/paket.exe
245 | paket-files/
246 |
247 | # FAKE - F# Make
248 | .fake/
249 |
250 | # JetBrains Rider
251 | .idea/
252 | *.sln.iml
253 |
--------------------------------------------------------------------------------
/Installation and better Performance/Readme.md:
--------------------------------------------------------------------------------
1 |
2 | # Visual Studio 2017 RTM - Installation and better performance
3 |
4 |
5 | 
6 |
40 |
41 | > **Talking Point**:
56 |
57 |
58 | > **Talking Point**:
71 |
72 | When you have the extension installed, the GitHub provider should show up
73 | under Open.
74 |
75 | > **Talking Point**:
88 |
89 | > **Talking Point**:
109 |
110 | > **Talking Point**:
4 | 
5 |
| Labs | 30 |Demo Script | 31 |Demo Video | 32 |Source Code | 33 | 34 |
|---|---|---|---|
| Visual Studio 2017 Install and Performance | 38 |Demo Script | 39 |Demo Video | 40 |Source Code | 41 |
| Visual Studio 2017 Productivity | 44 |Demo Script | 45 |Demo Video | 46 |Source Code | 47 | 48 |
| .NET Core tools in Visual Studio 2017 | 51 |Demo Script | 52 |Demo Video | 53 |Source Code | 54 | 55 |
| Visual Studio Tools for Docker | 58 |Demo Script | 59 |Demo Video | 60 |Single-container Source Code
61 | Multi-container Source Code |
62 |
63 |
| Visual Studio and Xamarin | 66 |Demo Script | 67 |Demo Video | 68 |BikeSharing360 Source Code 69 | | 70 | 71 |
| Visual Studio Mobile Center | 74 |Demo Script | 75 |Demo Video | 76 |BikeSharing360 Source Code | 77 | 78 |
| Visual Studio Team Services and DevOps | 81 |Demo Script | 82 |Demo Video | 83 |Source Code | 84 | 85 |
| RedGate and Visual Studio 2017 | 88 |Demo Script | 89 |Demo Video | 90 |Source Code | 91 | 92 |
4 | 
5 |
16 |
17 | >**Talking Point**: Here, I have a simple program that helps me to tweak different bike workouts.
18 |
19 | 2. Open the file **Athlete.cs** from **BikeSharing.DomainLogic** project.
20 |
21 | 
22 |
23 | >**Talking Point**: However, the first thing that you are noticing are all these icons on the left hand side. These are part of live unit testing. Live Unit Testing is constantly running unit tests in the background and updating these icons so that you can know the status of your code. A Red "X" indicates that this line is hit by atleast one failing test while a Green "check" indicates that this line is hit by all passing tests and a Blue "dash" means that this line is not covered by any test at all.
24 |
25 |
26 | 3. Click on the **X** icon and see exactly which tests are hitting here.
27 |
28 | 
29 |
30 |
31 | 4. Click on the Test here to navigate directly to it.
32 |
33 | 
34 |
35 | >**Talking Point**: I am not totally sure why this test is failing. So, i am gonna go and start debugging.
36 |
37 | 5. Start to Debug the failed test from your **Test Explorer** and you should see it throws a null reference exception as shown below.
38 |
39 | 
40 |
41 | 
42 |
43 | >**Talking Point**: This is part of a new exception helper in Visual Studio 2017 while we try to put the most useful information at the top like which variable is null and so on.
44 |
45 | 6. You can see here it even works, we have a chain of dotted expressions.
46 |
47 | 
48 |
49 | >**Talking Point**: So according to **todaysWorkout.Notes** was null, it specifically says that notes is returning null. So, now that i know notes can be null, I want to see anywhere else in my code when accessing a member of notes where i can potentially have another null reference exception.
50 |
51 | ## Demo 2: Finding all references
52 |
53 | 1. To do this, I am gonna do **find all references**. Select **Notes** and press **SHIFT+F12** or right click and **find all references**.
54 |
55 | 
56 |
57 | >**Talkiing Point**: This looks simple. No longer is **Find All References** a simple flat list, now its colorized. We even allow you to custom group how things are sorted in your results. If i take a look at this result, I can see the only member I am ever accessing of a **Notes.length** that I already have tests covering that currently is failing. Lets go fix it. I can quickly navigate to where I am initializing this.
58 |
59 | 2. Let's add quick null check. Add the below code snippet in the line number 18 of **BikeWorkout.cs** file.
60 |
61 | ```
62 | if (notes ==null)
63 | {
64 | throw new ArgumentNullException(nameof(notes));
65 | }
66 |
67 | ```
68 |
69 | 
70 |
71 | >**Talking Point**: I never should be able to initialize these notes as null. The whole point of this app is to make fun tweaks of my bike workouts to impress my friends so i am just going to add quick null check.
72 |
73 | 3. As you type the code, you can notice that the Intellisense looks a little different.
74 |
75 | 
76 |
77 | >**Talking Point**: In Visual Studio 2017, we have added a tray of icons at the bottom to allow you to filter your completion list by **category**. This is especially helpful if you are working with complex API in a large code base where your completion list has many items in it. Or, if you are a WPF developer, its really helpful to sort this by events only. I am gonna finish the typing by using Camel case matching.
78 |
79 | 4. If you see on the left hand side, the Live Unit Testing is being run after the code changes.
80 |
81 | 
82 |
83 | >**Talking Point**: If you are looking on the left hand side, you could see the Live Unit Testing is picking up which test is impacted by the code change, running them and updating these icons to let me know all my tests are now passing.
84 |
85 | 5. Navigate back to the initial method that was working. Click **CTRL+T** which brings up **GoToAll** that allows you to quickly navigate to any file, tag etc.
86 |
87 | 
88 |
89 | >**Talking Point**: I could hunt for this in the Solution Explorer or try to remember in my open tab or which file is in to find it. Or, i could just use "Go to All" which I can get here using Ctrl+T. Go to All allows you to quickly navigate to any file tag or member or symbol decoration from a single location. I can use a query syntax to filter only members and I can start to type the name of the method and navigate directly there. I can see that all my tests are passing. So before i submit this code for review, I actually want to clean it up little bit.
90 |
91 | ## Demo 3: Code Suggestions
92 |
93 | In Visual Studio 2017, we have added the concept of code suggestion. Code suggestions allow you to have best practices or alternate coding patterns to developers.
94 |
95 | 1. Go to line number **155** and select **var** then press **CTRL+.**
96 |
97 | 
98 |
99 | >**Talking Point**: So, if i wanted to access the one that is here, I can just press CTRL+. thats gonna tell me that I should use the exquisite type instead of "var". This is because my team truly believes that we should always use the explicit type instead of "var" to understand and for readability. If I want to actually apply this, I can just press Enter and now all my code here is in style.
100 |
101 | 2. Press **CTRL+T** and search for **editorconfig**.
102 |
103 | 
104 |
105 | >**Talking Point**: Infact, Visual Studio 2017 supports coding conventions by allowing your team to configure your own team preferences and enforce however they want inside the editor with the editor config file.
106 | Editor config is an open-source file format and we have worked with their community to have it work with .NET code style as well. If i scroll down here, you can see here are "var" preferences for my team. You can see that we choose to not prefer "var" and that if you do violate this rule by using the "var", it will trigger suggestion inside the editor to fix it.
107 | Alternatively, I could have made it a warning or an error if I want existing code style everywhere. I will just keep this as a suggestion for now. Also, building on top of this, you can define your own naming conventions in editor config.
108 | So, if I investigate what is going on here, you can see that i have violated my team's naming convention and this one is being used Pascal's case for methods so that with a single click I can now make my code adhere to my team's code style.
109 |
110 |
111 | ## Demo 4: C# 7 New Language features( Tuples)
112 |
113 | Not only all my code suggestions are great helping drive consistency across the repository, but also they are great for teaching new language features. Perhaps,most exciting language feature coming in C#7 is **Tuple**. Tuples allow you to return multiple values for methods so you dont have to juggle out parameters.
114 |
115 | 1. Go to **Athlete.cs** file. You can see here that i am returning both workout and double. I am consuming it down here and then accessing Tuple elements with their default names of **Item1** and **Item2**. If you look close, you can see I am getting a code suggestion here, so lets investigate it.
116 |
117 | 
118 |
119 | 
120 |
121 | >**Talking Point**: You can see that how we need to use the explicit tuple name rather than its default name of Item1 and Item2.
122 | So, i can quickly apply this text and improve the readability of my code. If you remember when i was adding a no-check earlier, you may have noticed that a code suggestion is available there.
123 |
124 | 2. Quickly navigate to the suggestion and apply. You should now see the explicitly provided tuple name here.
125 |
126 | 
127 |
128 | 
129 |
130 | 3. If you remember when i was adding a no-check earlier, you may have noticed that a code suggestion is available there. Go to **BikeWorkOut.cs** file and to the line number **20**, you can see the code suggestion here.
131 |
132 | 
133 |
134 | 4. I can see that its telling me to use the **C# 7 throw expression** to help condense my code.
135 |
136 | 
137 |
138 | 5. Once the change is done, you should see as shown below.
139 |
140 | 
141 |
142 | >**Talking Point**: Now that my codebase adheres to my team's code style and i have helped move my code forward by embracing C# 7 language features, I'm almost ready to submit this code for review. The last thing I got to do is refactoring.
143 |
144 | ## Demo 4: Code Refactoring
145 |
146 | Visual Studio 2017 has added a ton of new factoring that help make you more productive. Especially, if you are a developer like me where when i prototype i put all of my types in one file and then later i need to go back and pull them out into their own files. So rather than having cut and paste and add new items to file i can just do this with a single click in Visual Studio 2017.
147 |
148 | 1. You can see here I have a BikeWorkout in my **BikeWorkout.cs** file where i also have DistanceWorkout and i have one other type that i can't quite see. So rather than scroll, I can use now built-in indent lines to see exactly what other type is there.
149 |
150 | 
151 |
152 | 2. To access the refactoring i can just use the same **CTRL+.** that i was using before and if you look here you can see that it is asking me to move my file to a matching name.
153 |
154 | 
155 |
156 | 3. And there you go in a single click, it's gone.
157 |
158 | 
159 |
160 | >**Talking Point**: I can scroll up and do the same with my other type and I have cleaned up my files. I only have a single type that matches the file names that I have and here is where the true power of Live Unit Testing comes in. I have made a major code change, added new files, moved code around and live unit testing figured it out which test to run. So i didn't want to hunt them down in test explorer. It ran them for me without me having to press the button and it updated the icons in the editor so that I dont lose the context of my development.
161 |
162 | These are just some of the new features that we have added in Visual Studio 2017 and we can't wait to hear what you think!
163 |
164 |
165 |
166 |
167 |
168 |
169 |
170 |
171 |
172 |
173 |
174 |
175 |
176 |
177 |
178 |
179 |
180 |
181 |
182 |
183 |
184 |
185 |
186 |
187 |
188 |
189 |
190 |
--------------------------------------------------------------------------------
/Visual Studio Mobile Center/media/MobileCenter.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/Visual Studio Mobile Center/media/MobileCenter.png
--------------------------------------------------------------------------------
/Visual Studio Mobile Center/media/image1.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/Visual Studio Mobile Center/media/image1.png
--------------------------------------------------------------------------------
/Visual Studio Mobile Center/media/image10.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/Visual Studio Mobile Center/media/image10.png
--------------------------------------------------------------------------------
/Visual Studio Mobile Center/media/image11.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/Visual Studio Mobile Center/media/image11.png
--------------------------------------------------------------------------------
/Visual Studio Mobile Center/media/image12.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/Visual Studio Mobile Center/media/image12.png
--------------------------------------------------------------------------------
/Visual Studio Mobile Center/media/image13.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/Visual Studio Mobile Center/media/image13.png
--------------------------------------------------------------------------------
/Visual Studio Mobile Center/media/image14.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/Visual Studio Mobile Center/media/image14.png
--------------------------------------------------------------------------------
/Visual Studio Mobile Center/media/image15.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/Visual Studio Mobile Center/media/image15.png
--------------------------------------------------------------------------------
/Visual Studio Mobile Center/media/image16.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/Visual Studio Mobile Center/media/image16.png
--------------------------------------------------------------------------------
/Visual Studio Mobile Center/media/image17.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/Visual Studio Mobile Center/media/image17.png
--------------------------------------------------------------------------------
/Visual Studio Mobile Center/media/image18.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/Visual Studio Mobile Center/media/image18.png
--------------------------------------------------------------------------------
/Visual Studio Mobile Center/media/image19.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/Visual Studio Mobile Center/media/image19.png
--------------------------------------------------------------------------------
/Visual Studio Mobile Center/media/image2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/Visual Studio Mobile Center/media/image2.png
--------------------------------------------------------------------------------
/Visual Studio Mobile Center/media/image20.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/Visual Studio Mobile Center/media/image20.png
--------------------------------------------------------------------------------
/Visual Studio Mobile Center/media/image21.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/Visual Studio Mobile Center/media/image21.png
--------------------------------------------------------------------------------
/Visual Studio Mobile Center/media/image22.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/Visual Studio Mobile Center/media/image22.png
--------------------------------------------------------------------------------
/Visual Studio Mobile Center/media/image23.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/Visual Studio Mobile Center/media/image23.png
--------------------------------------------------------------------------------
/Visual Studio Mobile Center/media/image24.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/Visual Studio Mobile Center/media/image24.png
--------------------------------------------------------------------------------
/Visual Studio Mobile Center/media/image25.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/Visual Studio Mobile Center/media/image25.png
--------------------------------------------------------------------------------
/Visual Studio Mobile Center/media/image26.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/Visual Studio Mobile Center/media/image26.png
--------------------------------------------------------------------------------
/Visual Studio Mobile Center/media/image27.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/Visual Studio Mobile Center/media/image27.png
--------------------------------------------------------------------------------
/Visual Studio Mobile Center/media/image28.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/Visual Studio Mobile Center/media/image28.png
--------------------------------------------------------------------------------
/Visual Studio Mobile Center/media/image29.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/Visual Studio Mobile Center/media/image29.png
--------------------------------------------------------------------------------
/Visual Studio Mobile Center/media/image3.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/Visual Studio Mobile Center/media/image3.png
--------------------------------------------------------------------------------
/Visual Studio Mobile Center/media/image30.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/Visual Studio Mobile Center/media/image30.png
--------------------------------------------------------------------------------
/Visual Studio Mobile Center/media/image31.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/Visual Studio Mobile Center/media/image31.png
--------------------------------------------------------------------------------
/Visual Studio Mobile Center/media/image32.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/Visual Studio Mobile Center/media/image32.png
--------------------------------------------------------------------------------
/Visual Studio Mobile Center/media/image33.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/Visual Studio Mobile Center/media/image33.png
--------------------------------------------------------------------------------
/Visual Studio Mobile Center/media/image34.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/Visual Studio Mobile Center/media/image34.png
--------------------------------------------------------------------------------
/Visual Studio Mobile Center/media/image35.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/Visual Studio Mobile Center/media/image35.png
--------------------------------------------------------------------------------
/Visual Studio Mobile Center/media/image36.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/Visual Studio Mobile Center/media/image36.png
--------------------------------------------------------------------------------
/Visual Studio Mobile Center/media/image4.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/Visual Studio Mobile Center/media/image4.png
--------------------------------------------------------------------------------
/Visual Studio Mobile Center/media/image5.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/Visual Studio Mobile Center/media/image5.png
--------------------------------------------------------------------------------
/Visual Studio Mobile Center/media/image6.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/Visual Studio Mobile Center/media/image6.png
--------------------------------------------------------------------------------
/Visual Studio Mobile Center/media/image7.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/Visual Studio Mobile Center/media/image7.png
--------------------------------------------------------------------------------
/Visual Studio Mobile Center/media/image8.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/Visual Studio Mobile Center/media/image8.png
--------------------------------------------------------------------------------
/Visual Studio Mobile Center/media/image9.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/Visual Studio Mobile Center/media/image9.png
--------------------------------------------------------------------------------
/Visual Studio Mobile Center/readme.md:
--------------------------------------------------------------------------------
1 | # Visual Studio Mobile Center
2 |
3 |
4 | 
5 |
26 |
27 | >**Talking Point**: I am now logging in with my GitHub account. No need to register for a new service, or to remember a new login and password.
28 |
29 | 2. You should see the Dashboard as shown below.
30 |
31 |
32 |
33 | >**Talking Point**: Once I login, I can see all the apps that my team has been working on.
34 |
35 | 3. Click on **BikeRider app**.
36 |
37 |
38 |
39 | >**Talking Point**: Let's have a look at the BikeRider app in Mobile Center.
40 |
41 | 4. Scroll on the **Overview** page.
42 |
43 |
44 |
45 | >**Talking Point**: In the overview page I am being presented with a few easy steps about how to integrate the open source Mobile Center SDK. With only a few lines of code, the app collects crash reports and usage data. As we were working on this app, every time somebody pushes a change in the BikeRider repository, we automatically build it, distribute it to ourselves for testing, and run a suite of UI tests to make sure the most important flows are working.
46 |
47 | 5. Click on **distribution**.
48 |
49 |
50 |
51 | >**Talking Point**: To manage the testers, I have grouped them into distribution groups.
52 |
53 | 6. Click on **alpha team**.
54 |
55 |
56 |
57 | >**Talking Point**: The alpha team are the devs that should test each new version. I can manually distribute releases to them by uploading the binary, but I want to show you the real power of our services: automatically distributing builds upon each checkin.
58 |
59 | 7. Click on **Build**.
60 |
61 |
62 |
63 | >**Talking Point**: Since I’m connected with GitHub, Mobile Center already knows about my repositories, branches and project configurations.
64 |
65 | 8. Click on **Seattle branch**.
66 |
67 |
68 |
69 | >**Talking Point**: For the Seattle feature branch, we built the app and distributed each build to the alpha team.
70 |
71 | 9. Click on **Settings (top right) - and scroll as you talk**.
72 |
73 |
74 |
75 | >**Talking Point**: When setting this up, all I had to do was to select the right configurations from the dropdown, upload the signing files and select the alpha team for distribution.
76 |
77 | 10. Close **configuration**.
78 |
79 | 11. Click on a **build (succeeded)**.
80 |
81 |
82 |
83 | >**Talking Point**: It only took a few clicks to set up Continuous Integration for this app. Mobile Center runs all builds in our Mac cloud, and you – mobile app developers – no longer have to worry about providing your own Mac hardware for automated builds. No matter how eager testers are to validate they app, they cannot cover all the device combinations and Operating Systems existent out in the wild.
84 |
85 | 12. Click on **test tab**.
86 |
87 |
88 |
89 | >**Talking Point**: Here in the test section – are all the UI tests that have been executed for this app.
90 |
91 | 13. Click** on **last test run**.
92 |
93 |
94 |
95 | >**Talking Point**: The last tests ran on 28 devices – and consists of three simple tests to validate basic flows.
96 |
97 | 14. Click on a **test**.
98 |
99 |
100 |
101 | >**Talking Point**: The tests were run on real iPhones.
102 |
103 | 15. Click on a **phone**.
104 |
105 |
106 |
107 | >**Talking Point**: You can see exactly how the app looks like on the devices, whether tests are passing, and even get detailed logs and performance data. We believe that testing and automated UI testing is so important for delivering that 5\* experience. We host thousands of devices in our data center – all you have to do is to write your tests and upload them to us. We take care of the rest.
108 |
109 |
110 | **So far, I showed you how we used Mobile Center to enable fast iterations cycle. Once we distribute the app to more customers, we want to learn from the app's usage and fix issues as they arise.**
111 |
112 | 16. Click On **BikeRider - Production**.
113 |
114 |
115 |
116 | >**Talking Point**: Let's have a look at a different version of the same app that has been used in production in the last few months and for which the SDK has been collecting data.
117 |
118 | 17. Click on **crashes**.
119 |
120 |
121 |
122 | >**Talking Point**: My app is doing pretty well - 96% of the users never experienced a crash. Unfortunately, there are still a few crashes that my users are facing. Mobile Center groups similar crash reports into crash groups, and makes it easy for developers to identify the most important issues.
123 |
124 | 18. Click on a **crash group**.
125 |
126 |
127 |
128 | >**Talking Point**: If I look into a crash group, I can see how many users were affected, on which devices and operating systems the crash happened, and even the detailed stack trace. As important as learning about the issues users are facing, is learning about how the app is being used.
129 |
130 | 19. Click on **analytics**.
131 |
132 |
133 |
134 | >**Talking Point**: And here is where the analytics part of Mobile Center comes into play. I can see here how many people are using the BikeRider app, how often they use it – and for how long. When I look into the device section – seems like many of my users are using an iPhone 6S – and list of countries and on what languages they are using their phone.
135 |
136 | 20. Click on **events**.
137 |
138 |
139 |
140 | >**Talking Point**: The SDK was also used to track events. Developers can find out how many people use a feature, how often, and even how the feature usage evolves over time.
141 |
142 | 21. Click on a **BookRide** event and scroll down to **properties**.
143 |
144 |
145 |
146 | >**Talking Point**: Let's look for instance into how people book rides – not only I can find out how the feature is being used and its growth, but if I dig into properties I can see that people don't use suggestions and the events feature as much as we expected when launching them. I love when I get all of these insights by adding only a few lines of code in the app.
147 |
148 | 22. Click on **tables**.
149 |
150 |
151 |
152 | >**Talking Point**: Finally, there’s one more part of Mobile Center I want to show you. Every great app needs a great backend. Azure provides a great backend with tons of customization options. For smaller apps and prototyping, the Tables and Identity services of Mobile Center give you easy access to Azure table storage and authentication.
153 |
154 |
155 |
156 | >**Talking Point**: Let's have a look at how this would look like. I can see here in the tables section, a few tables for the bike rides and users – and how this table looks like. This makes it so easy to get started with your app's backend.
157 | Mobile Center brings to you – mobile developers – all the services you need to develop, ship and maintain beautiful mobile apps. You can now automatically build your app in our hosted cloud, run UI tests on real devices managed by us and distribute releases to your testers. To learn from your users, all you have to do is drop the Mobile Center SDK in your app. You can then learn about issues your users are facing and how exactly they are using your app when it is out in the wild. Mobile Center is Mission control for your mobile app – all you need in a single service.
158 |
159 | ## Old Demo (Connect 2016)
160 |
161 |
162 |
163 | >**Talking Point**: Mobile Center is the mission control for mobile apps I’ve always wanted. It brings all of the mobile services I need together in one place. I’ll log in with my GitHub, and right away I see all of the apps I’m working on.
164 |
165 | 
166 |
167 | 
168 |
169 | 
170 |
171 | >**Talking Point**: Before jumping into a production app, let me show you how easy it is to get started with your own app. I logged in with GitHub, so I can quickly choose the repo that contains my app. In this case I’ll choose the Ride360 client app that you’ve seen today. I just need to tell Mobile Center that this is a Xamarin app.
172 |
173 | 
174 |
175 | >**Talking Point**: I’m given the option to run the tests with Test Cloud, UI testing on real devices.
176 |
177 | 
178 |
179 | >**Talking Point**: Finally I can add some beta testers to receive builds of my app, let me add some of my collegues' emails.
180 |
181 | 
182 |
183 | >**Talking Point**: Alright! We’ve connected to a repo and created an app. I see some easy getting started instructions for adding the Mobile Center SDK to my app, and inline C\# snippets for initialization. On the left, you see all of the services Mobile Center brings together. Let’s start with Build.
184 |
185 | 
186 |
187 | 
188 |
189 | >**Talking Point**: Here are the branches in the repo I just connected, and we can see the master branch has its first build in progress. We’re getting live feedback as the build completes and BOOM, its done.
190 |
191 | 
192 |
193 | >**Talking Point**: Remember the tests we enabled when we connected this repo? This build is already being tested on real devices in the Test service. We can see that the simple test is already completed. It’s never been easier to start testing your apps on real devices.
194 |
195 | 
196 |
197 | >**Talking Point**: Finally, let’s see the distribution service. Here are the collaborators I added when I created the app, and I can see they’ve been emailed a link to install the app we just built and tested. You can even see which commit triggered the distribution.
198 |
199 | 
200 |
201 | >**Talking Point**: To show you Crashes and Analytics, I’m going to switch tabs to a production app. These are the crash reports for the live Ride360 client app on iOS. Mobile Center has the amazing crash grouping and information that customers loved in Xamarin Insights and HockeyApp. Crashes are grouped by root cause so you can diagnose and resolve them quickly.
202 |
203 | 
204 |
205 | >**Talking Point**: Since we’re looking at a production app, we can see the developer-friendly analytics we collect merely by integrating the Mobile Center SDK.
206 |
207 | 
208 |
209 | >**Talking Point**: Finally, there’s one more app service I want to show you. Every app needs a great backend, so Mobile Center makes connecting to the cloud easy as well. Our Table and Identity services give you easy access to Azure table storage and authentication. These are live tables powering our apps, and we can see as they are read and written to from clients. Mobile Center makes mobile devops more approachable than ever, and helps developers power their apps with Azure.
210 |
211 |
212 |
213 |
214 |
215 |
216 |
217 |
218 |
219 |
220 |
221 |
222 |
223 |
224 |
225 |
226 |
--------------------------------------------------------------------------------
/XamarinCycle9/media/1.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/1.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/10.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/10.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/11.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/11.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/12.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/12.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/13.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/13.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/14.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/14.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/15.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/15.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/16.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/16.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/17.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/17.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/18.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/18.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/19.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/19.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/2.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/20.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/20.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/21.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/21.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/22.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/22.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/23.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/23.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/24.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/24.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/25.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/25.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/26.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/26.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/27.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/27.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/28.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/28.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/29.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/29.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/3.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/3.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/30.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/30.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/31.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/31.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/32.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/32.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/33.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/33.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/34.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/34.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/35.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/35.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/36.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/36.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/37.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/37.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/38.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/38.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/39.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/39.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/4.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/4.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/40.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/40.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/41.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/41.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/42.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/42.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/43.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/43.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/44.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/44.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/45.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/45.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/46.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/46.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/47.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/47.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/48.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/48.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/49.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/49.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/5.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/5.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/50.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/50.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/51.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/51.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/52.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/52.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/53.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/53.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/54.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/54.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/55.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/55.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/56.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/56.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/57.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/57.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/58.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/58.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/59.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/59.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/6.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/6.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/60.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/60.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/61.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/61.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/62.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/62.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/63.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/63.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/64.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/64.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/65.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/65.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/66.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/66.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/67.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/67.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/68.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/68.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/69.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/69.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/7.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/7.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/70.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/70.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/71.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/71.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/72.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/72.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/73.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/73.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/74.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/74.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/75.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/75.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/76.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/76.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/77.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/77.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/78.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/78.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/79.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/79.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/8.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/8.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/80.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/80.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/81.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/81.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/82.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/82.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/9.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/9.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/VS_Options.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/VS_Options.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/VS_Tools-Options.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/VS_Tools-Options.png
--------------------------------------------------------------------------------
/XamarinCycle9/media/VSandXamarin.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/microsoft/VisualStudio2017Launch_KeynoteDemos/9d9bb3ed4936b6d2b1ffee8a2262d86f643cd1b0/XamarinCycle9/media/VSandXamarin.png
--------------------------------------------------------------------------------