(00:09):
[Inaudible],

(00:10):
Welcome back everyone to the Xamarin podcast, keeping you up to date with the latest and greatest in mobile development for Xamarin developers covering the Wordle xamarin.net Azure and more. I met soak up

(00:23):
And I'm James Montana mag Magno Matt, Matt, Matt. I like when you do the intro because you, we, we talk a bunch before the podcast starts and then immediately when we start, you kind of go into this presenter mode and they're like, I'm, you know, and you kind of get into it and your, your, your entire voice changes 100%. I don't know if you realize that at all.

(00:40):
You should hear my morning radio, DJ voice James now presenting, Matt soak up on a drive time radio 92.1 K X F M that's pretty much, that's pretty much what it is. I mean, I appreciate it. I'm not, I'm not bagging on it at all. I definitely appreciate it. And you know, it's a beautiful sunshiny rainy day right here in Seattle. So perfect. Always ranting. It's rained every day for like the last 60 days. So we'll know. We had two, two sunny days in a row and that's been it since the new year.

(01:11):
Yeah, it's been pretty not great. And yeah, it continues to not be great today, but you know, it doesn't matter cause we're here. We have so much news, so much ridiculousness. I figured we'd just hop right into it. Matt hyphen about that.

(01:23):
We got to get going. We have to get going. So James, I haven't seen you in like a month and I know you've been busy so why don't you fill me in on what's been, what's new? What is Microsoft?

(01:32):
It has been a it's been a, it's been a jam packed January that is for sure in January the month that never, that we never thought would end. Finally ended. And then we kicked off February with some crazy huge events around dual screen devices, the service Neo and serve as duo and windows 10 ax and everything sort of happened. On the 11th. This was this big day. There's this Microsoft three 65 developer day and Microsoft three 65, if you're not really aware of what this is, is you can sort of think of it as Microsoft three 65 is two parts. There's a consumer part and then there is a developer part and the consumer part or all of the things that consumers would buy. So they buy devices that buy identity, they buy office three 65, they bought, you know, Xbox stuff, all that stuff.

(02:24):
And then the developer part of is all the things that developers can build for those products. So that includes windows and office and the graph and now it includes the surface duo device and the Android bits and pieces for that and windows 10 acts, all this stuff. Also part of Microsoft three 65 or the other developer services such as, you know, visual studio, Azure, things that maybe you're using from Microsoft that aren't necessarily for Microsoft's shipping services. So obviously Xamarin is part of that because you know, you're using visual studio and.net and the ecosystem. So if you've ever heard Microsoft three 65, you might think office three 65 not to be confused there. And so there's that. So there's, that's sort of that framing there. Does that sound correct, Matt? You might even know more than I do. No, I think you hit it right on the bullseye and I learned something so I did not know all about that in a typical Microsoft fashion.

(03:22):
We have a ton of three 60 fives out there. So, perfect. No, you hit it right on ahead. Gotcha. And, and yeah, part of this event, which was great was was that they were launching developer initiatives around the windows 10 X dual screen devices and serve as a duo. And Xamarin had a big part of that. This is a fun event. I was there, I wasn't in the keynote, but I was behind the scenes of the keynote, rest assured on the Xamarin bits and an amazing team that was pulling stuff together. John Dick, Shane Javier David myself, I'll, I'll work on this together. I would just sort of, I didn't, I didn't do any of the hard, the hard work that the entire team besides me. He made it all happen. I was just orchestrating on the Redmond side of things.

(04:16):
And yeah, we had a great demo. Xamarin was all throughout the entire keynote. Kevin Gallo showed off this beautiful app that we built called Xamarin TV. They, I mean they did a deep dive into Xamarin cross-platform development for both a windows 10 X dual screen devices and the surface duo. And with that came the announcement of our brand new xamarinforms dual screen SDK, which also released on the 11th, the same day, which was very exciting, has a bunch of new helper API APIs and a new two pane view. The two pane view does all the hard work. It manages screens, it avoids the hinge, it reacts a rotation. You just say where it needs to go were built into the documentation is very exciting. And there's a great blog post that David put out about Xamarin coming to the surface, Neo and duo.

