 I think we've blathered enough. Let's go and give some time to some amazing people. We got about 60 seconds before we go to them, but what we want to do is please make sure to stay tuned for all of the cool stuff. There's a lot of stuff that you're going to learn. There's a lot of fun stuff that we're going to do after and we want your comments. Above all, we want your questions. We will get them up here on the tag board. There's 24 already. I'll push this button and then we'll start to ask them. I'm going to be the Vanna White today of Visual Studio 2019. I'm very excited about that. Without further ado, let me introduce two people. Well, let's have you introduce yourselves. We have Joseph and Amanda. Tell us who you are and what you do. We'll start with you, Amanda. Sure. I'm Amanda Silver. I'm the Director of Program Management for Visual Studio and VS Code. Fantastic. I'm Joseph Hill. I'm Director of Program Management for Visual Studio for Mac and Xamarin. VIPs, as we like to call you too. Why don't you give us a small recap of the stuff that we talked about. A tiny one so that we can get the pump primed for people to ask questions. We'll start with you, Joseph. Well, yes. So as I said, Visual Studio for Mac and Xamarin. Pretty excited. I think Visual Studio 2019 developers will be super excited about the improvements we've made to performance and stability for both Xamarin and Visual Studio for Mac. In Visual Studio, we've reduced the download size a lot. So as you're going through and installing Visual Studio 2019 today and you're thinking, oh, can I put 25 gigs of mobile development tools on my desktop? It's like one-third that size now. So you should definitely opt in to that. Fantastic. So just zip stuff up or what is it? Yeah, that's right. We would like somebody introduced us to this archiving tool and they were like, wow, this is great. Why are we using this? We parted DGZ at all up. That's awesome. Amanda, what about for you? Yeah, I mean, I think today is the big news of Visual Studio 2019 being ready for everybody to take on. So there's a kind of get first start experience so that you can really get into the flow with your code that your other teammates are working on. There's Visual Studio Live Share kind of in the Visual Studio 2019 box out the gate. So basically we have both collaboration at the check-in time so that you can actually go and review pull requests and things like that inside of Visual Studio, but also pre-check-in. So you can actually have a real-time collaboration session with somebody else that you're working with. The other things that are super exciting are Visual Studio and Telecode. We talked about which basically is kind of the first steps towards allowing AI and machine learning to basically enhance your productivity as a developer. But there's so many things that I can't even name all of them, right? We've improved the UI a little bit so that it just feels a lot cleaner. So you have headspace to kind of focus on the code that you're writing. We've improved the search capability in Visual Studio 2019 so you can actually discover new features that you might not have been familiar with previously. One of my favorite features is actually that we've moved the C++ debugging out of process. And so that has been absolutely huge for people who are working on very large-scale C++ applications, especially folks like those that are working on AAA games because they used to have a situation where they would basically run into out-of-memory exceptions in the debugger after about like five, 10 minutes of coding. And then all of a sudden now they really don't run into those things anymore. They can have half-hour, couple-hour-long debugging sessions. And that's pretty amazing because I saw there was actually debugging like a huge game and just like a game by itself is pretty big. And now when you have all the debug symbols and you have to keep track of all, I mean it's pretty amazing what you're able to do with that. Yeah, we have a lot of testimonials from folks who are building large-scale C++ applications that it really is a game changer. Awesome. So let's get to the questions and then I'll intersperse with some of mine. We have here my friend Toby Loba. What features do the Community Edition ship with? So actually our Community Edition is actually exactly the same as our Professional Edition. It just has different licensing restrictions on it. So any of the features that are in our Professional Edition are also available in the Community Edition. And obviously that's thousands and thousands and thousands of features. I can't name all of them. That's cool. So let's start a little bit with some of the streamlining that happened. You both mentioned there was some streamlining that happened with Visual Studio. Can you talk a little bit more in-depth about that? I did notice myself because I installed the RC last week. There was some snappiness to it. How did we make it a little bit faster? I know this happened in Visual Studio for Mac as well as Visual Studio for Windows, yes. Yeah, so just to start with Visual Studio for Mac, we've started to take code from Visual Studio over to Visual Studio for Mac. And luckily like our editor is where we've been putting a lot of the work. It's written in C-Sharp. We, Microsoft's already had an editor written in C-Sharp. So being able to bring it over to the Mac results in like, we have like 95% of the code for our new editor coming from the Windows implementation. But it's also snappy because we were able to move to a native Cocoa front end. And so we get like native scrolling and better support for right to left, rendering, WordWrap, a lot of features we couldn't do in our previous editor. We're able to do through building on a native rendering base with what you said, streamlining is where it's at, bringing over Visual Studio code. And we're eyeing the future, the roadmap, more features that we can bring over from Visual Studio and develop features in conjunction with Visual Studio. Amanda mentioned earlier, get to code. We're super excited about that because it's a feature we were able to bring to both IDEs at the same time with launch today. What does get to code mean? So get to code is basically the idea that we want you to get into your coding environment and become productive in the zone while you're programming as quickly as possible. And so Visual Studio originally was designed in an era when everything was installed on a bunch of disks that you would buy off of a shelf at some large big box digital store. And then you'd install all of it, including help and all of the templates and all of that kind of stuff. Nowadays, a lot of developers really start with either hosted repositories that are hosted in a private server or hosted in a public repository. And so if that's really where people are starting, we wanted to make sure that that is a really super productive experience inside of Visual Studio 2019. So if you open up Visual Studio 2019, you're gonna see kind of a streamlined start experience where the options are start from an online repo, start from a template, create a new project, start from an open project or anything that you've opened recently and so on. And so you can really get into the zone of coding as quickly as possible. Honestly, that's probably one of my favorite features where I started up and it actually starts up. Now, I wanted, you were gonna talk, it's usually like it took a long time book, I'm being honest here, we're all friends here. But now it's like really snappy, I get to what do you wanna work on? Yep, I think that's really the goal is we wanted to make sure that everybody who's new to the product but also those who have been using the product for years and years and years can basically get into the zone coding as quickly as possible. Now, Joseph mentioned a little bit about some of the streamlining that happened in Visual Studio for Mac. Can you describe a little bit some of the streamlining that went on in Visual Studio for Windows? Well, I mean, in some ways, so Joseph was talking a lot about kind of the installer and things like that. And we have definitely improved the install experience, the update experience and things like that in Visual Studio 2019 a lot. But some of the ways that it's been streamlined are actually kind of UI changes. So if you start up Visual Studio 2019, you might notice that there's a slight color theme change from Visual Studio 2017. And if you put them side by side, you'll actually, I find that Visual Studio 2019 feels just cleaner and you're not really quite sure why. But we've done a lot of work to actually make sure that we've cut bezels and we've cut repetitive text and stuff like that so that you can really be focused on your code. We've also kind of streamlined the menuing system so that it actually occupies one less row so that you have one more row of code that you can focus on. And then I think the other thing is with the enhanced kind of search experience, you now don't need to as often hunt and pack through the menuing system to find the thing that you need. What I find using Visual Studio 2019 is if I wanna use a certain feature or install a component that I hadn't installed previously, that I can actually just go to the search menu, type whatever I'm looking for and it'll come up there and it'll then kind of streamline my experience exactly to the menu that I need. Awesome. Joseph, do you have something? I was just gonna add to that, yeah, cuz on Xamarin, especially Impactfuls, we really improved the solution load time and solution creation time. So that's a snappier feel to you when you're able to do that. Yeah, I mean I didn't even touch on that. But performance is absolutely huge. I mean I talked about the C++ debugger being out of Proc and the impact that that has. But we've also done some pretty amazing things in terms of solution load time, project load time, as well as unit test discovery. So that it's now getting started in any typical project is tens of percentage points better. That's awesome. I personally noticed it. Like I said, I've been doing a lot of work in Visual Studio code with Python. And they said, they were like, hey, you gotta do the same thing. I think I'm like, and they said, hey, you can do Python in Visual Studio. I'm like, can you? And I went in there and it's surprising. It felt like I was back in my C sharp days, but it was Python, which is really cool. All right, from Frank Ofoedu from all the way from Nigeria. Will there be an offline ISO installer for the community version? This will help developers here who don't have stable internet connection there. Yeah, so we actually haven't been doing an ISO installer with 2017 or 2019. What we have is a layout option so that you can actually create your own offline installer and then access it that way. So you could certainly use Azure or something like that to create that layout and then install it from there. Cool. All right, so from Ken, we have, can a single developer release a commercial app on Community Edition if there are restrictions? Can you please elaborate? Yeah, so the Community Edition is basically four teams that are smaller than five. So that is definitely something that's supported with the community. Awesome, here's another one from Shannon. Will there be an issue if my team uses VS 2017 and check in code to get while using 2019? Will we be constantly buying for updates of the solution project files? Meaning is it the solution different? So the solution generally should not be different. You should be able to actually collaborate on them. But for the most part what we suggest is that you have basically a team that's kind of looking at migrating your solution to 2019. You can do this on the same box. So I think the important thing is that an individual developer can kind of go and survey the new release and they can do it side by side on the same box without actually impacting the rest of their source code or the stability of their 2017 install and evaluate it and then kind of migrate the team over to the 2019 version. I see, and this goes to a little bit of what Samuel is asking here. Can you upgrade from VS 2017 to 2019? You can actually have them both at the same time and not even interfering with each other, is that right? That's right, so you can install 2017 right next to 2019 and actually, in fact I do use some sometimes and when the other times. One of the things that we've really worked on in the last version is streamlining the upgrade experience from 2017 to 2019. So where in 2017 you would have to kind of pick the workloads, basically pick which SDK is what project types you wanted to work on. If you've already done that in 2017, then your update experience to 2019 should be super, super easy because we've basically migrated all of your settings, all of your workloads to the 2019 installer. Now here's a fun question. Was there any really big features that you wanted to include but did it make the cut? Now it feels like recently Visual Studio we've been putting out stuff super early. It's not like it used to be like we'd wait two years and then it would come in this huge box. Tell us a little about how you plan and what goes into releases. You wanna take that one, Joseph? Well sure, yeah, I mean it speaks right to the heart of the VS for Mac release. We listen to feedback from users and we test features as we're going. And the really big push that we have for VS for Mac 2019 is to switch the editor over to that editor I was describing earlier. That's a preview today in VS for Mac 2019. You can go into your preferences and select the new editor. It's a great experience and I recommend you do it. Right now it's in C sharp but we held it back from turning it on by default because just wasn't the right call, wasn't the best thing for users. But as that comes online, in updates to 2019 we'll have it on by default very soon followed by additional languages, XAML, JavaScript, Razor Blazer, etc. Awesome. Yeah I mean so I, especially with our update cadence where we now have preview releases coming out super regularly and we have updates coming out every few weeks or so. I never feel terrible about actually not getting a particular feature into Visual Studio because I know that it's coming down the road super quickly. There are a couple that are in basically like preview at this point. That will make it into an update shortly. One that comes to mind is time travel debugging. Another one is the IntelliCode kind of being in the box. Another one is the PR experience. All of those things will be coming up in future updates. And I think one of the things that's really changed over the last couple of years in terms of how we manage Visual Studio and kind of talk about it with the community is we're actually pretty transparent about what our roadmap looks like. And so you can actually look for Visual Studio roadmap and you can see all of these features that are coming down the pike. Yeah and this is very different than what it used to be because I remember we would just be like, wow, it's out. But I have talked to, for example, just with languages. With Matt Storgeson, I have talked to him years in advance before some like C Sharp AIDS coming out and I talked to him like a year and a half ago about the features that they were just thinking about, which is pretty cool. Now I'd like to move on to IntelliCode because I'm a machine learning person. And this is an interesting question that we're going to table just for a second while you talk about IntelliCode. What is it? And maybe there's some concerns that people have. How do you address them? For example, he's worried if IntelliCode suggests code according to what most people use, couldn't that cause bad practices around the world as a result of most people using old inefficient practices? Yeah, so I mean, IntelliCode is the first steps in a long road towards allowing machine learning to enhance your developer experience. And so the first thing that we did is we actually trained it on public repos that were highly rated. And so we assumed that if they were highly rated that that probably meant that they were decent code. What we've now added is the ability to train your IntelliCode machine learning models on your own custom code, even private code. That's unique to your team. And so you actually can select which repos you use to train those models. Yeah, so it's basically you get to choose what models you do. Yeah, that's right. And not only that, once you do that, once you choose to train on a model, which might take a couple of minutes to get the model back because it actually has to go and kind of calculate it in the cloud, create the machine learning models. You can actually share that model with your other teammates. So let's say you're a developer that's inside of a large enterprise with lots of developers on it. And you build a common framework for your team. You could actually train the IntelliCode model on that common framework and then share that model just like you would share any kind of a source repo with the other developers on your team. So they don't even need to go through the process of training it on that custom library. You've done that, you've curated that, and then you can make sure that they have the most productive experience on that library. And I think that's an important distinction, right? Because he brings up a good point. What if it's not according to the way we want to do it? That's the way I read it. You can actually use your own code and train it on that and have your own style as a company in the model. Okay, a couple more questions. There's one new coming in here. This one's a funny one. How fast can I install Visual Studio 2019? So the absolute minimum installer for Visual Studio 2019 should take about two and a half minutes. But of course, that comes with no workloads. So what you're going to get with that is basically like a lightweight editing experience with lightweight language services. So you might get some grammar and syntax, you might get some grammar and syntax checking, but not really kind of semantic analysis. It's pretty fast. I mean, I downloaded a couple of workloads and it was like I always check all the things, which I probably shouldn't do. And that takes a little bit of time because you're downloading a lot of different workloads, but I feel that the greatest thing is you have choice in what it is that you put on. Yeah, that's for sure. I mean, we've definitely been working to try to make sure that our installers for various workloads are a lot more lightweight. Yeah, that's why I smiled when I heard the question because I was like, man, depending on the configuration, the install times have just dropped so significantly. And yeah, minimal two minutes sure, but for your workloads you're going to be pleased. Because we learned how to zip, of course, we just figured out. Here's a really important question, is a new Visual Studio 2019 editor ADA compliant? Yeah, so we've definitely been working on improving the accessibility of Visual Studio 2019 for a couple of years. And actually 2017, I believe, was ADA compliant. But we continue to work on that and improve that. Okay, awesome. So what other features did you really, we talked about speed. We talked about, we talked about IntelliCode a little bit. Is there another feature that you feel people should really look at in Visual Studio 2019, or both of you? Putting you on the spot here. Well, I sure leapt in to fill some audio space. I'm stalling for Amanda because I know she didn't have a great one. No, I mean, I think some of the stuff that we've done, like for example, we've introduced debug search. So basically if you're in the middle of a debugging session, you can actually go and search for different levels of all of the variables that you might want to get values for. So you can basically kind of search on possible expressions that you might want to evaluate in the debug session. We have a lot of new, like refactoring features. So one of the big capabilities that we've introduced is code cleanup. So you can actually kind of go and, you know, if you have style guidelines with an editor config, which actually can be inferred using IntelliCode, then you can actually go and just hit a hot key. Control D for most people, and it'll clean up that entire file. So there are tons of goodies like that. But we also didn't even talk about kind of deploying to Azure, right? So, or to Docker or containers or Kubernetes. So a lot of kind of what we've also been working on is making it so that, you know, cloud native applications are super easy to author with Visual Studio 2019. That's cool. Yeah, because I mean, we can write all the code we want, but if it falls in the forest and there's no one around, does it even make a sound? It's, we got to put it in the cloud, right? A question for you. When will the Python tools in Windows version land in the Mac version? No ETA yet. I think we're definitely listening to feedback there, interest. We have the ability to add new languages, and we're doing that all the time. But, you know, Python's not, it's not on the immediate delivery. But hey, reach out to me. Yeah. I would love to hear how you want to use Python. If enough people yell at Joseph. That makes it happen. I'm just saying. We had donuts here this morning because we all yelled at Joseph. All right, from Evan. How do I get the new colorization of the text in VS 2019? If the installer is automatically importing my 2017 color configuration? So, this question is slightly ambiguous. I will answer it in two ways, kind of assuming that it's two different questions. So one is, I spoke a little bit earlier about the theming updates in Visual Studio 2019. So that, if you're using the default light theme, then that, you'll just automatically get the default light theme. You can always go back and reset your settings for the theme and kind of set it to the default light theme, and then you'll get those new kind of color options. That doesn't necessarily impact your text editor options. Because if you have your own custom settings for what you want your editor to look like, then that will override what our default theming does. And so for that, you'd have to go into tools options and basically reset, yeah. So we care more about what they set in there as opposed to what we want? Yeah, because there are a lot of people who have very particular preferences. I saw somebody, I think this was an April Fools joke, but I saw somebody yesterday who was talking about the hot dog theme that they'd like to set on their colleagues. So that basically it's a red background with yellow text. So if somebody steps out without locking their machine, they do that. That would be, I would spill my drink, I'm just saying. From Sander, is there an option to show the current solution to the title bar? I believe we had it before. Yeah, so there actually is an option to go into tools options and reset the title bar back. So there's just a lot of resetting then if you want to go in there. Here's a question, will live unit testing be available in the professional edition? No, live unit testing is a feature that's exclusive to Visual Studio Enterprise. Okay, next question from Ilias. Are you planning to work on improving development and debugging experience for Microsoft Dynamics CRM? Now here, this is an interesting question because when people ask this, I feel like there's like ten of us here at Microsoft and we're all like talking to each other. Why don't you describe what it takes to build something like this? Because everyone's gonna have a question of are you planning to work on foo for Visual Studio, why don't you describe this process? Sure, so the Dynamics CRM, I mean, this is a little bit of kind of insider baseball, but the Dynamics CRM team is obviously a different team than the Visual Studio team. And while we collaborate with each other, we're not sitting in the same room, we're not sitting in the same building. Sometimes we're pretty far away from each other. So while we might talk every couple of months about kind of what needs to happen, we're not talking all the time. And actually the Dynamics CRM like development experience that's in Dynamics CRM is part of the Dynamics CRM product, not the Visual Studio product. They have some extensions for Visual Studio. So all of the debugging improvements that are in C-Sharp that would show up there, show up in Visual Studio would show up for Dynamics. Having said that though, tell us what you want. Like if someone comes and is like, hey, we really want this foo product to be super good in Visual Studio 2019, we will go talk to whomever about whatever. I mean, you saw that in the keynote. Yeah, and it's also super important that if that's really important to you that you're also getting that feedback to the Dynamics team. Awesome. Oh, and I went, moved this one away. This is from Starling. For you, what's the main improvement of Visual Studio 2019? I know we kind of harp on it. But if you could condense it down to one thing, what would it be for you? I think the thing that most people are going to notice are that streamlining theme, and that I would include performance, UI improvements, the search experience, things like that that will basically just make you feel like you are sailing through code. That's awesome, Joseph. Yeah, I mean same, snappier, you're getting to code quicker. Get to code, that's the most visible thing, right? Improve get support. And yeah, you'll definitely feel it's a new idea. It's new, there's shyness. New is nice. I love it. From Dmitri, any news about Visual Studio extensibility in VS 2019? So what we've really been working on with the ecosystem in the 2019 era, as we've been developing it, is basically getting more things out of process and asynchronous. And so that really is improving the reliability and the performance of the core Visual Studio product. Awesome, so from Arwin, just to let you know, he installed the absolute minimum with no workloads. It's 2.5 minutes for him. I think that's what I saw. Yeah, which is awesome. We have community validation that this is actually the right thing. I just want to make sure that you knew that. Does VS 2019 have an ARM template validation and improved intelligence? Now ARM template, I'm assuming they mean Azure Resource Management. Yeah, so that's actually a highly requested feature that we're looking at for the next semester, basically. Cool, so here's a question about, because they're so excited. Actually, there is an answer to this question. Any idea about when will the telecode be available for VS code for C sharp? So the IntelliCode itself is actually something that's available for Visual Studio code. And it's actually the same extension for any programming language that you're programming in. So if you're doing Python or C sharp or TypeScript down the road, then it will just automatically pick up which programming language you're programming in and then the completion list will start to show up. Cool, and it's so subtle that you may not even know that it's just look for the little star. Yeah. Right, because sometimes I miss it, I'm like, oh yeah, that's the one I want. Yeah, that was a big debate. We were trying to decide if we should actually distinguish the IntelliCode recommendations or just change the reordering. And in the end, we decided to include the star just so that you know kind of what's coming from there. Because otherwise I think you probably wouldn't notice. Yeah. And you'd just feel more productive, but you wouldn't really know why. Not only that, but I feel like when it comes to AI things, we need to be pretty upfront that it's being generated by AI. Yeah, I agree. And a star is really good for that. Okay, so from M Kenyan. The second, what changes have you made for deploying to Docker VS1? You mentioned something a little bit about that. Yeah, I mean so we've actually improved a lot of the ASP.net kind of publish experience that you can actually go and deploy directly to a Docker container. We've made it easier to kind of discover a Docker container that you might want to attach to things like that. That's awesome. So next question, is there an integrated console in VS 2019 like code? Great feature in code, we'd love to have it in VS. I think what it means is an integrated terminal experience. So one of the things that actually this came from LiveShare when we found that people were collaborating, a lot of times the issue of like the bug repros on your machine but it doesn't repro on my machine, are actually due to environment setup and configuration. And the only way to kind of go figure that out is to actually go and get terminal access to the other person's machine. And so via LiveShare we kind of came, we increased the priority of introducing an integrated terminal in 2019 for the purposes of LiveShare. So now it is there. Cool, so that was a good answer. Yeah, absolutely. From Ishan Bhutani, how has VS 2019 improved over VS 2017 and performance parameters for low configuration devices? And maybe they mean like not so powerful machines. Yeah, it's a great question. I haven't looked at that specific question kind of those dimensions super recently. So I don't know, I can't just site that off the top of my head. I couldn't speak specifics but just to point out on the Mac, I run a 2013 Mac book because the keyboard works great. Oh snap. And so like, you know, at least on that side, I know that our improvements are working great on older hardware, very visible, so. That's cool. Well, we have about two minutes left and so if there's any other questions that come in, I'll make sure to grab them. But what's the takeaway for people? What do you want them to do? What do you want them to tell us if they're experiencing, about their experience? Cause like I'm a programmer, usually I've learned over the many years that if a customer says, yeah, but can it also? It means that I did the right thing. Yeah. So I think the big thing is go install Visual Studio 2019. It's safe to install on your machine right next to 2017. You can open up your projects and start working on them. And I think if you're encountering any kind of issues or have any kind of feedback, you can always go up into the right hand corner with that little message box and basically send us a message of feedback to our dev community. And we look at those. It's not like a... We look at every single one. Yeah. I know that one of our, as I work in the cloud advocacy group, one of our people put it in and they got like an email. Like every time I do stuff at Microsoft, I get an email from someone. They're like, hey, how is your experience? They don't know who I am. Yeah. I mean, we definitely use like, we use software to actually detect duplicates and things like that. And so if we find that it is a duplicate, then we might kind of resolve it and say, hey, this is a duplicate. But if it's something that's a suggestion or if it's a feature request or something like that or an issue that you're encountering, then that will definitely be looked at by a person on our team. Awesome. Well, thank you so much for your time. It is time now for us to check in with Jeff. Jeff, are you there, buddy? He's run. Oh, we're not checking in with Jeff. Okay, that's okay. He's running. I saw him grab his hat and run over there. I think his beard turned white after that. Pretty excited about that.