WEBVTT 00:00:00.730 --> 00:00:03.340 [Music] 00:00:03.940 --> 00:00:06.750 Thanks for joining us on actually the first ever episode of Breakpoint. 00:00:06.850 --> 00:00:09.450 We're trying something new so hopefully you'll like it. 00:00:09.500 --> 00:00:13.640 >> Yeah, it's pretty exciting. And actually, kind of nerve-wracking 00:00:13.690 --> 00:00:15.530 when we do the first of anything. 00:00:15.580 --> 00:00:16.240 >> Oh, please. 00:00:16.290 --> 00:00:19.430 >> And I'm looking forward to sharing some stuff about Visual 00:00:19.480 --> 00:00:23.170 Studio and Microsoft's ALM platform with everyone out there. 00:00:23.220 --> 00:00:25.400 >> Okay. Now, first of all, before we go into that, I have to 00:00:25.450 --> 00:00:27.450 say how clever is the name Breakpoint? 00:00:27.830 --> 00:00:29.910 >> Breakpoint is an interesting name. 00:00:29.960 --> 00:00:30.060 >> Come on. 00:00:30.110 --> 00:00:35.090 >> It sounds like new vintage of TV series, and I wonder if this 00:00:35.140 --> 00:00:36.450 is going to be a series. 00:00:38.270 --> 00:00:39.830 >> Stay tuned for that. 00:00:39.880 --> 00:00:40.680 >> Maybe. 00:00:40.730 --> 00:00:42.880 >> Ooh, I don't even know if we're allowed doing that on air, 00:00:42.930 --> 00:00:44.440 but he did it, not me. So... 00:00:44.490 --> 00:00:45.280 >> Exactly. 00:00:45.330 --> 00:00:47.930 >> But that's fine. So basically, the point of Breakpoint is actually 00:00:47.980 --> 00:00:52.210 first of all to take a break in your day, ha, ha, get it? 00:00:52.260 --> 00:00:55.360 Anyway, for those of you guys on the east coast with us, we're 00:00:55.410 --> 00:00:58.610 here live from I guess you can call it Toronto. 00:00:58.660 --> 00:00:59.970 Mississauga, I guess. 00:01:00.020 --> 00:01:00.340 >> Mississauga. 00:01:00.390 --> 00:01:04.510 >> I call it Toronto. Whatever. And for those of you guys on 00:01:04.560 --> 00:01:07.530 the west coast, it's take time for some breakfast, grab a cup 00:01:07.580 --> 00:01:10.760 of coffee. Let's talk Visual Studio. Let's talk about... 00:01:10.810 --> 00:01:12.360 today we're talking about ALM, actually. 00:01:12.410 --> 00:01:16.440 >> Visual Studio ALM. But really, what parts of Visual Studio 00:01:16.490 --> 00:01:19.030 aren't affected by the lifecycle. 00:01:19.080 --> 00:01:22.000 >> Now, so interesting enough, before we actually go into this, 00:01:22.050 --> 00:01:25.220 just for a quick little point there in the chat, how many of 00:01:25.270 --> 00:01:28.980 you actually saw the launch last week? Because that was awesome. 00:01:29.030 --> 00:01:29.570 >> Me, me. 00:01:29.620 --> 00:01:33.280 >> Right, the entire time I'm sitting there, and I'm like holy smokes. 00:01:33.330 --> 00:01:33.540 >> Yeah. 00:01:33.590 --> 00:01:35.790 >> And then I'm like okay, so I was taking some notes, and then 00:01:35.840 --> 00:01:39.550 okay, wow, another feature. What? Okay. Let's take some more notes. 00:01:39.600 --> 00:01:43.010 And then they throw out Visual Studio online, and I'm like... 00:01:44.200 --> 00:01:47.470 >> You know, and that stuff is great, because it impacts every 00:01:47.520 --> 00:01:51.540 type of developer out there, whether you're an individual developer, 00:01:51.590 --> 00:01:54.210 a hobbyist enthusiast, the stuff you can do with Visual Studio 00:01:54.260 --> 00:01:56.990 online all the way up to the biggest companies can make use of it. 00:01:57.040 --> 00:01:59.580 >> Now, of course, the down side to that, and I've had this come 00:01:59.630 --> 00:02:01.580 to me a couple of times when there was a little bit of talk, 00:02:01.630 --> 00:02:03.910 you know, everything's going to the cloud, blah, blah, blah. 00:02:04.700 --> 00:02:07.170 You have those guys who are like well, you know, every once in 00:02:07.220 --> 00:02:11.460 a while, we used the excuse that we don't have access to our 00:02:11.510 --> 00:02:14.500 tools, and now you can't use that anymore so now it's kind of 00:02:14.550 --> 00:02:18.170 like well, now you can do your job anywhere. So your boss calls 00:02:18.220 --> 00:02:20.270 you up and says hey, I have a late-breaking fix. You've got 00:02:20.320 --> 00:02:21.540 to get this in now. 00:02:22.190 --> 00:02:26.460 We can't really say anymore, well, I don't have access to Visual Studio. 00:02:26.980 --> 00:02:27.750 Because now you can. 00:02:27.800 --> 00:02:31.600 >> Yeah, you'd have to like basically cut your network cable and 00:02:31.650 --> 00:02:35.250 take your wireless router offline. And remove your cell phone 00:02:35.300 --> 00:02:38.160 from proximity. It's pretty wild. I mean, my... 00:02:38.940 --> 00:02:41.520 you know, I'm taking a datacenter with me everywhere I go. 00:02:41.570 --> 00:02:45.960 I always have access, no matter where I am to my back-end infrastructure 00:02:46.010 --> 00:02:47.960 and the tools I need to make them sync. 00:02:48.010 --> 00:02:50.580 >> He's saying this to the cloud guy. This is what I live and 00:02:50.630 --> 00:02:53.190 breathe with. But anyway, so enough of that. 00:02:53.240 --> 00:02:56.720 >> Jonathan's always been up in the cloud. 00:02:56.770 --> 00:02:59.340 >> Oh, boy. So this is going to be a little bit difficult for us. 00:02:59.390 --> 00:03:02.390 But last but not least, before we get started, remember this 00:03:02.440 --> 00:03:06.020 is, in fact, a live show so I have this chat screen open here. 00:03:06.070 --> 00:03:09.410 We already have some messages in there from, hey, from Ottawa. 00:03:09.460 --> 00:03:14.700 Hi. But point being as Adam and I are banting back and forth, 00:03:14.750 --> 00:03:18.870 ranting back and forth, demoing back and forth, post your questions. 00:03:18.920 --> 00:03:22.020 This way, you can get the answers that you want direct from us 00:03:22.070 --> 00:03:25.830 and if you're watching this online afterwards, on demand, just 00:03:25.880 --> 00:03:27.980 post the comments underneath the video and we'll get back to 00:03:28.030 --> 00:03:31.830 you, or you can tweet or LinkedIn or Facebook, whatever it is 00:03:31.880 --> 00:03:34.120 and we'll have all the details for you anyway. 00:03:34.170 --> 00:03:37.490 >> Absolutely. And if you don't get a chance to ask your questions 00:03:37.540 --> 00:03:40.650 today or you think of something that you forgot to ask and you 00:03:40.700 --> 00:03:43.200 happen to be in Toronto or Montreal... 00:03:43.250 --> 00:03:45.460 >> Adam's going to buy you a beer... I mean coffee. 00:03:45.510 --> 00:03:49.760 >> I don't, I don't... I was going to say please come out to the 00:03:49.810 --> 00:03:53.110 Visual Studio launch events that we're running both in Toronto 00:03:53.160 --> 00:03:57.760 and in Montreal December 4th and 5th. We are so fortunate to have... 00:03:57.810 --> 00:03:58.600 >> That's true.... 00:03:58.650 --> 00:04:02.490 >> a new addition to the Microsoft developer tools team, Claude 00:04:02.890 --> 00:04:06.860 Remillard, who is originally a Canuck by nature. He's from Montreal, 00:04:07.430 --> 00:04:11.310 and responsible for our new Visual Studio release management tooling. 00:04:11.360 --> 00:04:13.180 He's going to be the presenter there. 00:04:13.230 --> 00:04:15.300 >> So I think we're going to have to get him on the show at one 00:04:15.350 --> 00:04:15.750 point also. 00:04:15.800 --> 00:04:19.450 >> I think so. And I'm going to do a poor man's job of showing 00:04:19.500 --> 00:04:20.400 some of that today. 00:04:21.140 --> 00:04:23.480 >> He says this, but you guys are going to have an awesome time. 00:04:23.530 --> 00:04:26.980 Last but not least, actually, for more of those launch events, 00:04:27.030 --> 00:04:29.390 there's actually user groups all across the country that are 00:04:29.440 --> 00:04:32.790 also doing Visual Studio launch events. So make sure you go 00:04:32.840 --> 00:04:36.330 to plancast.com/cdndevs and you'll get all the listings of all 00:04:36.380 --> 00:04:39.080 the user groups across the country that are bringing the goodness 00:04:39.130 --> 00:04:40.710 of Visual Studio to country. 00:04:40.760 --> 00:04:43.930 >> And there is so much new in Visual Studio that we're not going 00:04:43.980 --> 00:04:46.660 to talk about today because it's... we're going to... 00:04:46.710 --> 00:04:47.320 >> Today is about ALM. 00:04:47.370 --> 00:04:50.250 >> But, you know, it just blows me away as a developer myself, 00:04:50.300 --> 00:04:53.530 as kind of a closet developer, because when people see my code, 00:04:53.580 --> 00:04:55.660 they put me in a closet and lock the door. 00:04:56.610 --> 00:05:00.950 There's just so much awesome stuff that isn't necessarily related 00:05:01.000 --> 00:05:02.930 to what we're going to talk about today that... 00:05:02.980 --> 00:05:04.130 >> Okay. So hold on a second. 00:05:04.180 --> 00:05:07.330 >> Go to the user group meetings and find out the stuff. 00:05:07.380 --> 00:05:08.740 >> Okay. So last cheesy joke. 00:05:08.790 --> 00:05:09.130 >> Yeah. 00:05:09.180 --> 00:05:12.400 >> In your closet code, do you have a lot of breakpoints? 00:05:13.990 --> 00:05:15.560 >> Wow, okay. Let's move on. 00:05:16.270 --> 00:05:20.270 >> On that note, ALM, Visual Studio. Adam, please, take it away 00:05:20.320 --> 00:05:20.970 by all means. 00:05:21.020 --> 00:05:21.370 >> Beautiful. 00:05:21.420 --> 00:05:26.950 So we as a product group and I kind of, you know, I don't get 00:05:27.000 --> 00:05:30.780 paid to work in Redmond on writing Visual Studio and you should 00:05:30.830 --> 00:05:34.610 all be very thankful of that. I get the pleasure of actually 00:05:34.660 --> 00:05:37.420 using these tools and seeing the evolution of what we've been 00:05:37.470 --> 00:05:41.590 doing with the Visual Studio platform for software development. 00:05:42.040 --> 00:05:46.200 And the product group has really been focused on a vision that's 00:05:46.250 --> 00:05:48.040 going to take a few years 00:05:49.290 --> 00:05:53.560 to deliver on, and that is the ability to deliver these new modern 00:05:53.610 --> 00:05:58.260 business apps with a modern approach to help you deliver those 00:05:58.310 --> 00:06:00.140 apps faster and better. 00:06:00.690 --> 00:06:03.620 Whether that is... oh, you want me to look at the screen. 00:06:03.670 --> 00:06:07.370 >> I sure do. Because I'm not on it right now. 00:06:07.420 --> 00:06:09.430 >> Okay. So I shouldn't be talking to you. I should be talking 00:06:09.480 --> 00:06:10.100 to you. 00:06:10.150 --> 00:06:10.900 >> Correct. 00:06:11.230 --> 00:06:12.220 >> Live rocks. 00:06:13.100 --> 00:06:17.580 So whether you're doing planning, development, you're validating 00:06:17.630 --> 00:06:20.560 the application, you're a taskster, you're an operations or release 00:06:20.610 --> 00:06:24.060 management, we have a whole new series of types of applications 00:06:24.110 --> 00:06:29.040 that we're building for our users that are architecturally very 00:06:29.090 --> 00:06:32.540 different than things we've traditionally built, where we might 00:06:32.590 --> 00:06:35.210 not know, for example, the type of device that's going to consume 00:06:35.260 --> 00:06:38.290 the app, or even the platform that's going to be used to consume 00:06:38.340 --> 00:06:41.610 the app. We have to take that into account. And at the same 00:06:41.660 --> 00:06:45.260 time, as we're doing that, we need to figure out how we do that 00:06:45.310 --> 00:06:50.170 faster and better, because users are demanding more experiences faster. 00:06:50.590 --> 00:06:55.300 So taking an approach to development that can increase your ability 00:06:55.350 --> 00:06:59.920 to deliver faster is pretty important. And we're also focused 00:06:59.970 --> 00:07:04.110 on taking the tools that we've worked on for a long time, like 00:07:04.160 --> 00:07:08.400 Team Foundation Server and looking at scenarios where we can 00:07:08.450 --> 00:07:11.960 enhance your ability pretty dramatically by bringing some of 00:07:12.010 --> 00:07:14.450 our online properties to play. And we'll look at that today, 00:07:14.500 --> 00:07:19.280 things like load testing. Things like load testing are really, 00:07:19.330 --> 00:07:22.140 really expensive to set up on premises, because you have to set 00:07:22.190 --> 00:07:23.340 up infrastructure. 00:07:23.880 --> 00:07:28.300 It takes time to schedule things. It impacts your existing network. 00:07:28.350 --> 00:07:32.330 Well, that's a perfect scenario for us to extend our lifecycle 00:07:32.380 --> 00:07:36.670 management tooling and processes to leverage cloud scenarios 00:07:36.720 --> 00:07:39.520 to help you do that much more easily. So I'm going to actually 00:07:39.570 --> 00:07:41.710 show that today to the folks in the room. 00:07:41.760 --> 00:07:43.070 >> Da-da-da. Here we go. 00:07:44.840 --> 00:07:47.480 >> We really also focus, and it's been our mission for a long 00:07:47.530 --> 00:07:51.820 time, to deliver lifecycle management tools your way. Allow you 00:07:51.870 --> 00:07:55.400 to approach the tools in a way that makes sense for your business 00:07:55.450 --> 00:07:59.350 and not necessarily force you to do the work the way we say you 00:07:59.400 --> 00:08:02.450 should do the work. And that's really important for customers. 00:08:02.500 --> 00:08:07.040 You can kind of adopt the tooling in a way that makes sense. 00:08:07.090 --> 00:08:09.970 For example, you see a lot... today, I'm going to show you some 00:08:10.020 --> 00:08:13.230 of the new Agile planning tools. Well, you know that's pretty 00:08:13.280 --> 00:08:16.810 scary if an organization isn't adopting Agile right away for 00:08:16.860 --> 00:08:18.350 lots of various reasons. 00:08:19.020 --> 00:08:23.340 What we've done is we've made the Agile planning tools applicable 00:08:23.990 --> 00:08:29.030 to every type of process or work flow that you want to use. 00:08:29.080 --> 00:08:33.880 So you don't have to adopt Agile all in one go. You can take 00:08:33.930 --> 00:08:37.610 the tools and the process says make the most sense. We've surrounded 00:08:37.660 --> 00:08:41.480 that with a lot of capabilities to help you work as a team and 00:08:41.530 --> 00:08:45.860 collaborate better. Things like Team Rooms that give you a lot 00:08:45.910 --> 00:08:48.080 of information about what's happened on the project. If you 00:08:48.130 --> 00:08:51.600 go away for a week and you come back, what did the team do during 00:08:51.650 --> 00:08:54.690 the week? Help me get up to speed. Be able to work with your 00:08:54.740 --> 00:08:58.650 stakeholders and get feedback from them that you can take action 00:08:58.700 --> 00:09:00.640 on in a much more... 00:09:01.560 --> 00:09:02.940 a much quicker way. 00:09:04.070 --> 00:09:07.900 And all of this is surrounded by integration with enterprise 00:09:07.950 --> 00:09:12.120 systems that you might want to leverage if you have System Center. 00:09:12.170 --> 00:09:15.140 There's great integration there. If you have... if you want 00:09:15.190 --> 00:09:18.310 to do load testing, if you have project server, if you want to 00:09:18.360 --> 00:09:22.390 use virtualizations to take care of testing labs, that's pretty 00:09:22.440 --> 00:09:23.330 powerful stuff. 00:09:23.380 --> 00:09:24.230 >> So I have a question for you. 00:09:24.280 --> 00:09:25.100 >> Sure, J.R. 00:09:25.150 --> 00:09:28.290 >> Because a lot of times, what happens when is we talk about 00:09:28.340 --> 00:09:30.610 ALM and we say it's ALM Your Way and stuff like that... 00:09:30.660 --> 00:09:32.700 >> What is ALM, by the way? What does it mean to you? 00:09:32.750 --> 00:09:34.460 >> Wow, that's a very good question. 00:09:34.510 --> 00:09:35.620 >> That's a good question for you. 00:09:35.670 --> 00:09:38.380 >> That's actually not what I was going to ask. But, okay, we'll 00:09:38.430 --> 00:09:39.000 work with that. 00:09:39.050 --> 00:09:39.340 >> Okay. 00:09:39.390 --> 00:09:42.230 >> So first of all, yes, question is what ALM means to each person, 00:09:42.280 --> 00:09:45.350 number one, because that is, to me, I think it's the biggest 00:09:45.400 --> 00:09:48.800 one of those things where, you know, it's like calling HD everything. 00:09:48.850 --> 00:09:51.820 Everything's high definition, everything's ALM. But where a 00:09:51.870 --> 00:09:54.760 lot of concerns come in is when here we are, we're saying ALM 00:09:54.810 --> 00:09:55.900 Your Way, but 00:09:57.850 --> 00:10:03.270 in previous iterations of this, it wasn't as customized to what 00:10:03.320 --> 00:10:07.720 we could actually do or what someone could actually choose to implement. 00:10:07.770 --> 00:10:12.730 So in new world, is it actually ALM? Like I can pick and choose 00:10:12.780 --> 00:10:15.460 blocks of different pieces of the process and implement them, 00:10:15.510 --> 00:10:18.510 or I have to do, like, the full-out ALM? 00:10:18.560 --> 00:10:22.590 >> Well, you know, TFS still installs and you still install the 00:10:22.640 --> 00:10:25.940 entire server. That's always been the way it has with TFS, and 00:10:25.990 --> 00:10:29.560 that continues to be the case. Whether you choose to do a TFS 00:10:29.610 --> 00:10:33.670 implementation on premises or you use the new Visual Studio online 00:10:33.720 --> 00:10:35.460 capabilities that... 00:10:36.360 --> 00:10:41.160 where we host that for you, you still have all of the capabilities there. 00:10:41.210 --> 00:10:43.340 But you don't have to implement everything. 00:10:43.880 --> 00:10:47.000 You don't have to boil the ocean, and that's really important. 00:10:47.050 --> 00:10:50.100 You can pick and choose the technologies that you want to use, 00:10:50.150 --> 00:10:54.080 the capabilities you want to use, and in many cases, you can 00:10:54.130 --> 00:10:57.170 pick the process that makes the most sense for you. If you don't 00:10:57.220 --> 00:11:00.540 want to do Agile, that's okay. If you want to use Scrum, go ahead, 00:11:00.590 --> 00:11:04.390 use Scrum. All of the stuff is in the box and ready for you to adopt. 00:11:05.290 --> 00:11:08.320 Another big thing I know a lot of our customers are trying to 00:11:08.370 --> 00:11:13.420 adopt or tackle building new models of applications on various 00:11:13.470 --> 00:11:17.340 different platforms, not just the Microsoft devices. The browser 00:11:17.390 --> 00:11:21.580 or the phone or Windows 8. You know, there's a reality out there 00:11:21.630 --> 00:11:25.070 that employees at customers that I talk to are bringing their 00:11:25.120 --> 00:11:28.470 iPads to work, and they want to be able to work with those applications 00:11:28.520 --> 00:11:31.820 as well. Well, to develop for that, you have a whole different 00:11:31.870 --> 00:11:32.720 set of tools. 00:11:32.770 --> 00:11:33.250 >> Right. 00:11:33.300 --> 00:11:36.470 >> And we've done some work to make sure that those tools really 00:11:36.520 --> 00:11:40.520 integrate well. If I'm a Java developer building an Android application 00:11:40.570 --> 00:11:44.550 or a J2EE application, I should be able to work with these tools 00:11:44.600 --> 00:11:48.320 seamlessly, and we've done that. For an Xcode developer, someone 00:11:48.370 --> 00:11:52.920 who might be building an app for iOS, we've actually got now 00:11:52.970 --> 00:11:56.350 full get integration in Team Foundation Server, which is pretty cool. 00:11:56.400 --> 00:11:59.580 >> That was a big one, actually, because not everybody wants to 00:11:59.630 --> 00:12:03.840 do TFS for their source codes repository. So now there's the option. 00:12:03.890 --> 00:12:07.420 >> And we actually took the approach of joining the get project. 00:12:07.470 --> 00:12:10.550 So we're a full-fledged get it server implementation. 00:12:10.600 --> 00:12:11.260 >> Nice. 00:12:11.310 --> 00:12:13.820 >> You can synchronize repositories with any... 00:12:14.560 --> 00:12:17.750 you can use any get client against TFS and away you go. So that 00:12:17.800 --> 00:12:22.500 means right from your Xcode IDE, you can access TFS and work 00:12:22.550 --> 00:12:24.940 with the rest of the team and the rest of the tool. So that's 00:12:24.990 --> 00:12:26.360 pretty powerful stuff, I think. 00:12:26.410 --> 00:12:30.050 >> So I think if I come up to my boss now and I say, well, okay, 00:12:30.100 --> 00:12:32.660 so we should definitely go here, and, of course, the number one 00:12:32.710 --> 00:12:35.400 thing I'm going to get is, well, we're not totally a Microsoft 00:12:35.450 --> 00:12:37.660 shop, even though that would be amazing if you were. But we 00:12:37.710 --> 00:12:40.370 can't assume that everybody's a full Microsoft shop. 00:12:41.500 --> 00:12:44.260 Now that's no longer an argument, because you do have all of 00:12:44.310 --> 00:12:46.310 these things that actually just come together and you can do 00:12:46.360 --> 00:12:47.490 ALM across all of them. 00:12:47.540 --> 00:12:48.270 >> That's right. 00:12:49.440 --> 00:12:52.450 We've, you know, this has been a journey for us as we've introduced 00:12:52.500 --> 00:12:55.390 this tooling from back in 2005. 00:12:55.400 --> 00:12:55.880 >> Right. 00:12:55.930 --> 00:12:58.200 >> This is the fifth release of the product and we've moved along 00:12:58.250 --> 00:13:00.720 with feature functionality that applies to everybody. 00:13:02.000 --> 00:13:02.320 >> Okay. 00:13:02.370 --> 00:13:07.210 >> Beg your pardon. And we, you know, I'm not huge on the analysts 00:13:07.610 --> 00:13:10.690 and using that as, you know, kind of a reason to convince somebody 00:13:10.740 --> 00:13:11.750 to use any tool. 00:13:11.800 --> 00:13:15.400 >> No, no, the real reason to convince them, okay, storyboarding 00:13:15.460 --> 00:13:16.090 in PowerPoint. 00:13:16.140 --> 00:13:19.260 >> Wow, storyboarding in PowerPoint is cool. But we got to be 00:13:19.310 --> 00:13:22.620 doing something right if Gartner says we're leading, if Forester 00:13:22.670 --> 00:13:25.960 says we're leading in the ALM tools. That means our completeness 00:13:26.010 --> 00:13:29.880 of vision and our ability to evolve the tools to listen to customers 00:13:29.930 --> 00:13:33.380 and implement means chances, you're going to have the ability 00:13:33.430 --> 00:13:36.640 to do what you want to do with TFS. And the different models 00:13:36.690 --> 00:13:39.230 make it really simple to implement. 00:13:39.280 --> 00:13:41.770 >> So I'm therefore now sold on ALM. 00:13:41.820 --> 00:13:45.500 >> Well, that was my goal, because really, I want you to do ALM 00:13:45.550 --> 00:13:46.540 Your Way on TFS. 00:13:46.590 --> 00:13:50.400 >> Fair enough. Now, let me, you know, if I may continue with 00:13:50.450 --> 00:13:51.130 what I was speaking about... 00:13:51.180 --> 00:13:51.750 >> By all means. 00:13:51.800 --> 00:13:52.830 >> Did I answer your question? 00:13:52.880 --> 00:13:53.360 >> I think so. 00:13:53.410 --> 00:13:53.730 >> Okay, good. 00:13:53.780 --> 00:13:56.390 >> The question is, do you guys have the answer that you guys 00:13:56.440 --> 00:13:59.040 need so that when you have that tough question of, well, we're 00:13:59.090 --> 00:14:02.320 not a Microsoft shop, can we still do ALM our way, hopefully 00:14:02.370 --> 00:14:04.740 you have that answer. But if you need more details... 00:14:04.790 --> 00:14:08.680 >> Absolutely. I talk to customers all the time, and I have customers, 00:14:09.260 --> 00:14:12.070 very large customers that are doing a lot of Java development 00:14:12.120 --> 00:14:16.390 through TFS and are doing multi-platform development with TFS. 00:14:16.440 --> 00:14:19.890 It works very well, and, you know, the reality is Microsoft is 00:14:19.940 --> 00:14:23.230 building a lot of apps that run across multiple platforms and 00:14:23.280 --> 00:14:24.200 guess what we use? 00:14:24.910 --> 00:14:25.700 >> Visual Studio. 00:14:25.750 --> 00:14:28.410 >> Visual Studio and TFS. Amaze, hey? 00:14:28.460 --> 00:14:30.520 >> ALM. We use our own stuff. 00:14:30.570 --> 00:14:31.570 >> And we're doing it our way. 00:14:34.450 --> 00:14:34.860 >> Nice. 00:14:34.910 --> 00:14:35.400 >> Thank you. 00:14:35.450 --> 00:14:38.360 >> Nice. That was a good one. I can't be the only one cracking jokes. 00:14:38.410 --> 00:14:41.660 >> So but let me introduce something that we announced real early, 00:14:41.710 --> 00:14:45.610 because I talked about ALM Your Way and not having to put a whole 00:14:45.660 --> 00:14:48.230 bunch of stuff in your infrastructure to work. What if I'm a 00:14:48.280 --> 00:14:52.130 small team or I have a virtual infrastructure, I'm a startup 00:14:52.180 --> 00:14:55.320 and I've got, you know, a couple of developers or five or ten 00:14:55.370 --> 00:14:58.390 developers, and we're all working from home and occasionally 00:14:58.440 --> 00:15:01.770 we get together at a coffee shop and work together. How do I 00:15:01.820 --> 00:15:05.430 make use of this type of capability without having it. And that's 00:15:05.480 --> 00:15:07.580 where Visual Studio online comes into play. 00:15:07.630 --> 00:15:08.020 >> Nice. 00:15:08.070 --> 00:15:09.360 >> Let me talk a little bit about that. 00:15:09.410 --> 00:15:09.970 >> Let's do it. 00:15:10.020 --> 00:15:13.820 >> All right. So Visual Studio Online is something we introduced 00:15:14.820 --> 00:15:18.920 recently with our launch, and we talked about how we're extending 00:15:19.340 --> 00:15:21.710 our TFS capabilities into the cloud. 00:15:22.470 --> 00:15:25.940 When we launched, we make that available to anybody who wants 00:15:25.990 --> 00:15:29.790 to use it free for up to five users who want to connect in. 00:15:29.840 --> 00:15:33.370 You simply go up to visualstudio.com and sign up for a subscription. 00:15:33.700 --> 00:15:37.550 And what this gives us is a full sort of TFS implementation. 00:15:37.600 --> 00:15:41.070 You can store your source code. You can manage your project delivery 00:15:41.120 --> 00:15:44.800 and track bugs. You can work together, even do things like requesting 00:15:44.850 --> 00:15:49.120 feedback of your end users all through Visual Studio Online and that... 00:15:49.170 --> 00:15:54.300 and connect with whatever IDE or developer tool you want to use remotely. 00:15:55.040 --> 00:15:58.390 On top of that, we've done a lot of stuff to help take the hard 00:15:59.120 --> 00:16:03.360 infrastructure taxing type of things that are normally very expensive 00:16:03.410 --> 00:16:07.800 to build and use in house and put them in the cloud and leveraged 00:16:07.850 --> 00:16:12.900 our datacenters to make it really simple for you to deliver on stuff. 00:16:12.950 --> 00:16:16.400 Things like load testing. Well, we now have introduced a load 00:16:16.450 --> 00:16:19.760 testing service where you can submit load tests to us. 00:16:19.810 --> 00:16:22.510 We'll take care of the infrastructure. We'll provision it. 00:16:22.560 --> 00:16:25.650 We'll run the load test for you and give you the results back. 00:16:25.700 --> 00:16:29.450 It's really simple. It makes it easy to do and easy to do it 00:16:29.500 --> 00:16:33.330 on a regular basis. So you get good information about how your 00:16:33.380 --> 00:16:36.500 app is going to scale as you go forward. Things like continuous 00:16:36.550 --> 00:16:40.140 integration and build services, not just for .NET applications, 00:16:40.410 --> 00:16:43.710 but things like Java applications as well. Very powerful. 00:16:43.760 --> 00:16:47.570 And we've even gone so far as to make it easy to make smaller 00:16:47.620 --> 00:16:52.140 or medium-sized changes to web applications in the cloud by putting together... 00:16:52.190 --> 00:16:56.010 putting in a first class code editing experience through a browser, 00:16:56.370 --> 00:16:57.990 which is really powerful as well. 00:16:58.690 --> 00:17:02.360 So I'd actually like to switch over if I may, and kind of take 00:17:02.410 --> 00:17:06.160 you through some of the Visual Studio Online capabilities, take 00:17:06.210 --> 00:17:10.660 you through some of the capabilities, first of all, of just what 00:17:10.710 --> 00:17:15.710 we've introduced in the cloud and then we'll come back and take 00:17:15.760 --> 00:17:19.630 a look at some of the stuff that applies wholeheartedly to everybody. 00:17:19.680 --> 00:17:20.180 Is that okay? 00:17:20.230 --> 00:17:22.470 >> Yes. And before we do that, we did have a question on the chat 00:17:22.520 --> 00:17:25.510 which was actually a really good one. Going back to ALM Your 00:17:25.560 --> 00:17:29.540 Way, I love it, any examples of ALM using get? 00:17:30.640 --> 00:17:36.640 >> Absolutely. So I have customers today who are using get to 00:17:36.690 --> 00:17:40.530 manage their source code, but when they check in code, it's still 00:17:40.580 --> 00:17:43.500 telling them what changes are happening in the code and what 00:17:43.550 --> 00:17:44.780 bugs they're fixing. 00:17:45.360 --> 00:17:48.520 They're still feeding a build system and doing continuous integration 00:17:48.570 --> 00:17:50.900 the whole way that they've done it before. 00:17:52.010 --> 00:17:55.350 And as more and more organizations are starting to implement 00:17:55.400 --> 00:18:00.010 TFS 2013, even if they've had previous versions of TFS, they're 00:18:00.060 --> 00:18:03.800 looking at, hey, maybe I should use get for my distributed teams. 00:18:03.850 --> 00:18:06.840 We support both models in TFS. You pick the one you want to use 00:18:06.890 --> 00:18:09.820 and you don't have to pick one and ignore the other. You can 00:18:09.870 --> 00:18:11.590 mix and match. So... 00:18:11.640 --> 00:18:14.020 >> Nice. And actually what I love about it, when I was playing 00:18:14.070 --> 00:18:18.400 with it the other day, was that if you switch back and forth, 00:18:18.450 --> 00:18:23.460 TFS, get, whatever, doesn't matter, the ultimately the users 00:18:23.510 --> 00:18:26.980 who are using this are actually not seeing any difference, which 00:18:27.030 --> 00:18:30.070 is the part that I loved the most, right? It actually all happens 00:18:30.120 --> 00:18:30.780 in the background. 00:18:30.830 --> 00:18:31.580 >> Absolutely. 00:18:31.890 --> 00:18:35.380 >> So at the end of the day, the users, the ultimate end users 00:18:35.430 --> 00:18:38.550 aren't actually knowing whether they're going get or whether 00:18:38.600 --> 00:18:41.390 they're going TFS. It's all managed by TFS itself. 00:18:41.440 --> 00:18:45.160 >> That's correct, absolutely. And it's Visual Studio has the 00:18:45.210 --> 00:18:48.060 get client integration built in if you're using Visual Studio, 00:18:48.110 --> 00:18:49.670 which makes it really simple to use. 00:18:49.720 --> 00:18:53.560 >> Yeah. Yeah. Let's just say I tried using get command lines. 00:18:53.610 --> 00:18:57.550 Whoa, did I realize that I got spoiled by Visual Studio. Holy smokes. 00:18:57.600 --> 00:19:01.050 >> Visual Studio has a tendency to spoil you. 00:19:01.100 --> 00:19:04.900 >> I'm like, I'm standing there trying to figure out command? What? 00:19:05.540 --> 00:19:07.420 Right. And they are not, of course, all my Azure guys laugh at 00:19:07.470 --> 00:19:10.210 me because I'm probably one of the only Azure guys that doesn't 00:19:10.260 --> 00:19:12.190 do PowerShell. 00:19:12.240 --> 00:19:17.270 I love Visual Studio. I'm sorry. I do everything in Visual Studio. 00:19:17.320 --> 00:19:22.560 So here I am, I'm playing with get in Visual Studio and TFS and 00:19:22.610 --> 00:19:26.060 I'm like yes, if I can do this, clearly we've done a good job. 00:19:26.110 --> 00:19:28.510 >> Well, and you could take that one level further and whatever 00:19:28.560 --> 00:19:32.540 you're doing in Visual Studio with get and TFS, try using those 00:19:32.590 --> 00:19:35.100 Xamarin tools that we talked about at launch. 00:19:35.150 --> 00:19:36.010 >> That was a nice project. 00:19:36.060 --> 00:19:39.830 >> And take your C# application and build it out as a native app 00:19:39.880 --> 00:19:45.500 for Android and iOS, as well as Windows and Windows Phone. That's cool. 00:19:45.550 --> 00:19:49.990 Anyway, to Visual Studio Online here, I wanted to kind of highlight 00:19:50.040 --> 00:19:53.360 some of the stuff. Here I am at the visualstudio.com portal, 00:19:53.640 --> 00:19:56.850 and this is where I get to everything related to development. 00:19:56.900 --> 00:20:01.340 I can jump to MSDN. I look at my subscription. But I can also 00:20:01.390 --> 00:20:04.310 start off with Visual Studio Online, and I've already signed 00:20:04.360 --> 00:20:07.660 up so I'm going to go to my personal, this is where I manage 00:20:07.710 --> 00:20:12.110 my little projects, my closet projects, as it were. 00:20:12.160 --> 00:20:13.320 >> The closet developer. 00:20:13.370 --> 00:20:16.640 >> The closet developer has come out of the closet and I'm online 00:20:16.690 --> 00:20:21.430 now, and I'm going to actually go to my account. It's AdamGA.visualstudio.com, 00:20:22.580 --> 00:20:26.240 and here I can see all the projects I'm working on. I can look 00:20:26.290 --> 00:20:30.230 at different functionality that I might want to do. And if I 00:20:30.280 --> 00:20:34.340 want to add additional users to my account, maybe beyond the 00:20:34.390 --> 00:20:38.090 five free users that I get, I can actually purchase additional 00:20:38.140 --> 00:20:41.630 user rights right from the online service. And just like people 00:20:41.680 --> 00:20:45.530 might be familiar, you know, Office 365 has really taken off, 00:20:45.580 --> 00:20:48.400 and people are getting used to that subscription model for office. 00:20:48.450 --> 00:20:51.550 Well, guess what? There's also a subscription model now for Visual 00:20:51.600 --> 00:20:55.740 Studio where, you know, if I don't have Visual Studio as an IDE, 00:20:55.790 --> 00:20:59.250 but I want to start using it, I can pay as I go now with Visual 00:20:59.300 --> 00:21:02.750 Studio too. So it's really powerful stuff. But in here, I got 00:21:02.800 --> 00:21:06.520 a project that I'd like to maintain. It's called web chunks 00:21:06.570 --> 00:21:07.610 and other things. 00:21:08.140 --> 00:21:10.830 Don't ask me where the tame web chunks came up. 00:21:10.880 --> 00:21:12.620 >> Came up in the closet. 00:21:12.670 --> 00:21:15.200 >> It came up in the closet. It's pretty boring in the closet. 00:21:15.620 --> 00:21:19.330 But this is where I keep a lot of the little projects, demos 00:21:19.380 --> 00:21:22.720 and stuff that I work on on a regular basis. And so in here, 00:21:22.770 --> 00:21:26.470 I can actually look at that. I can access my source code. 00:21:26.520 --> 00:21:29.530 You can see I'm not a typical developer in that I'm a developer 00:21:29.580 --> 00:21:33.010 of one. So I have some planning tools. I can see a burn down 00:21:33.060 --> 00:21:36.320 where I still have a lot of remaining work to do. I'm not exactly 00:21:36.370 --> 00:21:38.410 on an ideal trend path for my development. 00:21:38.460 --> 00:21:39.250 >> Clearly not. 00:21:39.300 --> 00:21:42.800 >> But even there, I can actually go in and look at the source 00:21:42.850 --> 00:21:46.460 code and view the source code for my application. I can download 00:21:46.510 --> 00:21:49.600 the source code. I can prepare files, all of stuff that I've 00:21:49.650 --> 00:21:54.430 normally done and I can even... J.R., I might even want you to 00:21:54.480 --> 00:21:58.030 provide feedback on an application I'm building, which would 00:21:58.080 --> 00:22:01.320 be scary. Now, I'm not actually going to ask you to provide feedback, 00:22:01.370 --> 00:22:04.220 because that would mean you'd have to open yourself up and download 00:22:04.270 --> 00:22:05.780 my Windows Store application, 00:22:07.110 --> 00:22:10.080 but I can actually go in here and just request feedback of someone 00:22:10.130 --> 00:22:15.230 like, I don't know, I'll request feedback of myself, because, 00:22:15.280 --> 00:22:20.610 you know, that's normally a good way to get positive feedback. 00:22:20.660 --> 00:22:22.660 >> And usually, you are your own worst critic. 00:22:22.710 --> 00:22:23.350 >> Exactly. 00:22:23.400 --> 00:22:24.220 >> Because I know I am. 00:22:24.270 --> 00:22:27.710 >> And, you know, I'm going to ask the user to install my client 00:22:27.760 --> 00:22:33.020 application, install learner from the Windows Store. 00:22:35.950 --> 00:22:40.230 And, you know, focus on the UI. 00:22:41.270 --> 00:22:43.240 You know, is it pretty? 00:22:43.290 --> 00:22:45.010 >> There we go. It's looking for the positivity. 00:22:45.060 --> 00:22:46.830 >> Is it easy to use? 00:22:48.120 --> 00:22:51.030 And guess what? When I send this out, it's actually going to 00:22:51.080 --> 00:22:55.280 send me an email, and I actually haven't checked the name there. 00:22:55.940 --> 00:22:59.180 It's going to send me an email and request that... 00:22:59.710 --> 00:23:02.800 that's interesting. It didn't actually do that so I'm going to 00:23:02.850 --> 00:23:08.930 pick myself here, and now I'm going to send the email off, and 00:23:08.980 --> 00:23:11.780 that's actually the Visual Studio Online service is going to 00:23:11.830 --> 00:23:15.940 send me a request to run my... you know, install my app, review 00:23:15.990 --> 00:23:21.780 the app, and actually provide rich feedback back to my service. 00:23:21.830 --> 00:23:26.720 And I'll actually get feedback directly in my Visual Studio tool set. 00:23:26.770 --> 00:23:30.110 So in here, I've actually done that before. I can go and take 00:23:30.160 --> 00:23:34.120 a look at the feedback I've gotten about my application before, 00:23:34.410 --> 00:23:37.910 and you can see the feedback request that I sent out. But I 00:23:37.960 --> 00:23:42.700 can also go and look at any feedback at all. And so I've gotten 00:23:42.750 --> 00:23:45.740 some feedback responses from users before where they... 00:23:46.410 --> 00:23:50.490 they, for example, viewed a website that I've recently reviewed. 00:23:50.740 --> 00:23:54.360 And based on that feedback here on this website, they thought 00:23:54.410 --> 00:23:57.540 it was pretty good. I could actually go and say, you know what? 00:23:57.590 --> 00:24:02.670 I'm going to go make a new backlog item on my project to change 00:24:03.270 --> 00:24:05.190 all web properties 00:24:06.420 --> 00:24:09.150 to look like this one. 00:24:09.200 --> 00:24:10.420 >> To look like me. 00:24:10.470 --> 00:24:13.560 >> Yeah, and I'll submit that, and that actually becomes part 00:24:13.610 --> 00:24:17.380 of my project now. How good is that? I actually went out to my 00:24:17.430 --> 00:24:21.620 user, say what do you think about this, and they gave me some 00:24:21.670 --> 00:24:25.920 real feedback over email at their own pace that's really rich, includes... 00:24:25.970 --> 00:24:28.540 it even included some video, I think. Yeah, we actually have 00:24:28.590 --> 00:24:32.240 some screen recordings in there, and I was able to actually take 00:24:32.290 --> 00:24:35.040 that feedback and take action upon it. Really simple, right? 00:24:35.090 --> 00:24:38.280 >> No, the part that kills me is that all of this was done in 00:24:38.330 --> 00:24:38.990 your browser. 00:24:39.040 --> 00:24:41.400 >> Yeah, it's all done in the browser. And... 00:24:41.450 --> 00:24:42.920 >> But you could do it in Visual Studio. 00:24:42.970 --> 00:24:45.100 >> Oh, absolutely, you could do it in Visual Studio. As a matter 00:24:45.150 --> 00:24:47.140 of fact, I want to show you the other... 00:24:47.190 --> 00:24:50.460 >> Hold on a second, so now it's Visual Studio your way. Not just 00:24:50.510 --> 00:24:51.220 ALM Your Way. 00:24:51.270 --> 00:24:53.030 >> Yes. Yeah. 00:24:53.080 --> 00:24:53.780 >> I had to. 00:24:53.830 --> 00:24:54.580 >> Absolutely. 00:24:54.840 --> 00:24:57.520 >> Come on, hammer it home. It's all about me. 00:24:57.570 --> 00:25:00.500 >> You know what? I want to show you one more feature of Visual 00:25:00.550 --> 00:25:04.660 Studio that's really cool. So I'm going to actually switch to 00:25:04.710 --> 00:25:09.240 my Visual Studio IDE here, and I've got a couple of instances open. 00:25:09.290 --> 00:25:12.740 But the first thing I'm going to show you is the regular Visual 00:25:12.790 --> 00:25:16.310 Studio 2013 IDE. But notice up in the right-hand corner, it's 00:25:16.360 --> 00:25:18.790 a little hard to see. I don't know if I have Zoom It installed. 00:25:20.560 --> 00:25:24.200 You can see it says Adam Gallant, and I'm signed in. What did 00:25:24.250 --> 00:25:27.230 you mean signed in? Yeah, I'm signed into Visual Studio. 00:25:27.280 --> 00:25:31.300 This means a couple things. First, it hooks me up to my Visual 00:25:31.350 --> 00:25:35.370 Studio Online so it knows where my server is. It also is going 00:25:35.420 --> 00:25:39.180 to know what my settings are in Visual Studio. And I can move 00:25:39.230 --> 00:25:42.480 between machines and Visual Studio will remember your settings. 00:25:42.530 --> 00:25:46.330 So if I go over to your machine, it's going to change the Visual 00:25:46.380 --> 00:25:50.940 Studio background, the layout of the Windows and everything from 00:25:50.990 --> 00:25:54.880 pink, for example, like you like to have yours, back to blue. 00:25:54.930 --> 00:25:56.720 >> I knew you were going to go there. 00:25:56.770 --> 00:25:57.620 >> So that's pretty cool. 00:25:57.670 --> 00:25:58.640 >> I knew you were going to go there. 00:25:58.690 --> 00:25:59.460 >> That's awesome. 00:25:59.510 --> 00:26:02.100 >> Now hold on a second, though. I notice so you're making fun 00:26:02.150 --> 00:26:03.400 of me, which is fine. 00:26:03.450 --> 00:26:03.520 >> Yes. 00:26:03.570 --> 00:26:06.340 >> But now I've noticed that you've also gone ahead and changed 00:26:06.390 --> 00:26:09.900 your Visual Studio interface to look like the old one. 00:26:09.950 --> 00:26:10.420 >> Ah, yes. 00:26:10.470 --> 00:26:12.360 >> Where I happen to like the new one. 00:26:13.410 --> 00:26:14.110 Just sayin'. 00:26:14.160 --> 00:26:16.340 >> You like the dark? I like the blue. 00:26:17.430 --> 00:26:21.630 You know, but I'm a lot older than you. So, you know, sometimes... 00:26:21.900 --> 00:26:22.380 >> Couldn't tell. 00:26:22.430 --> 00:26:26.160 >> Sometimes things have a habit of coming along. 00:26:27.530 --> 00:26:30.130 Jonathan, I've got a load test right here. Let's get back to 00:26:30.180 --> 00:26:31.310 what people are actually here for. 00:26:31.360 --> 00:26:32.250 >> Fair enough. 00:26:32.300 --> 00:26:36.030 >> I've got a load test here that actually runs against a website 00:26:36.080 --> 00:26:40.090 that I've built. Now, it's not a real fancy website. It's actually 00:26:40.140 --> 00:26:41.590 just the ASP.NET... 00:26:42.780 --> 00:26:47.440 it's just a standard ASP.NET MVC website. I happen to be hosting 00:26:47.490 --> 00:26:51.250 it up in the cloud, and I want to actually test this out. 00:26:51.300 --> 00:26:55.540 Now, this could be any website I want. It could be an ASP.NET. 00:26:55.590 --> 00:26:58.000 It could be PHP-based. Doesn't really matter. 00:26:58.620 --> 00:27:03.200 But as I want to measure this scaleability of that site, if I'm 00:27:03.250 --> 00:27:06.760 going to put it live, I probably want to see how it's going to 00:27:06.810 --> 00:27:11.200 respond and react when I run tens or hundreds or thousands of 00:27:11.250 --> 00:27:14.700 concurrent users against it. That's what Visual Studio load testing is. 00:27:14.750 --> 00:27:18.430 And ideally, I'd want to run this on a fairly regular basis as 00:27:18.480 --> 00:27:22.040 I'm doing development to see how I'm progressing towards those goals. 00:27:22.090 --> 00:27:23.440 >> And ideally not on your machine. 00:27:23.490 --> 00:27:27.050 >> Well, ideally not on my machine and not on my business network 00:27:27.100 --> 00:27:29.870 where other people are trying to access email and save documents. 00:27:30.210 --> 00:27:34.010 So that really restricts when I can run this. And even with 00:27:34.060 --> 00:27:37.780 virtualization on-premise, I still need a lot of hardware and 00:27:37.830 --> 00:27:42.780 a lot of time to set this up to run that scaleability. So with 00:27:42.830 --> 00:27:47.410 this load test scenario here, I've got a mix of activities on 00:27:47.460 --> 00:27:51.380 my website. I'm going to mix up a bunch of browsers, run it against 00:27:51.430 --> 00:27:54.490 that so we're going to see how it works with Chrome and Firefox, 00:27:55.140 --> 00:27:57.800 and I'm going to actually check to see how it works with a thousand 00:27:57.850 --> 00:28:00.990 concurrent users running against my website. Now, that would 00:28:01.040 --> 00:28:04.090 involve a lot of network bandwidth and infrastructure. 00:28:04.660 --> 00:28:07.550 But instead of running that locally, I'm going to take advantage 00:28:07.990 --> 00:28:10.510 of Visual Studio Online in our ALM tools. 00:28:10.560 --> 00:28:12.330 >> Here we go. We're going into the cloud. 00:28:12.380 --> 00:28:16.200 >> Simply going into my test settings on how I want to run it, 00:28:16.250 --> 00:28:20.660 and I'm saying run the test in my Team Foundation Service, AKA 00:28:20.710 --> 00:28:21.870 Visual Studio Online. 00:28:21.920 --> 00:28:22.450 >> Love it. 00:28:22.500 --> 00:28:23.300 >> So you ready? 00:28:23.820 --> 00:28:24.790 >> Here we go. 00:28:24.840 --> 00:28:27.830 >> So this should completely wipe out our network, right? 00:28:28.850 --> 00:28:29.910 Oh, no, it's not. 00:28:30.590 --> 00:28:31.310 Oh, no, it's not. 00:28:31.360 --> 00:28:32.110 >> Da-da-da. 00:28:32.410 --> 00:28:35.500 >> It's actually submitting this slide. Now, I'm flying a little 00:28:35.550 --> 00:28:38.960 bit without a net here, because I have no idea. This is a brand 00:28:39.010 --> 00:28:39.890 new service. 00:28:40.560 --> 00:28:44.070 But it looks like we're actually submitting the load test live 00:28:44.120 --> 00:28:49.200 into the cloud and it's sitting in a Microsoft datacenter and 00:28:49.250 --> 00:28:52.020 it's being queued up for execution right now. 00:28:52.750 --> 00:28:56.620 And it might take a couple of seconds to get everything set up. 00:28:56.670 --> 00:28:59.480 I don't know how many people are submitting load tests right now. 00:28:59.530 --> 00:29:02.330 >> I think just for fun, for the next half hour, we should stare 00:29:02.380 --> 00:29:02.730 at it. 00:29:02.780 --> 00:29:04.990 >> Well, it's only going to run for a minute. 00:29:05.350 --> 00:29:07.360 >> We could still stare at the results then. 00:29:07.410 --> 00:29:10.450 >> We can stare at the results and you can continue to 00:29:11.870 --> 00:29:13.730 keep us interested. How's that? 00:29:13.780 --> 00:29:14.540 >> You know what... 00:29:14.590 --> 00:29:18.170 >> But you notice here, it's acquiring resources right here, J.R. 00:29:18.220 --> 00:29:19.000 Isn't that amazing? 00:29:19.050 --> 00:29:19.640 >> Let's take a look. 00:29:19.690 --> 00:29:22.660 >> So it's actually starting up. It's acquiring the resources 00:29:22.710 --> 00:29:24.460 from the datacenter dynamically. 00:29:25.130 --> 00:29:27.840 It's going to configure the agents to run in a couple of second, 00:29:27.890 --> 00:29:32.250 hopefully, because it's always fun to make people wait on a webcast 00:29:32.300 --> 00:29:33.780 while something happens. 00:29:33.830 --> 00:29:36.790 >> Well, but at least this way you're waiting for second as opposed 00:29:36.840 --> 00:29:38.730 to minutes or hours. 00:29:38.780 --> 00:29:42.230 >> But interestingly enough, I don't have to wait. I can just 00:29:42.280 --> 00:29:44.640 let this run, right? I can go off and do something else. I can 00:29:44.690 --> 00:29:48.070 go to another instance of Visual Studio here, for example, and 00:29:48.120 --> 00:29:51.870 look at, you know, I've got this Windows Store application. 00:29:52.320 --> 00:29:55.890 I might actually want to examine it for energy consumption so 00:29:55.940 --> 00:29:59.630 I can see how my application performs on different types of devices. 00:29:59.680 --> 00:30:03.030 So while that's running, I'm actually going to launch a brand 00:30:03.080 --> 00:30:07.960 new feature in Visual Studio where I bring up my personal application. 00:30:08.860 --> 00:30:13.730 This is a Windows Store application making use of Azure Mobile Services. 00:30:13.780 --> 00:30:15.720 >> Which are near and dear to my heart. 00:30:15.770 --> 00:30:19.000 >> They're wonderful. So this application signs me in using my 00:30:19.050 --> 00:30:22.330 Microsoft ID, but it could have been my Facebook ID. And with 00:30:22.380 --> 00:30:26.360 that, I can go through my application, look at particular lesson 00:30:26.410 --> 00:30:28.880 plans that I've done, and it's going to remember, for example, 00:30:28.930 --> 00:30:32.340 that I'm watching this lesson, and it going to keep track of 00:30:32.390 --> 00:30:35.390 my progress for the application. So pretty cool stuff. So I 00:30:35.440 --> 00:30:39.790 can actually go through and try different content in there. 00:30:39.840 --> 00:30:42.460 And when I'm done, I'm just going to close the app and go back 00:30:42.510 --> 00:30:46.740 to my desktop, and I'll stop collecting data. Now Visual Studio, 00:30:46.790 --> 00:30:50.170 while my load test is running in the cloud there, by the way, 00:30:50.220 --> 00:30:52.470 has told me how this application is going to work. 00:30:52.520 --> 00:30:53.020 >> Love it. 00:30:53.070 --> 00:30:57.630 >> And check this out. It's going to tell me... I'm going to ignore... 00:30:58.250 --> 00:31:00.410 you know, it's also really good... 00:31:01.330 --> 00:31:03.780 >> He's also in the cloud. 00:31:03.830 --> 00:31:08.390 >> Yeah, Marco is in the cloud. I'm going to exit link so that 00:31:08.440 --> 00:31:12.850 my sales guy, who is actually with a customer right now, he will 00:31:12.900 --> 00:31:15.920 come back and watch this, by the way and understand why I couldn't 00:31:15.970 --> 00:31:18.190 answer his sales question. 00:31:18.930 --> 00:31:20.170 >> Because we were running a load test. 00:31:20.220 --> 00:31:21.830 >> We are running a load test. 00:31:21.880 --> 00:31:23.130 >> And an energy consumption test. 00:31:23.180 --> 00:31:25.270 >> Well, you know, that's pretty powerful stuff. Leveraging the 00:31:25.320 --> 00:31:30.650 cloud, we were able to do a load test, measure the energy consumption 00:31:30.700 --> 00:31:36.540 of my application, and receive a request from my sales guy using 00:31:36.590 --> 00:31:39.990 Office 365. That's pretty powerful stuff. Let's go back to the 00:31:40.040 --> 00:31:41.700 load test and see what we got. 00:31:41.750 --> 00:31:43.950 >> So I'm going to pause you for a split second here. 00:31:44.000 --> 00:31:44.890 >> Yeah. 00:31:44.940 --> 00:31:47.730 >> So I think one of the key things that even though obviously 00:31:47.780 --> 00:31:51.350 the load test itself, which is awesome to actually do not on 00:31:51.400 --> 00:31:55.810 your machine, one of the big things at least for me when I'm 00:31:55.860 --> 00:31:58.250 talking to developers is they're like, well, whoa, wait a second. 00:31:58.300 --> 00:32:04.880 So now we can actually provision and do load tests without having 00:32:04.930 --> 00:32:07.030 anybody from IT involved? 00:32:07.080 --> 00:32:07.770 >> Absolutely. 00:32:07.820 --> 00:32:08.340 >> So now... 00:32:08.390 --> 00:32:09.260 >> How good is that? 00:32:09.830 --> 00:32:12.540 Not that I dislike that... 00:32:12.590 --> 00:32:13.550 >> So here we are... 00:32:13.600 --> 00:32:16.220 >> Look, the results are coming back. You should put that on 00:32:16.270 --> 00:32:17.150 the screen while we talk. 00:32:17.200 --> 00:32:19.670 >> Let's look at it. Here are the results. 00:32:19.720 --> 00:32:20.280 >> Oh, wow. 00:32:20.330 --> 00:32:23.220 >> I still want to ask my question, though. Let's stare at the results. 00:32:23.270 --> 00:32:26.060 >> Let's stare at the results for a second, because this is actually 00:32:26.110 --> 00:32:29.900 live testing a website using a thousand virtual users. 00:32:30.780 --> 00:32:33.460 And we're actually seeing, we're 30 seconds into the one-minute 00:32:33.510 --> 00:32:36.560 test, J.R., and we can actually start to see some performance 00:32:36.610 --> 00:32:40.180 statistics coming back, like my average response time for my 00:32:40.230 --> 00:32:45.070 pages is actually pretty poor. But it is coming down now that 00:32:45.120 --> 00:32:46.980 the application has reached steady state. 00:32:47.030 --> 00:32:47.860 >> Of course. 00:32:48.270 --> 00:32:52.010 >> And so that means I might want to go and avail myself of Azure's 00:32:52.060 --> 00:32:55.610 instant elastic scale capability and start adding more scale 00:32:55.660 --> 00:32:59.310 to my app because I need it. But as it turns out, either my app 00:32:59.360 --> 00:33:03.630 has crashed or it has reached steady state, so chances are it 00:33:03.680 --> 00:33:07.470 didn't crash and we've actually gotten to a steady state of execution 00:33:07.520 --> 00:33:10.490 in our app, which is kind of cool. And my load test is telling 00:33:10.540 --> 00:33:13.550 me that. And, oh by the way, it's collecting the results from 00:33:13.600 --> 00:33:18.010 the test now and, you know, we can switch back, but... and talk, 00:33:18.060 --> 00:33:22.050 we don't have to watch this anymore. We'll get all the detailed 00:33:22.100 --> 00:33:26.210 test results just like we would have before if we ran it locally, 00:33:26.260 --> 00:33:28.630 and we'll just download those and we can analyze that at our 00:33:28.680 --> 00:33:28.830 own pace. 00:33:28.880 --> 00:33:30.930 >> I was actually getting kind of excited about watching all the 00:33:30.980 --> 00:33:33.860 squiggly lines, but as I'm watching this and you're talking about 00:33:33.910 --> 00:33:37.100 thousands of users and stuff like that, it occurred to me that 00:33:37.150 --> 00:33:39.690 if you think back in the day, right, so... 00:33:39.740 --> 00:33:41.650 >> There's a lot in the back of days. 00:33:41.700 --> 00:33:45.060 >> Fair enough. Let's go back just a few days before all this 00:33:45.110 --> 00:33:48.050 stuff came out. Right, here we are as developers, we're ready 00:33:48.100 --> 00:33:51.380 to go into testing. We need to test the stuff out. We go, we 00:33:51.430 --> 00:33:54.440 make the test out to IT, and we basically sit there and hold 00:33:54.490 --> 00:33:56.660 for three weeks, four weeks, until... 00:33:56.710 --> 00:34:01.790 >> Absolutely. You know, the cloud really changes your ability 00:34:01.840 --> 00:34:07.350 to be agile in delivering software. Those delays that you experience 00:34:08.010 --> 00:34:11.470 really fly in the face of what you're trying accomplish by being agile. 00:34:11.520 --> 00:34:16.770 Quick cycle times, quick ability to rapidly take feedback from 00:34:16.820 --> 00:34:21.080 your stakeholders, whether they be internal or external and implement them. 00:34:21.130 --> 00:34:24.140 If you've got to wait, you know, I've talked to customers recently 00:34:24.190 --> 00:34:26.110 where to get a new server is three months. 00:34:26.160 --> 00:34:26.980 >> Of course. 00:34:27.030 --> 00:34:30.420 >> I mean, nowadays, three months is about how long it takes to 00:34:30.470 --> 00:34:32.090 build most of the applications. 00:34:32.140 --> 00:34:32.690 >> Of course. 00:34:32.740 --> 00:34:35.180 >> The cloud really changes that. 00:34:35.230 --> 00:34:37.790 >> So then if you think about it, you're going to go now... 00:34:37.840 --> 00:34:41.160 so now here's me coming up to my boss again saying oh, we need 00:34:41.210 --> 00:34:44.160 this, right. Boss is going to be like whoa, whoa, whoa. 00:34:45.080 --> 00:34:47.760 Now there's something new that we have to pay. And then you're 00:34:47.810 --> 00:34:49.560 like uh-uh, MSDN. 00:34:49.610 --> 00:34:55.020 >> Absolutely. So here's the coolest thing I ever saw, and I didn't 00:34:55.070 --> 00:34:58.980 really prepare you for this, Jonathan. I didn't. I'm going 00:34:59.030 --> 00:35:01.840 to do something that really is going to upset Jonathan. I'm going 00:35:01.890 --> 00:35:05.070 to bring up another slide to kind of show you something that 00:35:05.120 --> 00:35:10.160 I think is super cool, and it answers your question. So bear 00:35:10.210 --> 00:35:11.740 with me just a second. 00:35:11.790 --> 00:35:15.150 >> I'm waiting. I'm waiting anxiously. I'm staring at your screen. 00:35:15.200 --> 00:35:17.470 >> Well, and do you know what? The other thing that you could 00:35:17.520 --> 00:35:23.130 do is you could watch a Channel 9 video that we've done on the 00:35:23.180 --> 00:35:24.540 Canadian developer connection. 00:35:24.590 --> 00:35:25.180 >> Yes, indeed. 00:35:25.230 --> 00:35:29.650 >> On this whole thing about using our cloud for dev and tasks. 00:35:29.700 --> 00:35:33.950 Now, this is a really busy slide, but you can see that if you 00:35:34.000 --> 00:35:38.330 have MSDN subscriptions with your Visual Studio, you get credits 00:35:38.380 --> 00:35:42.820 to use the cloud for any dev test purpose you want. So think 00:35:42.870 --> 00:35:46.770 if I have Visual Studio Pro with MSDN, I get 50 bucks a month, 00:35:46.820 --> 00:35:51.340 Canadian or U.S., sorry, to actually do whatever I want or a 00:35:51.390 --> 00:35:55.670 hundred bucks if it's Visual Studio Premium or 150 if that's Ultimate. 00:35:55.720 --> 00:35:59.110 And if you really think about that, do you know what that means? 00:35:59.160 --> 00:36:02.580 Well, let's look at premium for a second. With the benefits 00:36:02.630 --> 00:36:05.960 you get in premium, you can run three whole virtual machines 00:36:06.010 --> 00:36:09.500 for 16 hours a day with your benefits for the month. 00:36:09.550 --> 00:36:10.350 >> ALM Your Way, man. 00:36:10.400 --> 00:36:15.340 >> ALM Your Way. You can run 80 virtual... 80... machines for 00:36:15.390 --> 00:36:18.110 a 20-hour load test using your benefits for the month. 00:36:18.160 --> 00:36:18.700 >> Crazy. 00:36:18.750 --> 00:36:23.260 >> These are not insignificant. So definitely take a look at your 00:36:23.310 --> 00:36:29.190 benefits and what you have available to you as part of your MSDN subscriptions. 00:36:30.980 --> 00:36:31.500 Cool, hey? 00:36:31.550 --> 00:36:35.500 >> Yeah. I'm still trying to... I'm still stuck at the fact that 00:36:35.550 --> 00:36:38.000 there isn't that wait time anymore. So ultimately, what we're 00:36:38.050 --> 00:36:41.470 saying here is we're going to go to this model, and here I am 00:36:41.520 --> 00:36:45.170 developer, I've finished my stuff quickly because I am now agile 00:36:45.220 --> 00:36:48.750 and now on top of that, so I've optimized what I'm doing from 00:36:48.800 --> 00:36:51.660 a development perspective, but now I can optimize my load testing 00:36:51.710 --> 00:36:55.080 and all of my... I shouldn't even say load testing, all of my 00:36:55.130 --> 00:36:59.810 testing simply by adding in the fact that now my entire world 00:36:59.860 --> 00:37:02.110 connects into the cloud giving this stuff back and now we can 00:37:02.160 --> 00:37:02.900 move things quickly. 00:37:02.950 --> 00:37:05.350 >> It's so awesome to have a datacenter in your pocket. 00:37:05.400 --> 00:37:08.570 That's the way I look at it. I have my own datacenter that goes 00:37:08.620 --> 00:37:11.300 with me everywhere with an unlimited scale. 00:37:11.350 --> 00:37:13.740 >> So that, of course, that's awesome for me as a developer. 00:37:13.790 --> 00:37:16.880 But now I'm thinking okay, so now how do I pitch this to my boss, 00:37:16.930 --> 00:37:19.550 because let's be honest, I don't buy this stuff. He does. 00:37:19.600 --> 00:37:24.490 I can be like, well, listen, we could do all this stuff and get 00:37:24.540 --> 00:37:27.240 products into market that much quicker. 00:37:27.290 --> 00:37:27.540 >> Absolutely. 00:37:27.590 --> 00:37:28.900 >> Which ultimately is what they want to hear. 00:37:28.950 --> 00:37:32.170 >> And guess what. The benefits you've already paid for, sir, 00:37:32.220 --> 00:37:37.800 will allow me to do that for... largely for free for my dev and test. 00:37:37.850 --> 00:37:40.240 >> If I called my boss sir, I think he'd laugh at me. 00:37:40.290 --> 00:37:42.600 >> I know your boss. He would. 00:37:42.650 --> 00:37:45.390 >> Anyway, back to new capabilities of ALM. 00:37:45.440 --> 00:37:47.950 >> You know, it's funny. I introduced stuff that I think are really 00:37:48.000 --> 00:37:52.050 impactful, but there's tons of new things that you can do in 00:37:52.100 --> 00:37:54.680 Visual Studio ALM that we've introduced in this release. 00:37:54.730 --> 00:37:55.890 >> Right. Let's do it. 00:37:55.940 --> 00:38:00.440 >> Whether it's on your local machine or in the cloud ALM, we've 00:38:00.490 --> 00:38:03.230 done a lot of things. And we kind of group them into a few core 00:38:03.280 --> 00:38:06.890 categories from planning, right, it's kind of good to understand 00:38:06.940 --> 00:38:07.860 what you're going to build. 00:38:08.550 --> 00:38:12.250 To developing, to releasing and operating. 00:38:12.840 --> 00:38:16.450 We've done a lot. So whether that's working with things like 00:38:16.500 --> 00:38:20.730 Kanban and Scrum and taking the Scrum tools or the tools that 00:38:20.780 --> 00:38:25.110 apply to Agile development, allowing you to work with any process 00:38:25.160 --> 00:38:29.220 you want, but still using those tools, we've really extended 00:38:29.270 --> 00:38:32.830 it out. So you can... you know, if you're managing a whole bunch 00:38:32.880 --> 00:38:36.770 of smaller delivery teams, you can aggregate up and use the Agile 00:38:36.820 --> 00:38:40.050 tools for that. When you get into development, I talked a little 00:38:40.100 --> 00:38:44.230 bit before about the Team Room as kind of being a place, a persistent 00:38:44.280 --> 00:38:47.680 place where you can do chats, you can comment on source code 00:38:47.730 --> 00:38:51.140 and inspect what's going on. But we've actually done other stuff 00:38:51.190 --> 00:38:54.610 like load testing as a service. We've got a little, nice little 00:38:54.660 --> 00:38:59.330 heads-up display or dashboard inside the IDE to help you understand 00:38:59.380 --> 00:39:01.770 what's happening with the source code, who's got it checked out, 00:39:01.820 --> 00:39:04.520 who was the last person to edit it. And it just kind of sits 00:39:04.570 --> 00:39:07.660 there to help you see what's going on without getting in your way. 00:39:08.360 --> 00:39:12.250 A really exciting capability that we added in this release is 00:39:12.300 --> 00:39:15.490 something called Visual Studio Release Management, and I'll show 00:39:15.540 --> 00:39:18.760 you that in a couple minutes, where we can actually have a fully 00:39:19.380 --> 00:39:24.280 functional, multi-environment release path defined. We can deploy 00:39:24.330 --> 00:39:27.960 our applications through that with full approval work flows all 00:39:28.010 --> 00:39:31.400 included, and that's actually part of Team Foundation Server. 00:39:31.450 --> 00:39:35.070 I'm going to show you that tool in a little bit. And last but 00:39:35.120 --> 00:39:38.810 not least, as our system gets into production, we want to be 00:39:38.860 --> 00:39:42.810 able to understand how our users are working with the application 00:39:42.860 --> 00:39:45.540 so that we can improve how we do our work. 00:39:46.090 --> 00:39:49.380 I can't show you that today, because that's brand new. It's called 00:39:49.430 --> 00:39:52.160 application insights. It's something that's in preview, and you 00:39:52.210 --> 00:39:56.120 can actually go and attempt to use it. Application insights 00:39:56.170 --> 00:39:58.950 gives you things like health dashboards, about how your app is 00:39:59.000 --> 00:40:04.370 working, gives you notifications and debug information constantly 00:40:04.420 --> 00:40:08.180 about how the application is functioning if you're getting errors, 00:40:08.230 --> 00:40:11.070 and gives you trending and information about how to improve your 00:40:11.120 --> 00:40:14.730 application, whether your app is on premises or it's running 00:40:14.780 --> 00:40:15.470 in the cloud. 00:40:15.520 --> 00:40:18.540 >> So before we go back to the awesomeness of that, actually, 00:40:18.590 --> 00:40:21.120 for those of you guys that are watching from the west coast, 00:40:21.170 --> 00:40:26.450 so this is a small little plug for dev teach, but on dev teach, 00:40:26.500 --> 00:40:29.350 which is actually happening in about two weeks or so, they're 00:40:29.400 --> 00:40:32.110 actually going to go for the first time in public, if you will, 00:40:32.160 --> 00:40:34.510 they're actually going to go through all of the application insights 00:40:34.560 --> 00:40:37.590 and actually drill deep into all the functionality. 00:40:37.640 --> 00:40:41.810 >> It's an incredible new piece of functionality that really is 00:40:41.860 --> 00:40:45.800 jaw-dropping in terms of how easy it will be to use and the types 00:40:45.850 --> 00:40:48.220 of information that you're going to get about your app. So you're 00:40:48.270 --> 00:40:51.140 going to be... the idea is you'll know before your users what's 00:40:51.190 --> 00:40:52.110 happening with your app. 00:40:52.160 --> 00:40:54.410 >> Which ultimately what is you want to do anyway, okay, because 00:40:54.460 --> 00:40:57.390 the last thing you want to do is get anything out to the users. 00:40:57.440 --> 00:41:01.620 If the users have to tell you that there's a problem, there's only... 00:41:01.670 --> 00:41:03.190 you can only do first impressions once. 00:41:03.240 --> 00:41:03.670 >> Absolutely. 00:41:03.720 --> 00:41:04.500 >> And then it's done. 00:41:04.550 --> 00:41:07.480 >> It's absolutely done. What do you do on your phone today if 00:41:07.530 --> 00:41:10.320 you install an app and it doesn't work the way you think it works 00:41:10.370 --> 00:41:11.510 within a minute, what do you do? 00:41:11.560 --> 00:41:13.870 >> You rate it and you uninstall it. 00:41:13.920 --> 00:41:15.350 >> And most people won't even rate it. 00:41:15.400 --> 00:41:18.310 >> Fair enough. I do like to provide feedback. 00:41:18.360 --> 00:41:21.070 >> Yes, I know very well that you like to provide feedback. 00:41:21.120 --> 00:41:21.660 Thank you very much. 00:41:21.710 --> 00:41:23.490 >> I don't know what he's referring to. 00:41:23.540 --> 00:41:26.080 >> The other thing that's really exciting now, not everybody has 00:41:26.130 --> 00:41:27.710 applications that face the public. 00:41:27.760 --> 00:41:28.160 >> Right. 00:41:28.210 --> 00:41:31.200 >> And while app insights might work for them, they might already 00:41:31.250 --> 00:41:35.150 have an infrastructure to manage their systems operationally. 00:41:35.710 --> 00:41:39.420 In the Microsoft world, that's System Center. And System Center 00:41:39.470 --> 00:41:43.810 Operations Manager includes now a connector that can actually 00:41:43.860 --> 00:41:47.450 connect the Team Foundation Server and provide deep diagnostic 00:41:47.500 --> 00:41:51.580 details and incident management. So if I'm an IT operator and 00:41:51.630 --> 00:41:56.660 I don't understand the code base, that's not my job, but an incident 00:41:56.710 --> 00:41:59.900 comes up like an exception or the website's not performing well, 00:41:59.950 --> 00:42:03.340 I can actually route that alert to the developers who are in 00:42:03.390 --> 00:42:06.800 charge of it. They can see all the detail they need, and the 00:42:06.850 --> 00:42:08.360 root cause and fix it right away. 00:42:08.410 --> 00:42:11.340 >> So now built into ALM my way, we now all of a sudden have dev 00:42:11.390 --> 00:42:12.210 ops in there as well? 00:42:12.260 --> 00:42:15.920 >> We have not just dev ops, but I would call it ops my way. 00:42:15.970 --> 00:42:18.300 >> Ooh. Or operations as a service. 00:42:18.350 --> 00:42:21.050 >> Operations as a service, yes, sure. Absolutely. 00:42:21.430 --> 00:42:22.600 >> Come on, I had to. 00:42:22.650 --> 00:42:26.390 >> So not only application insights, but operations as well. 00:42:26.440 --> 00:42:26.810 >> Cool. 00:42:26.860 --> 00:42:29.500 >> So do you know what I thought I'd do is we could switch over 00:42:29.550 --> 00:42:30.560 and I could show you some of this stuff. 00:42:30.610 --> 00:42:32.550 >> Let's do it. 00:42:32.600 --> 00:42:35.630 >> All right. So I'm going to switch over to a virtual machine. 00:42:35.680 --> 00:42:39.100 Funny enough, the virtual machine I'm going to run, and I'm really 00:42:39.150 --> 00:42:43.210 mucking with Jonathan right now, because I'm switching between things. 00:42:43.260 --> 00:42:44.930 >> And he's doing it on purpose too. 00:42:44.980 --> 00:42:48.230 >> I do. I like to do that on purpose. I'm actually going to 00:42:48.280 --> 00:42:53.830 a virtual machine image. This virtual machine image is actually downloadable. 00:42:54.330 --> 00:42:55.140 >> Nice. 00:42:55.190 --> 00:43:01.930 >> This 2013 release image will be available shortly off the web. 00:43:01.980 --> 00:43:05.160 If you go to Brian Keller's website or if you just want a short 00:43:05.210 --> 00:43:08.340 cut, you can go to aka.ms/almvm. 00:43:11.400 --> 00:43:17.480 You can download fully configured Visual Studio virtual machines 00:43:17.530 --> 00:43:22.700 with sample data, with Visual Studio hands-on labs to help you 00:43:22.750 --> 00:43:25.840 learn how to use all these tools. And I'm looking at one right here. 00:43:25.890 --> 00:43:27.620 >> And, of course, we'll have the link for them in the comments 00:43:27.670 --> 00:43:28.590 to the video anyway. 00:43:28.640 --> 00:43:29.860 >> Absolutely we will. 00:43:30.600 --> 00:43:31.910 You get on that right away. 00:43:31.960 --> 00:43:32.710 >> Absolutely. 00:43:33.460 --> 00:43:37.590 >> But here's the web access for Team Foundation Server, and we've 00:43:37.640 --> 00:43:39.400 actually gone back in time. 00:43:40.700 --> 00:43:44.770 We're actually traveling back in time to a time between July 00:43:44.820 --> 00:43:46.100 1 and July 12. 00:43:46.990 --> 00:43:49.960 We've done that in the VM so that you have some sample data to 00:43:50.010 --> 00:43:51.400 work with that's meaningful. 00:43:52.230 --> 00:43:56.360 And I also like doing that in my demos because anything that's 00:43:56.410 --> 00:43:59.920 goes wrong with my demos, I can blame on temporal effects. 00:43:59.970 --> 00:44:00.490 >> Of course. 00:44:00.540 --> 00:44:02.740 >> And that's really important to have a scapegoat. 00:44:03.530 --> 00:44:06.960 But right from this home page, I can actually look at things 00:44:07.010 --> 00:44:12.800 like my backlog view and in my backlog view, I can see all the 00:44:12.850 --> 00:44:18.600 teams that I'm working with. I can manage things like features 00:44:19.060 --> 00:44:22.980 that aggregate up my backlog items. Oh, yeah, and by the way, 00:44:23.030 --> 00:44:27.010 if I was not using Agile or Scrum, this is going to show up for 00:44:27.060 --> 00:44:32.590 me as requirements and whatever other aggregation I want. 00:44:32.640 --> 00:44:37.420 So I can use this to manage my teams, assign things to team members, 00:44:37.470 --> 00:44:42.210 break down my features into requirements and tasks, drag and 00:44:42.260 --> 00:44:46.060 drop them to schedule them to particular iterations or sprints 00:44:46.110 --> 00:44:49.830 or cycles or whatever I call them, and even manage all of that 00:44:49.880 --> 00:44:53.860 through a Kanban board that's customizable. That's pretty powerful stuff. 00:44:54.630 --> 00:44:57.930 If you're today... or if you've seen people do it or if you've 00:44:57.980 --> 00:45:00.790 got a room where you've got sticky notes on the wall and you're 00:45:00.840 --> 00:45:03.750 moving them between columns to manage your development process, 00:45:04.210 --> 00:45:06.570 this is the same type of capability. 00:45:07.080 --> 00:45:12.220 I simply drag and drop and use the tools to work my way. We even 00:45:12.270 --> 00:45:14.750 have added the ability to execute... 00:45:15.330 --> 00:45:20.330 to author test plans and to execute functional tests right from 00:45:20.380 --> 00:45:23.620 the web browser. So you could test anywhere you want as well. 00:45:23.670 --> 00:45:25.420 I think that's pretty cool stuff, J.R. 00:45:25.470 --> 00:45:29.200 >> Absolutely. It still goes back to the fact that you can have... 00:45:29.950 --> 00:45:32.750 you can do the work you want to do when you want to do it how 00:45:32.800 --> 00:45:35.410 you want to do it and then good things just happen from there 00:45:35.460 --> 00:45:38.140 simply by just having everything all together, number one. 00:45:38.190 --> 00:45:39.080 >> Absolutely. 00:45:39.130 --> 00:45:40.800 >> Accessible from anywhere, number two. 00:45:41.490 --> 00:45:45.370 And... okay, I'm going to say it again, done your way. But what 00:45:45.420 --> 00:45:47.680 struck me as actually kind of really cool is how you mentioned 00:45:47.730 --> 00:45:51.400 that even the wording changes based on the type of process that 00:45:51.450 --> 00:45:52.300 you selected. 00:45:52.350 --> 00:45:55.660 >> Yeah, TFS doesn't say you have to use any one process or another. 00:45:55.710 --> 00:45:56.700 Use whatever you want. 00:45:56.750 --> 00:45:58.940 >> And to me, I find that fascinating, especially if I'm in a 00:45:58.990 --> 00:46:01.730 large organization and here I am trying to manage, you know, 00:46:01.780 --> 00:46:05.270 change management and, okay, we're moving to this new platform. 00:46:05.320 --> 00:46:07.980 We're kind of spicing things up a little. We're getting a little 00:46:08.030 --> 00:46:10.960 bit more organized. The last thing I want to do is throw new 00:46:11.010 --> 00:46:11.960 terminology in there and do... 00:46:12.010 --> 00:46:12.300 >> Absolutely.... 00:46:12.350 --> 00:46:14.770 >> all these things that, for all intents and purposes, people 00:46:14.820 --> 00:46:18.580 don't know, which, of course, makes the change that much more... 00:46:18.630 --> 00:46:19.730 we'll call it traumatic. 00:46:19.780 --> 00:46:22.500 >> And limits your ability to be successful in that quickly. 00:46:22.550 --> 00:46:22.960 >> Right. 00:46:23.010 --> 00:46:26.550 >> Right. And this is all about taking the practices that make 00:46:26.600 --> 00:46:29.850 the most sense and have been proven out over time and applying 00:46:29.900 --> 00:46:31.320 them in the order that you want. 00:46:31.370 --> 00:46:36.280 >> And the part that gets me is ultimately, it's your choosing. 00:46:36.330 --> 00:46:39.630 And most of the time, we're used to implementations that we basically 00:46:39.680 --> 00:46:42.370 have to buy, and implement as is. 00:46:42.420 --> 00:46:42.850 >> Absolutely. 00:46:42.900 --> 00:46:45.480 >> But it seems like here, at least, that's actually very much 00:46:45.530 --> 00:46:48.420 so not the case, which technically makes it a much easier sell 00:46:49.290 --> 00:46:50.460 to the powers that be. 00:46:50.510 --> 00:46:53.730 >> The other thing that's really amazing and a lot of people don't 00:46:53.780 --> 00:46:58.280 know is that you don't actually buy TFS. You can buy it, you know. 00:46:58.330 --> 00:47:01.320 You've got Visual Studio Online that you can use for free for 00:47:01.370 --> 00:47:02.380 five users. 00:47:02.430 --> 00:47:04.570 >> Whoa, whoa. Free for five users? 00:47:04.620 --> 00:47:05.190 >> Free for... 00:47:05.240 --> 00:47:05.730 >> Unlimited? 00:47:05.780 --> 00:47:09.980 >> Unlimited. For five users. Now, you will have limited number 00:47:10.030 --> 00:47:12.570 of user minutes for your load test. 00:47:12.620 --> 00:47:12.740 >> Fine. 00:47:12.790 --> 00:47:13.330 >> Makes sense. 00:47:13.380 --> 00:47:13.800 >> Makes sense. 00:47:13.850 --> 00:47:15.490 >> Limited number of build minutes. 00:47:15.540 --> 00:47:16.070 >> Fine. 00:47:16.120 --> 00:47:20.560 >> Not limited... when I say limited it's, you know, I can only 00:47:20.610 --> 00:47:25.010 run the equivalent of about 50,000 user hours of load time a month. 00:47:25.060 --> 00:47:26.200 >> Oh, you know, only 50,000. 00:47:26.250 --> 00:47:26.860 >> A month. 00:47:27.510 --> 00:47:29.110 >> A month. And then they reset every month. 00:47:29.160 --> 00:47:31.340 >> Yeah, and they reset every month. So, you know, if I want 00:47:31.390 --> 00:47:35.860 more, I can pay for it by number of user. But it's a significant 00:47:35.910 --> 00:47:36.790 amount for free. 00:47:37.460 --> 00:47:42.080 But if you have at least one MSDN subscription in your organization, 00:47:42.130 --> 00:47:45.090 you have TFS, you own it. It's included. 00:47:45.140 --> 00:47:46.460 >> Including all this stuff you just went through? 00:47:46.510 --> 00:47:50.060 >> Including everything I've shown you. So, I mean, there is 00:47:50.110 --> 00:47:53.630 Visual Studio... of course, if you start to use the more enterprise 00:47:53.680 --> 00:47:56.800 features, the more capable features in different versions of 00:47:56.850 --> 00:48:01.070 Visual Studio, you still have to acquire those. But it comes 00:48:01.120 --> 00:48:03.730 as a benefit of MSDN subscriptions and 00:48:04.960 --> 00:48:05.580 Visual Studio. 00:48:05.630 --> 00:48:08.880 >> And ultimately, can I add on each step, or do I have to just 00:48:08.930 --> 00:48:09.970 get everything all at once? 00:48:10.020 --> 00:48:13.010 >> No, you can start off, for example, if you have Visual Studio 00:48:13.060 --> 00:48:15.990 Professional today and you want to use to Premium to get some 00:48:16.040 --> 00:48:19.730 more features, and Premium is the one that most of our large 00:48:19.780 --> 00:48:22.910 customers standardize on, because the benefits are so good. 00:48:22.960 --> 00:48:23.100 >> Right. 00:48:23.150 --> 00:48:27.690 >> I mean, you get access to every Microsoft technology for the 00:48:27.740 --> 00:48:30.310 purposes of dev and test. So if you're doing SharePoint development, 00:48:30.360 --> 00:48:33.670 dynamics development, SQL development, Windows development, it's 00:48:33.720 --> 00:48:37.060 an all-you-can-eat environment for yourself. It slices per user. 00:48:37.110 --> 00:48:38.460 >> All you can eat, love it. 00:48:38.510 --> 00:48:41.160 >> All you can eat. And I'm very familiar with all you can eat. 00:48:41.210 --> 00:48:42.910 >> It is lunch time and/or breakfast. 00:48:42.960 --> 00:48:43.120 >> Yeah. 00:48:43.170 --> 00:48:43.860 >> So... 00:48:43.910 --> 00:48:47.650 >> So, you know, in the Visual Studio IDE, I just connect up and 00:48:47.700 --> 00:48:49.580 it lights up. The more... 00:48:49.630 --> 00:48:55.190 the more you use a TFS, the more it lights up and gives you more value. 00:48:55.240 --> 00:48:57.430 >> Love it. So I see you have Visual Studio on your screen now. 00:48:57.480 --> 00:48:59.810 Does that mean we're going to go see something in Visual Studio? 00:48:59.860 --> 00:49:02.560 >> Well, I was just going to highlight that the Visual Studio 00:49:02.610 --> 00:49:07.170 IDE includes first class connectivity to Team Foundation Server 00:49:07.220 --> 00:49:09.660 and I can do things like work with my source code. 00:49:10.300 --> 00:49:13.600 If I'm using Visual Studio Premium, I also get things like my 00:49:13.650 --> 00:49:17.120 work, which shows me the work that I'm working on at any point 00:49:17.170 --> 00:49:20.220 in time, allows me to pick from items that have been assigned 00:49:20.270 --> 00:49:24.760 to me. It co-relates changes to code that I'm making and even 00:49:24.810 --> 00:49:29.380 lets me enlist other people in my team in code reviews, which 00:49:29.430 --> 00:49:34.100 is an included work flow. So it's a very functional UI that's 00:49:34.150 --> 00:49:39.780 tied to the ALM experience that you've adopted. But there's 00:49:39.830 --> 00:49:42.330 one other capability I wanted to talk about, because we talked 00:49:42.380 --> 00:49:45.180 about it a couple minutes ago, and it applies to everybody. 00:49:45.230 --> 00:49:48.580 Is, you know, the whole purpose of ALM and getting there is actually 00:49:48.630 --> 00:49:51.040 to produce software. And once we've produced the software, we 00:49:51.090 --> 00:49:52.330 kind of have to deploy it. 00:49:52.380 --> 00:49:54.900 >> Really? I thought the whole point of ALM was to produce reports. 00:49:54.950 --> 00:49:55.820 >> Yeah, well... 00:49:55.870 --> 00:49:56.920 >> For the bosses. 00:49:56.970 --> 00:50:00.800 >> Typically, in the past, perhaps that was the case. TFS takes 00:50:00.850 --> 00:50:03.560 care of all that for you so you don't have to worry about that. 00:50:03.610 --> 00:50:06.210 But, you know, at the end of the day, this is all about producing 00:50:06.260 --> 00:50:10.590 software that we can put into different environments for testing 00:50:10.640 --> 00:50:13.690 or production. So I'm actually going to bring up the new component 00:50:13.740 --> 00:50:17.450 of Visual Studio called Release Management. And in Release Management, 00:50:17.500 --> 00:50:19.400 we can configure our applications. 00:50:20.070 --> 00:50:22.810 For example, I've got a call center application here, and if 00:50:22.860 --> 00:50:28.030 I open that up, I can actually see information about how I'm 00:50:28.080 --> 00:50:32.900 going to deploy that application and define the work flows and 00:50:32.950 --> 00:50:37.090 configuration on the different machines using this tool. I can 00:50:37.140 --> 00:50:40.930 actually configure the paths for deployment so I can say, you 00:50:40.980 --> 00:50:45.030 know what? I've got a number of different environments like dev, 00:50:45.080 --> 00:50:47.380 prod and QA. I've got 00:50:48.720 --> 00:50:52.870 servers defined in those environments and even paths for release. 00:50:52.920 --> 00:50:54.700 So I can actually say, you know what? 00:50:55.430 --> 00:50:59.450 I want my app to go through these environments and in each step, 00:50:59.500 --> 00:51:04.320 I might want to have automated or interactive approval work flows 00:51:04.370 --> 00:51:07.580 that happen so that I can control when the application moves 00:51:07.630 --> 00:51:11.170 from one environment to another, who is responsible for making 00:51:11.220 --> 00:51:15.000 sure they approve the application moving to that point, and then 00:51:15.050 --> 00:51:18.200 the tool will actually do that and report back to you. This is 00:51:18.250 --> 00:51:22.100 a brand new capability. It solves some huge problems for our 00:51:22.150 --> 00:51:27.230 customers, and it's included with Team Foundation Server in Visual Studio. 00:51:28.070 --> 00:51:29.470 >> But not in the cloud this time. 00:51:30.300 --> 00:51:33.710 >> Well, interestingly enough, it's only for on-premise right now. 00:51:33.760 --> 00:51:34.360 >> Fair enough. 00:51:34.410 --> 00:51:38.090 >> But it does allow you to deploy to Azure virtual machines. 00:51:38.140 --> 00:51:42.260 It can start and stop virtual machines in the cloud and deploy 00:51:42.310 --> 00:51:42.810 to them. 00:51:42.860 --> 00:51:45.460 >> Huh. So the part that's killing me right now as I'm watching 00:51:45.510 --> 00:51:48.670 you go through this demo is I'm just thinking I'm going to have 00:51:48.720 --> 00:51:51.460 one of those moments of back in the day again. So back in the 00:51:51.510 --> 00:51:55.390 day, when all of this stuff wasn't available, I actually remember 00:51:55.440 --> 00:51:58.480 going through release management plans. We would write documents 00:51:58.530 --> 00:52:02.700 for the longest time. We would have a gazillion people review them. 00:52:02.750 --> 00:52:06.930 A gazillion updates only to not actually follow it anyway. 00:52:07.210 --> 00:52:08.070 >> Yep. 00:52:08.120 --> 00:52:12.640 >> Sorry. We did follow it. We got the apps into production. 00:52:13.250 --> 00:52:16.440 It's okay. I don't work there anymore. Point being, all of this 00:52:16.490 --> 00:52:20.540 stuff you now have for me in a... effectively, what is a work flow. 00:52:20.590 --> 00:52:23.250 >> Well, and the best part about it is it's mechanical. 00:52:24.030 --> 00:52:27.240 And the mechanical nature of any of this is the reason why people 00:52:27.290 --> 00:52:31.570 adopt things like build processes, automated testing and release 00:52:31.620 --> 00:52:34.730 management is that it's not subject to somebody having a bad 00:52:34.780 --> 00:52:38.760 day or being forgetful, somebody being sick or away. 00:52:38.810 --> 00:52:40.990 >> Doing deployments at 2:00 in the morning when you've had a 00:52:41.040 --> 00:52:41.870 full day of code. 00:52:41.920 --> 00:52:44.590 >> Right. When it's mechanical and it does it all the same way 00:52:44.640 --> 00:52:48.010 every time, it's also auditable and traceable. You have a kind 00:52:48.060 --> 00:52:50.380 of a guaranteed work flow that you can count on. 00:52:51.470 --> 00:52:54.360 And once it's in place, you can do it more often too. So it 00:52:54.410 --> 00:52:59.290 supports the idea of automated releases, but also supports the 00:52:59.340 --> 00:53:02.880 concepts of Agile, where I'm releasing very frequently and getting 00:53:02.930 --> 00:53:04.600 a lot of feedback from my users. 00:53:04.650 --> 00:53:06.640 >> The one thing... the two things, actually that you kind of 00:53:06.690 --> 00:53:10.610 glossed over there that were also big deals is you said auditable. 00:53:10.660 --> 00:53:13.010 What was the other one? There was another one after that. 00:53:13.060 --> 00:53:13.910 Consistent, I think. 00:53:13.960 --> 00:53:14.710 >> Consistent. 00:53:14.990 --> 00:53:16.420 >> The point being, right... 00:53:16.470 --> 00:53:17.460 >> Like a pretty bird. 00:53:18.850 --> 00:53:22.390 >> The point that being when you're in a larger organization where 00:53:22.440 --> 00:53:26.160 ultimately, you know, you have all this processes for splitting 00:53:26.210 --> 00:53:29.580 between developer and implementation and all that kind of stuff, 00:53:29.630 --> 00:53:32.650 you need that capability to do the audits. You need to be able 00:53:32.700 --> 00:53:37.310 to have that sense of removal and that sense of automation. 00:53:38.080 --> 00:53:40.530 And now, basically, with release management, you have all of 00:53:40.580 --> 00:53:43.510 that built in right into the tool, taking it from your assets 00:53:43.560 --> 00:53:45.070 you have in TFS. 00:53:45.120 --> 00:53:47.780 >> Perfect. How good could that be? 00:53:48.570 --> 00:53:51.700 >> As far as I'm concerned, having been the one that had to sign 00:53:51.750 --> 00:53:54.290 off on all the releases and whatever, and I'm sitting there, 00:53:54.340 --> 00:53:56.430 I'm like did you do this, did you do this, did you do this? 00:53:56.480 --> 00:53:59.080 I can now actually go into the logs and say yes, this was done, 00:53:59.130 --> 00:54:00.320 this was done, this was done. 00:54:00.370 --> 00:54:03.740 >> Absolutely, you can. And you can come back and whether you 00:54:03.790 --> 00:54:07.200 decide you want to use a... the graphical tool, the rich tool 00:54:07.250 --> 00:54:11.920 that we have or the browser-based UI, it will do email notifications 00:54:11.970 --> 00:54:13.380 to let you know you have to approve. 00:54:13.430 --> 00:54:14.610 >> Is that what you're doing here on your screen? 00:54:14.660 --> 00:54:17.670 >> I'm seeing the... I'm seeing an activity where we triggered 00:54:17.720 --> 00:54:20.590 a build for a release so I'm actually going to create a new release 00:54:21.120 --> 00:54:25.840 and I'll just actually say, I want to release the Fabrikam call 00:54:25.890 --> 00:54:31.130 center app to prod using the latest build. And it will kick 00:54:31.180 --> 00:54:35.360 off a build or grab a build from Team Foundation Server and away 00:54:35.410 --> 00:54:38.060 I go. So I can actually take it from a drop location. I can 00:54:38.110 --> 00:54:42.950 kick off a new build, and now we're actually actively building 00:54:43.000 --> 00:54:47.010 the software application and deploying it, and it's going through 00:54:47.060 --> 00:54:49.070 the whole release sequence 00:54:50.560 --> 00:54:54.110 from dev to prod, and all the steps in between, and I will get 00:54:54.160 --> 00:54:57.300 approvals requested of different users and I have to wait for 00:54:57.350 --> 00:55:01.310 them to approve. I can see what states happening and it's using 00:55:01.360 --> 00:55:04.800 all of the activities that I've defined for deployment as part 00:55:04.850 --> 00:55:05.630 of this process. 00:55:05.680 --> 00:55:08.600 >> I think I'm going to keep the screen on these guys, because 00:55:08.650 --> 00:55:12.340 I think I'm going to go over here on the side and cry for a bit 00:55:12.390 --> 00:55:15.900 just because I remember having to do this at 3:00 in the morning 00:55:15.950 --> 00:55:20.620 by paper and email. And now, no such thing. 00:55:20.670 --> 00:55:21.340 >> No such thing. 00:55:21.390 --> 00:55:23.410 >> No such thing, okay. So now that I'm done crying, you guys 00:55:23.460 --> 00:55:26.510 can see any back here, which actually seems like a really good 00:55:26.560 --> 00:55:28.710 place to kind of end off for today. 00:55:28.760 --> 00:55:31.110 >> We've talked a lot about a whole bunch of things today. 00:55:31.160 --> 00:55:31.940 >> Full circle. 00:55:31.990 --> 00:55:35.550 >> And I encourage people to go take a look at the virtual launch, 00:55:35.600 --> 00:55:37.470 because we recorded that and made that available. 00:55:37.520 --> 00:55:39.220 >> And that's at events.visualstudio.com. 00:55:39.770 --> 00:55:40.650 >> Events.visualstudio.com. 00:55:40.700 --> 00:55:42.290 >> Not that I memorize my URLs or anything. 00:55:42.340 --> 00:55:45.490 >> And you're going to post that in the comments of the session today. 00:55:45.540 --> 00:55:48.000 I know that. And also... 00:55:48.050 --> 00:55:49.310 >> He has a lot of faith in me. 00:55:49.360 --> 00:55:50.000 >> I do. 00:55:50.050 --> 00:55:50.680 >> Thank you. 00:55:50.730 --> 00:55:55.460 >> And also, I encourage people if they're in the Toronto area 00:55:55.510 --> 00:55:59.130 or in the Montreal area to come out to the Visual Studio launch events. 00:55:59.180 --> 00:56:02.040 I think you'll get a great chance to ask questions about this technology. 00:56:02.090 --> 00:56:03.090 >> For sure. 00:56:03.140 --> 00:56:06.200 >> You'll see the local Visual Studio teams there that you can 00:56:06.250 --> 00:56:10.960 talk to about anything particular about your organization or 00:56:11.010 --> 00:56:14.300 even if you want to talk about licensing and what you need, they're 00:56:14.350 --> 00:56:15.220 going to be there. 00:56:15.970 --> 00:56:18.210 And try the tools out. I mean, this stuff... 00:56:18.260 --> 00:56:18.710 >> Can't get any better.... 00:56:18.760 --> 00:56:22.080 >> is live now, and it's that powerful. I'm not... you know, 00:56:22.130 --> 00:56:25.610 we're not... none of this was prepared demo software. We didn't 00:56:25.660 --> 00:56:28.580 do anything that wasn't flying by the seat of our pants. 00:56:28.630 --> 00:56:33.060 And when a monkey like me can get it done, generally anybody 00:56:33.110 --> 00:56:34.460 out there can get it done too. 00:56:35.310 --> 00:56:38.410 >> He says this, but he practices demos every once in a while. 00:56:38.460 --> 00:56:40.820 It's not like this is the first time you've talked about this stuff. 00:56:40.870 --> 00:56:42.930 I did throw a couple monkey wrenches in there. 00:56:42.980 --> 00:56:46.940 >> Yes, you did. But I also wanted to say, J.R., thank you very 00:56:46.990 --> 00:56:51.290 much for including me as the first person, the first guest in 00:56:51.340 --> 00:56:53.240 this new Breakpoint series. 00:56:54.880 --> 00:56:56.910 >> With content like that how could you not be the first? 00:56:56.960 --> 00:56:59.060 >> It's a dubious honor, I must say. 00:56:59.720 --> 00:57:03.320 And it can only go uphill from here. So, you know, thank you 00:57:03.370 --> 00:57:05.290 everyone for tuning in. 00:57:05.340 --> 00:57:07.720 >> Don't thank me. Thank them. They're the ones that took an 00:57:07.770 --> 00:57:08.490 hour of their day. 00:57:08.540 --> 00:57:11.080 >> I know. And you'll get some on-demand requests as my fore finds 00:57:11.130 --> 00:57:11.730 out about this. 00:57:11.780 --> 00:57:12.620 >> Well, mine too. 00:57:13.670 --> 00:57:15.800 >> That's always good. It's traffic. 00:57:16.180 --> 00:57:18.740 >> Now, having said that, though, now that he's done his piece, 00:57:18.790 --> 00:57:22.570 a couple of things left for me. So we'll actually have this video 00:57:22.620 --> 00:57:25.050 on demand for you probably in the next couple of days or so. 00:57:25.700 --> 00:57:30.290 Check back on the CDN devs Twitter handle and you'll get the 00:57:30.340 --> 00:57:33.780 notification of when the video is actually on demand, or you 00:57:33.830 --> 00:57:37.820 can actually look us up on Channel 9. Channel9.msdn.com and 00:57:37.870 --> 00:57:41.470 just do a search for Breakpoint. It looks kind of empty. I mean, 00:57:41.520 --> 00:57:44.350 not as sexy as I would like it to be at this point but that because, 00:57:44.400 --> 00:57:47.760 hey, guess what? Pilot episode so cut me some slack. We'll get 00:57:47.810 --> 00:57:52.160 some good stuff on there for you in the meantime. And, of course, 00:57:52.210 --> 00:57:55.220 so mark your calendars so at this time next month... 00:57:55.270 --> 00:57:58.620 actually, might not be next month because it's like crazy vacation 00:57:58.670 --> 00:58:00.110 season, but we'll see. 00:58:00.160 --> 00:58:03.350 >> And it would be the 22nd of December. 00:58:03.400 --> 00:58:06.290 >> Basically, the third Friday of every month we're going to try 00:58:06.340 --> 00:58:08.520 to do this and bring you the latest and greatest in the Visual 00:58:08.570 --> 00:58:13.220 Studio world. But like I said, stay tuned to Twitter, @CDNDEVS 00:58:13.590 --> 00:58:16.610 or the MSDN e-news newsletter. Or if you don't have it yet, you 00:58:16.660 --> 00:58:19.780 can subscribe for it. And we'll keep you posted as to when we 00:58:19.830 --> 00:58:20.780 get all this stuff. 00:58:20.830 --> 00:58:24.110 >> And download Visual Studio 13. Go activate your Visual Studio 00:58:24.160 --> 00:58:26.450 Online account and... 00:58:26.500 --> 00:58:28.190 >> Three things. You only get three things. 00:58:28.240 --> 00:58:29.500 >> The last one's really important. 00:58:29.550 --> 00:58:29.830 >> Yeah. 00:58:29.880 --> 00:58:33.680 >> If you haven't already done it, go activate your Azure benefits 00:58:33.730 --> 00:58:35.080 and start to make use of the cloud. 00:58:35.130 --> 00:58:38.560 >> Of course. If nothing else, because maybe you watch some of 00:58:38.610 --> 00:58:41.370 my other shows. We do a lot of really good stuff with Azure. 00:58:41.420 --> 00:58:45.240 But if nothing else, dev and test for sure. And actually, Adam 00:58:45.290 --> 00:58:49.720 has a really good session on Channel 9 for how to use your MSDN 00:58:49.770 --> 00:58:52.840 for this kind of stuff. It's a little bit more in detail. 00:58:53.110 --> 00:58:56.370 With that, we are at the top of the next hour, I guess. So we 00:58:56.420 --> 00:58:58.830 are going to go offline for now. We're going to stay on the 00:58:58.880 --> 00:59:02.000 chat for another half an hour or so, so keep the questions coming. 00:59:02.050 --> 00:59:04.760 We're happy to help. And again, if you're watching this on demand, 00:59:04.810 --> 00:59:08.070 just post the questions underneath the video and we'll get back 00:59:08.120 --> 00:59:10.620 to you as soon as we can. In the meantime... 00:59:10.670 --> 00:59:11.160 >> Thank you. 00:59:11.210 --> 00:59:13.700 >> Code well. I guess, what would be an appropriate sign-off? 00:59:13.750 --> 00:59:15.380 Code well? F5? 00:59:16.960 --> 00:59:17.310 >> F5. 00:59:18.000 --> 00:59:19.080 >> Build continuously. 00:59:20.250 --> 00:59:21.510 >> Continuously integrate. 00:59:21.560 --> 00:59:29.600 >> I love it. All right. See you in a month.