(05:10):
And the app was shown across, you know, a windows 10 desktop windows 10 X on, on service Neo emulator and on the service duo and got to show visual studio and the, the emulators and video playback and all this stuff to which is very exciting. And there's been a bunch of obviously excitement from the community on Twitter and on the following the events. And yeah, it was, it was a blast. And I even had a deep dive session when you go to the virtual event page. I think it'll be on YouTube too, is there is a building dual screen experiences with Xamarin session as 19 minutes long. I did that as well. So you can go and get a deeper dive information and on it too. So it was really exciting because it was this,

(05:58):
I mean we have a lot of non Xamarin events, right? Build and ignite and.net conference. Xamarin is a part of those, but sort of, it was great to work together with these teams to sort of see one big happy family on these brand new devices coming together. So I thought that was quite excellent. Yeah, it was amazing. First stop. It was big congratulations to the team to get everything out there and ready for a huge show and just to have it ready. And there's a lot of pressure and I'm sure all our listeners know when you have a big deadline to have it all, they get a project done. It's, it can be a lot. And to have the team deliver like that is, is awesome. And especially then to see the Xamarin logo all over the place and just be, yeah, you know, it's, I had nothing to do with it.

(06:44):
In fact, I didn't even know the show was going on that day. I had a meeting with that day, Bart now waiter that day and he's like, did you watch? And like watch what I had no idea what was happening. But yeah, that was, that's totally awesome. And so James, do you think it was on February 11th that we announced, you know, the, the experience for dual screen, do you think the one and a one played any, any factor into it? Like dual screens and he had two ones on each side. Oh wow. I didn't even think of that. Didn't even think of that. It could be, I just thought of it right now. That's what you get when you listen to Matt radio net radio coming in with all the cool insights on data analysis. Yeah, that could be, yeah, I mean who knows. But it was a fun event and they definitely go watch back all of them if you haven't.

(07:31):
So boom. Yeah, we'll link to everything in the show notes for sure. So you definitely check it out. So, and another cool thing with the SDK for the dual screens, I do believe you have to be running forums for dot five the preview release, is that correct James? That is correct. Yep. And of course then four dot. Five preview release is out then. And there's a couple of cool features with that. My favorite one is the embedded bonds. And what's super cool about that is before, if you want it to embed fonts, he always could do that with forums, which you actually had to go into each platform project, add it in. At least in iOS you had it mess with the input P list and everything. Now it's just a assembly attribute. They have to add to the, to the assembly info that CS file in your forms project and then just use it.

(08:25):
You just use it in your label, just use font, family equals whatever the font name is done. That's super cool. I mean it's, it's just one of those changes that makes life easier for the developers out there. And what's even, what I really like about the embedded fonts are the glyphs, fonts, like font, awesome stuff like that to make 'em pretty pictures. So it's just all about that UI and yeah, so that's one of my favorite features that came out of it. Another cool feature is media element and that was featured pretty heavily in the, in the, and the dual screen is Xamarin TV app. Because that was the TV portion of it. And that's something we've been, I'm trying to, I'm not sure how long we've been trying to do, but that's actually kind of brand new to the whole world of Xamarin forum.

(09:17):
So that's, that's another really super cool thing that we just put out and forms for about five. And then Android X, which we've been talking about for a long time. When you're targeting Android 10, that's going to come along for the ride. You get it now by default. And then the last thing, and we are talking about this before the show is it's trigger mania, a ton of different new triggers in a forms for. But for that by there's like a compares state trigger and adaptive trigger device, state trigger, an orientation state trigger, just a ton of ton of different things. So let's just take like the orientation state trigger. So correct me when I'm wrong here James, cause I might get it wrong cause there's so many different ones, but like an orientation straight state, let's say your device is landscape, you change it over to portrait, things are going to, you can have things automatically change on screen based off at that trigger happening.

