Christina Warren

@Doctor Who — it should not! I think I included the wrong URL (since updated). Try Microsoft.com/learn instead!

@shaovoon: Thank you so much for your comment! We're so thankful for our viewers and customers like you! Have a great week!

@Magnificus: thanks for the heads-up! Fixing it now!

@shaovoon: I was out sick and it was unexpexted! Sorry about that — it would be great if I could have a co-host or stand-in and if I know I’ll be out of town I’ll definitely try to do that. It’s harder if I get sick because I choose the stories, write the script, and put together the image/video assets used in editing — so if that isn’t done, it’s hard for someone else to just host. 

 

But we’ll try to keep this as consistent as possible!

@Keith Latto: Fixed! Thanks!!

@RodAtWork: So going forward, Microsoft Learn is going to be the central place for our learning content. The other content will likely remain (I'm not sure if any of it will be migrated to the Learn platform because the setup is different), but Microsoft Learn is the place going forward.

I totally agree that it's overly confusing to figure out where to go for certain things -- especially when there is overlap -- and that's one of the reasons we're trying to make one destination now. I'll reach out to some of the MS Learn teams to see if I can get an answer for what will be happening to the MVA content.

Thanks!

@ratige:Sorry about that -- it's been fixed and here it is too https://myignite.techcommunity.microsoft.com/?WT.mc_id=ch9-yt-chwarren

@mrahmadawais: thanks for being such an amazing member of our community!

@Janisku7: I'm not sure if I'm understanding you correctly, but you can still do the same multicloud DevOps stuff you did before with VSTS with Azure DevOps -- the CI/CD stuff is called Azure Pipelines but it works with any cloud, just like before.

@Chris: I’m sorry about your build server and I hope you’ve been able to recover everything as much as possible. 

The VSTS team posted and postmortem and there’s a preliminary root cause anlaysis out now. I’ll cover it in this week’s episode. 

Again, I know how much downtime sucks and we’ll continue to be as transparent as we can going forward!

@Matt fischer:thanks for the feedback! We covered 15.8 and F# 4.5 — but I’ll make a concentrated effort to make sure I highlight and emphasize the biggest .NET stuff too!

My goal is to cover all the biggest news across Microsoft platforms, but I definitely don’t want to give .NET the short end of the stick.

Thanks again for the feedback and I hope you’ll get a chance to see the .NET Conf next week!

@Tom: Sorry about that. I don’t know any way to speed up YouTube — there might be some extensions — but I put time codes in the description to try to point out where new stories start.