Channel 9

This video demonstrates how Visual Studio 2017 makes it easier to be more productive than ever as you create modern web applications. Download Visual Studio 2017 and select the "Web Development" workload

A quick overview of some of the new language features coming to C# 7.0. For more details see our blog post.

Visual Studio Application Insights is an extensible, intelligent application performance-management service for web developers, providing fast analytics and integration with your existing DevOps workflows. This video demonstrates how you can use Application Insights to detect and interactively diagnose performance problems and answer complex questions about usage and performance. Get started for free: http://aka.ms/AIGetStarted

Published on Sep 26, 2016http://CppCon.orgPresentation Slides, PDFs, Source Code and other presenter materials are available at: https://github.com/cppcon/cppcon2016Lifetime safety means writing code that, by construction, is guaranteed to eliminate two things: (a) use of null/dangling pointers (including pointerlike things such as references, iterators, views, and ranges), and (b) leaks (including the rare 1% case where we're tempted to admit the possibility of an ownership cycle or need to support lock-free concurrent data structures).Last year, my CppCon 2015 talk "Writing Good C++14... By Default" focused on (a), null/dangling, because it's the more difficult and usually more serious problem. I gave an overview of a new approach of using static analysis rules to eliminate use of null and dangling in C++. That work continues and we're in the process of writing down the formal rules for the approach that I showed last year.This year, the focus will be on (b), leaks: The talk aims to begin with a set of simple rules, the "5-minute talk" to demonstrate that a handful of rules can be taught broadly to programmers of all levels, and results in code that is clean and free of leak bugs by construction.But, since we'll still have 85 minutes left, we can use the time to spelunk through a series of "Appendix" code examples, in which we'll demonstrate "why and how" to apply those rules to a series of increasingly complex/difficult situations, and that are aimed at increasingly advanced and "clever" (note: not always a good thing) programs and programmers. We'll address questions such as: How should we represent Pimpl types? How should we represent trees – what should the child and parent pointer types be, and (when) should they be unique and when shared? How should we deal with "intra-module" or "encapsulated" cycles when you control all the objects in the cycle, such as all the nodes within a Graph? And what about "inter-module" or "compositional" cycles when you don't know in advance about all the objects that could be in the cycle, such as when combining libraries written by different people in a way that may or may not respect proper layering (notoriously, using callbacks can violate layering)? The answers focus on cases where we have solid guidance, and then move toward some more experimental approaches for potentially addressing the ~1% of cases that aren't yet well covered by unique_ptr, shared_ptr, and weak_ptr.Herb SutterSoftware architect, MicrosoftAuthor, chair of the ISO C++ committee, software architect at Microsoft.Videos Filmed & Edited by Bash Films: http://www.BashFilms.com