(10:15):
So you no longer have to change. Be listening to it in the code behind or your view models is just going to set it up in your XAML or set it up through C sharp in a triggers and it just change our properties that way. So it's kind of more declarative programming, so to speak. So, and there's a ton of different triggers that you can use with it. So there's a ton of, Ford F five has a lot of goodness in it mean it's a pretty big release. So those, those are dot numbers. Each one of them is really, they probably should be big numbers in front, but I guess there's no breaking changes on it. So why white bump up the big number. But yeah, a lot of, a lot of cool stuff in there. So on.

(10:55):
Yeah, I'm really excited about the state triggers and more of that. I understand them because I didn't realize there were so many in there. The more I started to think of how it will be easier to do responsive design in my mind because when you are rotating from landscape to portrait, you want to change your grids or you want to change how many columns you know, are visible and let's say a collection view. And right now I do this in my code. I, I have my collection view listening to a dynamic resource which is an integer. And whenever I rotate the device, I have a listener and when I rotate it, then I set that value. But now I can just have an orientation state trigger and say, Hey, when it's in landscape show one and when it's in, you know, a landscape show two or when it's on a specific device show five, right?

(11:50):
It's kind of kind of really nice. And it's gonna I know a lot of this kind of comes from the, the dub pav, WPF UWP world and there's more of these different adaptive sort of triggers, but it's quite nice. I think it's super, super good to see. Just more customization to help developers be more responsive, especially with the dual screen devices and that'll be nice. And yeah, I, I agree with you on the embedded fonts. Super cool media element, audio and video, really, really nice. And, and that, that one's, that one's been there for awhile, so that's exciting. So get released, go, go check it out. And while you're checking out previews, how about visual studio 16. Dot. Five preview to this is packed full of goodies for anyone developing on windows. This was the first preview with Xamarin hot restart, which allows you to deploy directly to an iOS device.

(12:43):
It'll package up a package and allow you to restart your application. Having to do a full compilation. It's super cool. Also in here, surprise for Android developers building Android XML user interfaces, they have apply changes. It's sort of the XAML hot reload for Android developers. This came from the Android Android studio world, but this allows you to apply resource changes while you're debugging your application. So it does like a quick diff and re-exports the DLL and does a bunch of magic. So that's cool. Also optimizations around the example document outlines. You can get a nice visual outline there. And then also faster Android startup. With the new custom profile startup tracing, which is super nice startup tracing was a feature we talked a lot about previously, which was a predefined profile for both Android and Xamarin forms that sort of ahead of time compiled the bits needed to start your app, but now you can run a few command lines and create a custom profile.

(13:50):
So that helps package up your application with this custom profile to finally tune that startup performance. And this is a really great feature. So definitely check out that one. If you're developing over on windows and saw that preview, you can just sell your previous side-by-side. Don't forget that they both work. Yeah, that startup tracing is amazing. And now they can really get down and turn the knobs and this can be even better. But yeah, definitely check that out. That's so, so cool. And in lockstep, if there's a visual studio update, there's going to be a visual studio for Mac update. Well a preview update in this case and I'm eight, that five preview to out on the streets and a lot of the changes are the, are the same that happened in vs 2019 such as the startup tracing is in there. The XAML document outline is in there, but there's two pretty cool ones that aren't in the ones on visual studio 2019 that are in the Mac version. And the

(14:51):
First one is you get to pick which storyboard designer you want loading by Depot. So if you're still doing storyboard, designing in traditional Xamarin dot iOS and usually you can just load it up with within the Xamarin or visual studio, Mac designer. A lot of times though, you switch over, at least the, I, I do switch over to X code now. You can just say, all right, I always want to pump X code open. I always want to edit an excode. So this will just a nice little improvement in your workflow and sort of just having to right click and go into X code that way. And then the other one, which is super duper cool and I, when I saw, I was like, Oh I can't believe this is actually happening is multi target hot reload. Yeah. For, yeah. For different devices. So now you can actually see your changes to your XAML files happen both in Android, the Android emulator in the iOS simulator at at the same time. James. Right. That's, that's super duper cool. I mean you can now, now you're, you know, you're playing around on both devices cause a lot of times there's gonna be tweaks that you have to make those for Android or tweaks he does have to make for iOS or to get that precise look. And I can see it both at the same time and not have to mess around on each individually. So that's a big time saver,

(16:11):
I think. So it's one of those features that you may not use all the time, but you'll be happy that it exists when you do need to do that. So I can definitely see myself using that in a demos and a in different things. I've used the, I have used the multi debugging before when I present like signal and I just want to launch and make changes and then redeploy to both the devices. I don't have to toggle back and forth and start and stop. So I set up a custom profile to, to do both and it takes five seconds to set up. So definitely check that out. That is for sure. Oh boy. We've got a bunch of other stuff going on. We had some great blogs in and around triggers that we'll be talking about today. And the first one it was, it's trigger mania to be honest with you.

(16:55):
There's just the original state manager, the visual state manager everywhere. The first one was from our good friend Gerald. It was on the Xamarin forms team and he he wrote a bunch of blogs and said, you should be writing more blogs for our blog. Gerald, stop, you know, and said, these are great blogs. Put them on our blog. And like, I love your blog but, but yeah, you know, I know you've got a bunch of unique things, so how about you come write some great blogs and share that content. And he wrote a great one on a feature that's called it's the visual estate manager with using a new property called target name. So this is something that's in, in the world. It's visual state manager has been around for a while and this one is also in four dot five pre-release.

(17:36):
So this is another one that's in that prerelease, but it was in the first pre-release. So pre three has a new new new stuff. This is even in the first ones. If you had upgraded and tried it at all, it's there. So when you have the visual States such as you know and invalid and whatever, you'd have these States, you would normally just set a, a, a property on them. But now what you can do is you can assign multiple setters for multiple controls via the name of their control. So previously you would assign this on like on the label itself. So then you'd have to duplicate this code everywhere because each label or each button would have to have these visual state groups. It's like super tedious cause you're just copying and pasting code around. But now you can say is, Hey, I have a bunch of controls inside of this layout.

(18:33):
Let's say a StackLayout. You can just have a visual state manager with a state of invalid or normal. And when you set it, you can say, set the property for this specific control. So here I can say target name, like label, welcome and button welcome or whatever. And then I could apply this specific property that I want. So I would, I would, I would define the name of it. So I'd be like labeled.tech scholar. And button.tech scholar and it would figure out how to do that. So it's, it's really nice that you can remove a bunch of duplicate code in your application when you already have state. So you can think of, I'm just gonna set, here's one big state for the page and then I'm going to apply all these different property centers and things like that. So just really minimizes the code. So that's a good one.

(19:20):
Yeah. I, I'll be honest, I kind of stayed away from the visual state pen enter cause it was just so much typing. It was a lot. Now this really minimizes it. You can do a lot of it's visual state manager is super duper cool and just being able to minimize that typing and be able to target a bunch of different child controls within like a stack layout is a

(19:40):
Totally worth it. Yeah. Yeah. I agree.

(19:44):
So we talked about, I think last, well we've been talking about Android app bundles forever. Four or five months in a row. And the Android app bundles really lets you shrink your deliverable app to, to the customers. Like, so you can include localization languages just for people like say in Germany or Italy and a lot of people with maybe everybody should be using dev ops too.

(20:12):
Check your coat in and run a bunch of tests and, and whatnot. You can now easily

(20:18):
Do Android app bundles within both app center and Android or Azure dev ops, which is great cause I believe you could do it in an app center before. Now it's even easier. It's just a

(20:33):
Flip of a switch.

(20:35):
And what's even better is that you can actually go and download that app onto as well from right from app center. And then you can do some sideloading if you want. And there's a couple more steps that you'd have to do in dev, but it's pretty much the same thing as you would do if you were building a regular APK file is that you need the key store, but you're in, you're going to build it the same way. But when you, you're just adding a couple build arguments to the when you're actually building, building the file and it's yeah, at bundles, James, what he say everybody should be using it from here on out. Pretty much. Pretty. Yeah. Yeah. So it's, it's super awesome that they're in our two dev ops offerings. So, and it's super mean. It couldn't be easier to add in. So why not? It's true. I 

(21:24):
I did write that blog a while ago and I was like, I'm ready. Are they happy? And finally went out. I was like, well, this isn't a super important blog post, so I wanted to go out at some point and we finally got it. So that was good. All right, last trigger, last trigger talk, last visual state manager talk because we got one more here that I think is a nice practical use. So we've talked about all the things that it supports, but what can you do with the thing and that's always a nice topic for a specific blog. Like what's a real world? Yeah, sure. I see the samples and I'm changing a background color and I'm changing the text color ever. Come on. Like what's the real world use case over there is our good friend Ben over on our mobile customer advisory team wrote this great little blog post about how to update the tab icons on tabs.

(22:09):
Let's say you're using Shaller using a tab page two selected or unselected state using fonts. So I thought this was super Nieto. And with state triggers. So what he does here is he's able to apply sort of style triggers. So what he says is when the tab is checked, show a specific font that is in checked is actually selected. So that's kind of a cool trick in there and there, but it's a, when it's checked in quotes here, show an icon that's like filled completely. So it shows it's selected, but if it's false, use a font that is sort of not filled. So it's like an unselected state. So a lot of like font awesome, for example, has a regular, and then it has a solid of the same icon. So it's the same exact glyphosate, same exact font you know, glyphs that you would use, but it's either filled or not filled.

(23:12):
And, and I've, I've wrote about how to do this with renders and a bunch of other stuff in the past and it's quite a lot of code to, or to kind of trick the system into doing this. But this is great cause it's built right into the box. I would have never thought of this. And that's really, really, really nice to see. I do hope that Xamarin forms just puts it in of having a selected icon and unselected icon or just a generic icon, you know, as a fallback. That would be the ideal scenario. But you could imagine using just this sort of style trigger

(23:44):
Three or for

(23:46):
Just about anything. So it's super duper cool. So definitely give that blog a look because I'm going to go update my handsome informs application with this. So bam. Nice. Yeah, I was reading through this. The bod is like, no way. That's, it's obvious in hindsight, but you never think of it beforehand. And these practical blogs are the, are the greatest, greatest ones there. And I don't remember if he was using the embedded fonts or not from forms for that five but you totally could. Yeah, totally should do it. Yep. And speaking of embedded fonts, this next one has absolutely nothing to do with embedded files, but if you submitted a app to the iOS store lately and you're using UI web view, you've probably got a main note from Apple saying you're using something that's going to be deprecated, change it out. And that's because by default Xamarin forms under the hood is you still using UI web view and come April, I think all new apps submitted to the app store are going to get rejected if you're still using UI web view.

(24:53):
And in December of this year, any existing apps are going to get kicked out. If you're still using UI web view, they want to go with, I believe it's WK WK WebView renderer instead. So the team obviously totally on it and they've come up with a solution to fix it. So the solution is forms four dot five preview. And then there's a couple different [inaudible] arguments that you need to pass in on the, over on the iOS project properties. You can set that. Our good friend Gerald wrote a blog post on how to do it. It's really, he goes through what the team actually had to go through to do it, which is they had to work to get it done. They got done. But for us, super easy to switch out, upgrade a Ford F five and it's just, just a command line, add some properties to it and then a one line done and done.

(25:50):
And an Apple, we'll be super happy with our apps going forward. Yeah. And let's make sure people know your app's not going to get removed from the apps or you just won't be able to submit new apps or update your existing app without adding this flag in there. So if you have apps today, they're not going to get removed. Right. right. It's just that, so be aware of that. And you know, this is a, you know, Google makes these changes and Apple makes these changes all the time where you got to update things. And this to me it was actually a good, a good, it's a bad thing and a good thing, right? So the, the good part is that the bad part is that you gotta go do this. Right. But the good part is that that really your app is probably already using the WK stuff cause it's been in Xamarin forms for like so long then that was the default.

(26:35):
So you already have that. And the other good part is that with this starts to come the linker ability of Xamarin forms. So Xamarin forms traditionally is not linked at all away. And if you turn on full linker, you gotta, you know, put a bunch of DLLs in to link skip Xamarin forms. But this sort of starts in the ability to, to, to remove some Xamarin form stuff out of there, which is, which is cool. So this could in theory, longterm, I don't want to speak for the team, but if I'm imagining it, it could really help reduce some of the stuff that's in that's included in your app. When you, when you use xamarinforms have you like never use media element, then you don't need all the media elements stuff. So don't include any of that code then that's how the linker works. So that would be really cool. So we'll see how that goes kind of longterm, but it's pretty exciting. Just you can already get it and you can already

(27:30):
Give it a go. So boom, there we go. There we go. And that's the end of the news. So let's get on to everyone's favorite part of the podcast, especially Matt's favorite part, the podcasts that cloud Azure news, what you got for us this month. All right, so the first one, I don't, it's not exactly news, but it was news to me and it's called the Azure Quickstart center. And so Azure, James, guess how many's Azure services? There are out there right now, 5,284 by thousand 283 fourth is coming next week. Now there's like a hut, there's like 180 different Azure services. And if you're looking to get started it might be just a little bit overwhelming on where to go. So what this quick start center is, it started as a hackday project, which at Microsoft at Rizza or a hack week project, I believe it. So during the summertime at Microsoft we get like a week to work on I guess pet projects, you know, that bring them to fruition.

(28:26):
And what this project did became a full time job for somebody then to bring it out. And it started from a hack week project to a full time job and it's to guide people through picking which Azure service best fits their scenario. So in order to use it, it's called the quick start center. You would go into the Azure portal and then on the top of the portal, there's this search bar, just type in Quickstart center into that global search and it'll come up. And then let's say you wanted to create a, create a database or create a website, it's going to essentially ask you some questions on what you're doing and it will guide you step-by-step on what you should pick. So that's pretty cool. I mean it kind of takes the guesswork out of like, Oh, should I do a VM cause I have a lift and shift or just go right to an Azure functioning cause I'm just doing web API, just do it.

(29:22):
And and even shows you how to manage your costs too. So VMs, they're on constantly 24 hours a day might be a little bit too much if you're just serving a couple of web API APIs that a function should handle cause they're only getting hit, you know, even if they're only getting hit a couple of hundred times a day, you don't need a virtual machine to have spent spun up 24 hours a day. So it's, yeah, I mean it's just super cool and it really is just made to help you out, pick the best solution to your, to your problem. So nice. Yeah, it was news to me. I'm like, Oh, that's, that's super cool. So I'll, I'll put a link to the to the show about that. Donovan Brown hosted an Azure Friday where, where they went over that. So super nice. Nice. And this other one since we're kinda talking about API APIs is the Azure API management tool.

(30:16):
So I guess I'll give a, I want to talk about just a feature of this tool, but to give a background of what API management is, is, let's say you were, I, I always think of like dark sky a. Dot net is like they provide a bunch of weather APIs and some of them are free for use and other ones you have to pay to get to. And so how do you manage all of that? Like, like then there's quotas and then there's throttling and all that other stuff that goes along with it. Well, the API management tool handles that stuff. Or helps you set that up. So that's a quick overview of what what it is. And so they just released this new tool which helps you publish it and create like this website over the top of it where you can actually advertise which API you have and you can get documentation out to developers and let the developers actually test the API APIs right within this portal.

(31:11):
And even better, this portal all compiles down essentially to a static website. And so this website you can host through API management or you can host it yourself if you wanted to add, if you wanted to change it and customize it and make it your own. And it's kinda like this drag and drop a CMS type system. So it's super duper cool. And when I saw I was like wow, this is CMS. But it's kind of sitting, it lets you create like a storefront essentially for your API's. And API management itself was super cool. Now this is just kind of like taking you that one step further. So I just wanted to let everybody know about that. And then in this last one, James makes me super sad, which is why I kind of buried it at the end, but I'm app center, their Ambasz features are now getting retired.

(32:03):
So then not, not making it out of preview, not making it out of preview. Right. And I'm, I believe early may, they'll be gone, gone. So right now you can still use them. So if you have anything built on them, we have time to transition off. But data and authentication, we'll have to transition over to cosmos, DB and B-to-C directly. They were using both of those underneath the hood, but now you're going to have to move to them and use the SDKs directly against cosmos. And B-to-C push is going to stay around for a little bit longer than that. I offhand don't know the retirement date for that, but it's going to stay around a little bit longer. But I'm the best serve to start moving off to that as well. The notification hubs, so yep. The sad day, especially since I was so, so excited about it.

(32:55):
But yeah, it is what it is. So it is, I mean the nice thing is that you were using cosmos and all the BTCC front of the hood, B to C stuff under the hood and not, it was in preview. And you know, I, I the other parts of app centers are still is their focus. So their focus around sort of the dev ops part of it with build and distribute and analyze, crash or printers still are laser focus and, and that's a, they're going to continue to build, build servers around that which is, which is great cause I still use all that, all that stuff in my apps for a very long time. So yep. And those are not going anywhere. Yeah. So all right. Which brings us to the app service of the month, which I should have been Azure API management, but I'm going to talk about something a little bit different here.

(33:44):
And it's, this one is not necessarily a service cause it applies across a bunch of different Azure services on, it's called the Azure manage identities. And so what this is great at is that it removes the you don't have to put any credentials into your apps anymore to access different Azure surfaces. So for example, let's say you're creating a web API and that web API needs to get at like cosmos DB or it needs to get at Azure storage for something. Normally what you'd have to do is have like a web config file or something like that with the credentials to get at those different services. So what Azure managed identities does is as soon as you deploy that up to Azure, essentially what you do is enable it. And then that service, your web app is now in active directory as you can think of it as a person.

(34:41):
And now that web app, since it's a person can now through row base access control, access cosmos or it can access storage as whatever roles you granted. So if you just want to read only, it just has read only if you want it full writing, I can do full writing. So it takes away the need to have any credentials hard-coded anywhere, even in a config file. So super duper cool that you can do it, do it that way. And it really kind of means no real big coding changes for you on the front end when you're writing it. So it's just a way to make your apps more secured and really utilize active directory since whenever you create an Azure subscription, you are really kind of creating an active directory instance cycle so long with it. So, yeah. Yeah. Very cool. Yeah, I love, I love, always love talking about these these new crazy services and I know nothing

(35:38):
About, so I'm quite excited about that. So that's pretty rad. I love it. So definitely take a look at that. And you know, if you need some off, got that. Ady so definitely take a look at that and Oh man, we added a new to Xamarin essentials one dot four. I don't think there's actually a package out by the time, and maybe this is all, there'll be a preview package of it out, but the team added a web authenticator API. This is cool because it mirrors the like windows web authenticator but allows you to our sample at least you can hit any backend. But asp.net core is great for this because they do all the web authentication into basically anything for you. And the idea is stop putting secrets and stuff into your app and put them on your server and log to the server and let the server handle refreshing and tokens and all this stuff.

(36:26):
So you instead of calling Twitter to refresh the token, you call your, you call your backend, which then refreshes the token and returns it to your app or let your backend query the data on Twitter and not your app. You know what I mean? Like get the logic out of your app to do the things because your backend should be the the in between to do that. And and it's a great little API. It's like one line of code to say like authenticate user or something like that. And you and your backend, there's a great asp.net sample. You create an a mobile controller that does all the routing and uses Chrome custom tabs and SF Safari view and the UWP authenticator and really handles it. So if you need to do social auth into your back end that already has some social authors, boom, it puts it together well.

(37:14):
Some great docs on it. We'll probably talk about it next month. I'm a lot when one Oh four is PR should be out I think hopefully by then, so we'll talk about it a lot more next month. We'll have some great docs on it, but I do want to mention that we have some great upcoming events that you should totally be aware of. On the 24th of February is the visual studio for Mac refresh events. My good friend John Galloway has been working to create a rock star event over here of amazing topics of things that you can build in visual studio for Mac. So I'll run it down. There's a keynote with Amanda silver, Scott Hunter and John Galloway to kick off the day at 9:00 AM there's building blazer apps with Dan Roth and Kendra havens. Real time with signal our with Brady Gaster. Asp.Net core on a Mac with Sayed and John serverless with Jeff Holland who doesn't love a little Jeff Holland in their life.

(38:04):
Come on now. Building mobile apps with Maddie leisure and myself, James Montana mag. Now as long as I can get there on time my good friends Abdula is going to give a a unity talk for Mac OS developers. Mckayla is going to be there giving a productivity developing with.net on a Mac. And then Jeff Fritz and of course Jeff Fritz is going to do a virtual attendee party as well. So definitely check it out. We'll have links in the show notes and of course if you want Xamarin stuff, we got something for you. We have our upcoming dotnet come focus on Xamarin event focus.dot net focus.net focus.dot net [inaudible] dot net Oh geez. Pretty exciting about this. This is having on March 23rd, so we'll reiterate it next month on the pod, but as a full day, live stream, Xamarin a goodness event. We had blazer in January, Xamarin in March.

(39:03):
Super excited. The initial agenda came out. I'll run this down really quick. All things Xamarin, Madela J or David or now just going to crush it and do an awesome opening session. Maddie's going to do Xamarin productivity to the max, our good friends Javier and Gerald doing visualize your data collection view cares of you and beyond a myself and all of the lovely individuals in the community and our partners are going to do expect tacular session called spectacular components or Xamarin apps. I'm really excited about this one. It's a great session where I have to do nothing and and everybody could see, I could see why you're excited. I just stand up there. It's gonna be great. This is a good one. David and guy Marin guy is from the, the Android dual screen team. Developing dual screen experience with Xamarin.

(39:52):
Suite D is coming back, developing performance Xamarin apps, picking a back end for your Xamarin apps. I'm real interested in this one from our good friend Matt soak up. I don't know if you've heard of him. I don't give him that one. Get excited. Then we have some great community sessions. Katrina's going to do one on testing your Xamarin app. Bharti a is going to do one called building in a marketing award, winning Xamarin apps. He's won a Google design awards and Google play awards with his Xamarin Xamarin apps. Ronnie Little's a second going reactive with reactive extensions and UI and then Alexander Santos Kosta developing accessible apps and we have two more TBDs I'm locking in a few speakers. If they would email me back speakers, you know who you are. So email me back. Yeah, I'm really excited about it. Check it out in the show notes and I think that's going to do it then.

(40:48):
Anything else from you? I'm excited for these events. I mean V S for Mac. This is almost like a visual studio for windows launch. If everybody that's going to be there. And I love, love the community sessions that are coming up for the focus on Xamarin. The dot, dot, dot, dot. At Samarin. I love it. Yeah. Cool. All right, well you can check us out at Xamarin podcast with Xamarin, podcast.com Xamarin podcast.com. That's a website. You follow us on Twitter? I'm at James Monto Magno at code mill mat. That's you. That's me. That's you use where you can get it. And we have a YouTube. So we have we have emails, we have other things on the internet and you find us just Google us being us if

(41:34):
You're famous, find us out. So thanks everyone for listening. Until next month is VDR Xamarin podcast. Thanks for having me, James. We'll see you next month.

(41:53):
[Inaudible].