.Net Foundation .Net Community Standups, 25 Apr 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Windows Desktop: .NET Community Standup - April 25th, 2019 - .NET Core for Desktop

Description

Join members from the .NET teams for our community standup covering great community contributions for WinForms, WPF, and UWP.

Suggest an idea for a standup: http://aka.ms/dotnet-standup-suggestion

A

Hello, everyone welcome. My name is Daniel Jacobson I'm, a program manager on visual studio. We have a bunch of folks from Microsoft all across the the teams that are being bringing you Windows platforms, Windows, desktop platforms and I'll go ahead and let them introduce themselves hi.

B

Guys, my name is olya garish and I'm program manager right now, working on bid forms hi.

C

My name is Kevin Larkin I'm, the program manager on the Windows SDK and.

D

This is Gustavo Rubio I'm, a program manager working.

A

On WPS and there you have it so across Visual, Studio, WPF windows forms and your windows SDK. We have them all here. So if you have questions comments, feedback, we're really excited to have a conversation with you today we're going to go ahead and get started in just a moment. We have some community updates, we're excited to share with you.

A

We have a few demos that we'd like to share, and since this is our first desktop focused stand-up, we're also looking for ideas for how we can provide more value to you in the future and our next stand-ups and future streams. So please engage with us in the chat. I'll, be monitoring that closely and I'll I'll be having a conversation with everyone. So let's go ahead. I'm gonna hand it off to olya and I think we have her screen great.

B

So since this is our first stand up related to desktop, I wanted to give a quick heads-up, a quick recap of what has happened in dotnet and desktop world and, as you probably know, they're bringing desktops tag to dotnet core in the next version.

B

3.0 vim forms and WPF would be available for building your desktop apps and it just released our preview for version announcing that in our dotnet blog, you can go and check out what is new in dotnet core 3 preview and as we are bringing it to the net core we're also open source, VIN forms and WP a--.

B

You can find the source code at github.com, dotnet, WinForms and dotnet WPF, where we're bringing all code we are developing in the open s for pin forms that everything related to run time and right now we are bringing parts of system design that are also have some dependencies related to run time for the informs designer.

B

There is a lot of work that has to be done because before our designer was running as a visual studio in dotnet framework process, now, as it started its target in the net core, it has to run out of process and we basically need to go and redesign our designer.

B

It's gonna take us a lot of time, so Binford's designer is not available yet, but their work arounds how you can use the net core apps of informs and WPF, and still we use the framework designer and I can show one of the ways how you can do it you can have.

B

If you have a dotnet framework project, you can create a new donut core 3 project mean forms or WPF, and you can link all files from your old mean for the framework project to your new one. You can do that by adding those lines in the project file, and then you have your donut core project running on dotnet, core 3 and.

A

So so in this world you.

B

Have essentially.

A

Two of the almost same application- one is a done at framework version, yeah, there's a dotnet core version, including the same files, and that's just a can continue to use the designer while we're bringing up the new there.

B

Same every time you make a change in one. The changes are immediately translated to the other because they are sharing same files. But that way you can go to your framework and you can still use the designer you can make changements to the UI, but also benefit from all the features that are available for dotnet core another way you can do it. You can have just two project files, one is targeting the net framework and one is targeting the net core and and what you need either designer experience or the not quarry.

B

You can load your project with one or the other project file. We have a question: will there be F sharp support.

A

Yes, I just replied to that in the chat. How are you using F sharp? Is it for WPF applications? What are you using it for today? We can definitely follow up and figure out exactly what scenarios are trying to accomplish. I believe the team is working on at least achieving parity with what we had in dotnet framework, but I can I can double check.

B

And the preview version is already available, you can go and download it at the dotnet microsoft.com /downloads, dotnet, core, slash, 3.0 and daily builds are also available for those who wants to get the latest changes. So.

A

You mentioned the wind forms designer and the WPF designer are both in progress right. Yes,.

B

A

For those of you who have.

D

A

Uwp development that may be watching this is similar to what we did when we essentially rebuilt the designer from the ground up for you WP applications when you are targeting it was the 1709 version of the SDK, the 16 299 version. If you're looking at the bill numbers.

B

Yeah great so, as I mentioned the open source code and since then we got lots of contributions from community and we want to thank everyone very much for your input and I just wanted to talk briefly about if you want. Unfortunately, I cannot talk about all of them, but one of the PR that created lots of response was Windows. Start, dialog and Constantine Preiser suggested to bring tasks dialog to win forms and WP a--. This dialog is available since windows vista and it's more has more advanced functionality than message box, but it's there's.

B

No official Microsoft implementation of task dialogue in viña forms or WPA, so Constantine created incredible PR described all the problems provided Trisha now lots of code samples provided the prototype and he got I believe like 70 likes ten hearts for 867 commands on this PR. So it took us some time to figure out very exactly. We won this code to live and how we want to reuse it between being forums and WPF. But now we made our decision right and we will work with the author closely to get to accept this be ours.

B

Thank you very much for that. Another great contributor Cubao me. He created ninety. What is I'm bad at math, 100 801. Sorry PR is only to Vita for I. Believe I don't know was he contributing to double yeah.

A

B

Here's those PRS are related to cleanup fixes tests improvement. So thank you very much you for your contribution. Another great they are was done by my head. Dobby I apologize if I'm pronouncing the name wrong, but he updated the entire VIN forms code to remove language keyboards, to use language keyboards instead of BCL types. So he went, he updated the hundred 70 files and thanks for doing incredible amount of work and one more PR I would like to mention, is done by Zack white.

B

He removed resource exposure resource consumption attributes also he had to go through a lot of infirmity six files. Unfortunately, I cannot talk to every contributor who made it in put in our repositories, but thank you very much guys for doing it and if any of you are gonna, be visiting build and my in Seattle here please find us we'll be an expo hall all the time or reach out we're Twitter. We would love to meet.

B

You too, thank you in person to introduce you to the team right and moving on now, I'd like to talk about a few new features that win forums have been working and just released for dotnet, core 3 version, and the first one is. We are bringing chart in control back to the net core, so I can show what it is for bean firms. Developers they're probably know give me one. Second I will create a new framework project, so you can see them.

B

The designer sense designer is not available yet in the.net Court, but here in the tool box. If we search for chart here is a chart control- and this is what we initially did not bring to dotnet core. The reasoning was that this functionality was not owned by VIN firms team. It was not in our source code, it was in a completely different place.

B

It was the property of different team, and once we ported everything related to informs, it was not included there, but we heard feedback from the community that some folks are blocked by that they cannot retarget their applications from framework to core just because they have dependency on chart control and chart control is not available at 4-3, so we ported this code to the net core and now it's available as a nougat package.

B

If you want to use it in your core applications, you can simply add system that windows, dot bean forms, data visualization to your project and you can use chart controls, as you were, using it in that new framework. They also open sources code and it lists in a separate repo can find it that github.com dotnet slash vin harms data visualization.

B

So here is all source code for you and the reason we brought it primarily to unblock people who want to port their existing doesn't frameworks that are using chart controls when we're thinking about data visualization in modern word, we usually think like big data everything cloud uses, you usually want to benefit from all those assets as well and for a cloud solution. We already have a great product called power bi that provides amazing functionality on data visualization. So if we're talking about more advanced scenarios, then chart control have already it's already available in power.

B

Bi you're very welcome to check out that, and that's why we're not planning on invent in this area like the functionality is. The control is very mature. It's been around for a long time, I believe it's well tested and we would not discover any new major issues, and that is why we ported this code, but we are not prioritized in this area for a new development right now. The repository is basically read-only. If you want to add some functionality or very welcome to fork it and contribute in add something new.

B

For now we will not be accepting feature, PRS, etc, but please give us feedback, and if we see that it's very important for you or there's need, we might change our decisions in future. So if you want to learn what chart control is, there is a great sample on the windows, vin forums. There's data visualization repository sample.

B

You can get this guy and I'll just show you what it has. It has every chart that is available by this control and it also has very interactive UI, where you can learn how to build charts. What kind of charts exactly you would need for your application if we get let's, let's get something together, for example, this guy you can make some adjustments and see how it will look like, and once you found what you like, you can just get the source code in C, sharp or a visual basic and insert it in your application.

B

A

This entire application is running against the dotnet core runtime correct right.

B

A

You know how much effort was involved in actually porting this from framework to core it.

B

Was done by close third month, our team member, who used to be MVP and contributor and I believe who didn't take him too much time? To put it all,.

A

B

Right so the next topic I would like to talk about is a high DPI stadium. Recently we introduced set high DPI mode and high DPI setting high DPI enum. What is high DPI mode? So, as you probably know in modern world, we have monitors with different resolution and there are many scenarios when you run same application on different resolution monitors or you even drag the application.

B

While it's running from one monitor to another, to get your controls rendered properly, you can set various high DPI modes and if we go to high DPI mode in on here, all available values so depay in the where it's this property will work for every monitor and it's simply scales. You were controls the picture as a bitmap. Of course it results too blurry picture if you're working on monitors was a higher than 100% resolution, but the good thing about mode. Is there no breaking changes? It just works everywhere.

B

Then we have a system where that would work for many applications, but not all of them and in this mode your controls would be rendered properly on your main monitor.

B

But if you have another monitor with a different resolution, everything will be scaled as a bitmap to on other monitors, so on not primary monitor picture might be blurry, and then we have a permit or and per monitor v2, where premonitory 2 is a final, our like destination, where we want to be where every control renders, according to the monitor it is displayed at every time we drag, who forms from one monitor to another.

B

We render in this happenin and the controls are shown at the best resolution that monitor support, unfortunately, to be able to support that mode.

B

Many controls have to get some work done and not even all uniforms controls already yet support this mode, and there is another. So eventually we want to be at para, monitor be to per monitor it's just like a half step to per monitor v2, and if your application can support it, that's great, but sometimes you have to do extra work to enable it. We are working on the VIN firm side.

B

We are working to provide the support of pair, monitor b2 for our controls and it's ongoing process, and we recently added another one dpi and a very GDI scale which acts like dpi and aware, but you can benefit from your GD a graphic. The quality is much better and this one I would like to show you on this example. So first we would run the application with a dpi and aware mode. This application is a very simple clock.

B

It'll see it in a second and I. Don't know how well you can see it on this seconds, but if you take a closer look, those lines they're kind of like have big pixels yeah.

A

You can see it's kind of worried. Okay,.

B

Great and now, let's just update and set dpi in a very GG, I scaled mode instead of dpi in the where which is the same it doesn't, it would work everywhere, but yep. If you take a closer look, all those lines now are smooth and nice jacket.

D

B

Okay, so this features we just recently added and before I, give it back to Danielle. I would like to talk about porting your applications. If you have a dotnet framework application and you're interested about ported to the net core, we have a blog that is available on the net block. It's called how to pour desktop applications to dotnet core 3. Where you have steps described in the porting process. There is a video, it's pretty long, it's 30 seconds, 30 something minutes. First part Scott hunter talks about the net core.

B

So if you don't know about it, that's a great video to check out to see the value of the dotnet core compared to that in the framework and the second part, I am porting application that has a WinForms and library and putting them both to the net core from the infirmary, so check it out, and if you got stuck, if you have any questions, please reach us out at this email. We are happy to help.

B

You you're happy to learn to hear your feedback to learn from your experience, so we can do better and so and thank you so much awesome.

A

So I hope you can all see my screen now. If you've been playing and paying close attention to the WPF repository on github, you may have noticed it's taken us a little bit of time to port more of our source code to the repository to be open source. Fortunately, we have Gustavo the PM on the WPF team, to explain some of the incredible and pretty challenging work that the team has been doing to get us to this state and to prepare us for the future so that we are essentially more agile.

A

We can start bringing more and more code and kind of accelerate our investments. So I, like Gustavo, explained sure.

D

Yeah so back in in December there was a brother announcement that BB F would be open source along with WinForms, and at that time there were some binaries that were open, source, I, believe system about Sam, oh and since then like we went a bit quiet on the repo, but believe me, like. The team was working super hard and since in December we did receive some feedback on from the MVP summit.

D

um Okay, could you guys be more more transparent about what what's been happening, so we really want to open up and start sharing more updates to the community. So as a whole, the team has been working on one of one of the major items that took so much time was. Some boarding to the arcade has decayed, which is a new build system for dotnet core, and the team was dealing with a bunch of complexities through onboard two to the to decay. Just cuz.

D

It was one of the first teams to on board and build native C++ projects and and that that didn't play well with with the existing set up. So the team had to go and and and tweak some of the the the functionality there. You can read more on the on the update and and learn some of the intricacies WPF has been around for a while. So there's also a lot of the code has has tricks there and there's a lot of reference between the different binary.

D

So, for example, presentation UI is used to build presentation framework. So there's a lot of cycles there and- and you can, you can learn about the details there dead. Last month the team also ported a couple of binaries. They ported presentation build tasks. So that's a big big big amount of work and then also the Microsoft that as the key that Windows desktop.

D

So that's that's been keeping the penis busy as a sample for sure and.

A

Don't worry if you didn't get a chance to read all of that, you can find the links that we're sharing at akms slash net core desktop so or you can just navigate to this issue in the WPF repository. Oh yeah, thanks Gustavo, so so going forwards. What do you think some of the expectations could be for contributors or participants in that repository, yeah.

D

So, at a macro level right now we're trying to work all the functionality from dotnet framework to the to dotnet core and as such we were trying to reach first functional and performance priority right. So the contributions that we're looking at is any any work that will help us reach that further.

D

So any bugs that that you find that might help us accelerate the effort right now and then we're almost close to to automating some of our our tests so that we can ballet pool because it's still probably a month out, but once that happens then we'll be taking a lot more Borah question coming as well. Awesome.

A

I'm really looking forward to kind of the WPF and win forms being open source world where it's just kind of the norm. Instead of this kind of unusual dream, almost it's. It's really an exciting time for for desktop development, yeah for sure cool. So just calling out some some things that have been going on in the community. Some contributions, some blog posts. One thing that was recently published by or Novotny who's, pretty active in the community is a blog post about telemetry and desktop apps I.

A

Think when you, when you think about WPF and Windows forms, you don't think about some of the most modern development practices such as DevOps and telemetry, and things like that and with this hold on that core effort, we're breathing new life into these platforms and we are making them more modern and so you'll probably see a lot more from from us and from the community about modern development development practices, including DevOps, and then automated builds and Azure pipelines, and so here's a really neat blog post about getting telemetry and desktop apps using application insights.

A

For now we're also working with the App Center team. Microsoft to make that kind of a better supported story for desktop development scenarios, but if you want to go ahead and get started and start getting analytics in your desktop applications today, this is a really great place to get started.

A

One of the other blog posts that came out recently was was pretty interesting. It's using dependency injection and service provider with the BPF, so these kind of more typical asp.net core scenarios for managing your desktop configuration settings and persisting them across your application using dependency injection. So again, this is a really neat blog post. If you're wondering how do you manage all of those application configuration settings and persist them throughout your entire app? So this is another cool and from Marco Minerva last month, I believe some tweets. We, this is an example of many tweets.

A

We've been seeing actually from Yann Karger who works on mops, he's already updated all of his open source libraries to work on dotnet core and me. While this is incredible, work he's one of many and we've I think been overwhelmed by the positive reception that we've been seeing with desktop development support on deck or you look at prism.

A

You look at like some of the component vendors that are already working on getting previews out for dotnet core is really been incredible and I think by the time we do GA later this year, you'll probably have a pretty comprehensive and robust ecosystem already ready for those dynacord desktop applications. So you can also see the first reply.

A

It's me also, like lots of people, are doing the work and and I think part of it is because it's really not that hard we've been working through many different scenarios, and there are a couple corner cases and education where you might get into a little bit of trouble, but for a lot of different applications and libraries moving from framer to core is more of an update than it is a full migration. So thinking about it in that context, is, is really kind of exciting again calling out some of the top contributors.

A

I know olia kind of already started mentioning this. We wanted to thank Andre, who is not a Microsoft employee. These first couple are but they're doing their jobs and they're doing a great job as well you being active in the WPF repositories and then looking at wind forms again we have Hugh doing that crazy, a crazy amount of work to clean up some of the code base, which is really appreciate it. So thank you so much if you do make interesting contributions, file, interesting issues, submit pull requests.

A

Well, we'll definitely keep an eye out to call these out in future stand-ups, where we're really excited to work more and more with the community as we work on these projects, and then this is just probably redundancy at this point. But I think this is just a demonstration of my excitement that wind forms and WPF are and github like wow. That's crazy I mean if you think, if you go back ten years ago, it's unheard of so, if you haven't just looked at the repositories, go ahead and take a look.

A

It's really really cool only already shared this, but if you're interested in porting to DES are to dotnet, where this goes into some of the reasons you might want to do that as well as some of the examples- and we can do a some demos as well, but we'll get to that in just a moment- there's another tool about porting. So this is kind of the pre-migration step.

A

If you, if you will that, helps you analyze your existing dotnet framework, applications and assemblies just to give you kind of an early read on compatibility, so this produces a report, an Excel report that analyzes all your binaries and it tells you exactly how compatible you are with the.net core platform you're targeting. So this is essentially just before you do any migration. How likely is it that it's going to work and if you want I, can also show you a cool little trick?

A

If you don't want to do any work at all, but you want to see an application trying to work on net core, let's go ahead and do that demo.

A

So I had this dotnet framework application I'm going to never get all the way the bin folder, and so this is a WinForms application that just does some directory enumeration and essentially creates a pie chart. So let me navigate to a folder and notice this folder picker. This is this will be interesting later. So, if I go all the way to my repos folder I can scroll down.

A

It takes a little bit of time that works, repos and I'll go to levels deep and I'll run this, and so you can see that took about a second and it creates a list of all these directories and how much space are taking up relative to the full list. Now, if I want to do this same exact application running against a dotnet core without even touching the code like I'm, not even recompiling, I can actually do that.

A

So, if I open up my command, prompt I can use the dotnet CLI and I can use this little trick called dotnet, exec and then I just pass in the executable, and so now the same exact application is running on dotnet core. So if you remember, when I click browse here, I get this old kind of classic folder picker dialog. If I click browse here, I get the typical explorer dialog same assembly, different runtimes, so this is pretty cool. This is again another trick and like the early porting step.

A

So again, if you don't want to do any work at all, you just want to see. Does your application work when running against Nick, or this is a good way to test that? Don't do this for production scenarios? This is just like hey. Is this gonna work? How much effort am I going to need to do to actually get this working so now I can use the Explorer.

A

Scenario and I'll do the same thing, and now I will go to levels deep again and one thing you'll notice is, and obviously the performance will vary, but it's a lot faster at doing file enumeration. So some benefits of porting to dotnet, core and I'm gonna put a big asterisks on this, but certain scenarios will have improved runtime performance and, and one good way to think about what scenarios will run faster is to think about the history of dotnet core. It was kind of born primarily as a server workload.

A

So, if you think about anything that has extreme impact on server scenarios such as file I/o database access networking those types of scenarios, you can probably expect some noticeable performance improvements there. That said rendering performance or startup performance. You might not see big differences between dotnet framework and dotnet core in those types of scenarios.

A

So, depending on your application, you may get performance benefits just enduring the the update and in order to do that, dotnet exec one other thing you will have to do is you have to create this runtime config file, I'll open that, so you can see what it looks like, but that is essentially just articulating the runtime properties that you want to run the application against. So you can see I want to run it against the Microsoft Windows desktop app framework, and this is the version of the SDK that I have installed.

A

It's a slightly older version of the preview, but there you have it. So that's one way of just a hey. Is my application. Gonna work on dotnet core one other thing that we recently released. We released an update to Visual Studio 2019. We have 16.1 preview 2 the reason I'm bringing this up is because, from talking to many net desktop developers, one of the biggest pain points or challenges they have is with application distribution.

A

Just deploying your application getting it onto your customers devices we're doing some work in the tools to make that better with the MSI x-pac agem technology, specifically with a feature of that called app installer, and what this enables you to do is more kind of advanced side loaded deployment scenarios such as automatic updates, behind-the-scenes updates things like that. We recently added a new item template which is called the app installer file, and this lets you specify some of those properties. When you launch your application, this will determine. How often do you check for updates?

A

Do you check every time you launch the app? Do you check once a day those types of things it'll? Also, let you figure out and specify where you're deploying your application. So that's when you deploy it to a server the the application running locally knows where to check for updates. One question was: how much faster was it so when running the application on framework it took about a second thousand milliseconds and when running it against tynacorp took about a hundred and twenty milliseconds. So it's quite a bit faster running that same sample, you'll, probably notice.

A

30% to 80% on average for those types of file, enumeration scenarios, but yeah so take a look at 16.1 and look at the windows application packaging project with the app installer file and again this title template lets. You specify more specific information about deploying and bundling your application for distribution now.

A

The next thing I want to talk about is another thing that we recently listed publicly on nougat, and this is the Microsoft Windows SDK contracts, nougat package, one of the things that we've been working really hard to do is kind of blur the lines between some of our older net platforms and our more modern Windows 10 runtime capabilities, and so this is one effort that makes it really easy for you, and existing WPF or windows forms application to reference.

A

Those windows, 10 windows, runtime, api's and so we're gonna have a demo here that Kevin is gonna. Do in just a moment. That'll show you exactly what this enables and- and this was kind of supported in the past, but it was really difficult to do.

A

You'd have to find this kind of esoteric Wynand D file that was installed as part of the SDK and add a direct file reference, and every time you update the SDK, you had to make sure that you were referencing the right one, and this really streamlines the process to be able to do just a nougat package, so I'm gonna hand it off to Kevin to share his screen and we'll see. If we can get this working.

A

Are you able to sure.

C

I'm not sharing the right thing.

B

A

Can see we're also gonna blog about this very soon, so you get super early sneak peek preview of the the blog post draft.

A

There we go cool, excellent, well.

C

Thanks Daniel, as as he mentioned just last night, we flipped the new get packages to be visible, so they're now available we're doing the kind of a slow rollout of this feature, and daniel mentioned to me that we had this opportunity to. You know, bring this to the the crowd. Unfortunately, he caught me, as you can see by the my application in kind of a moment of reflection, and I was trying to figure out what I'm doing with life, but I thought I could show you how Windows api's can help.

C

You figure that out at an answer that question you're, making the Windows desktop development community better, that's what you're doing okay excellent. So what we have here is just a managed app and, as you can see, I have a little bit of code here that that is using the the geolocation API. So, as you can see, they don't work when I uncomment that so let me go and add a reference to our new get package.

C

And as you see, it doesn't show up well, we still are set as pre-release so make sure you check that flag and then we'll show up now. As you see, we have the latest released a 1903 release. We also have the two previous releases 1809 and 1800 Tsar also available to you and those are the different Windows 10 versions.

C

Right, that's correct there, the previous two releases of Windows, and so you can specify exactly the contracts you want for your minimum version by using those contracts, you can also use the latest ones and then you know do kind of a light up to make sure that you're using those api's on the right OS. When you run it awesome, okay, and so it's installed locally. So this will go through pretty quickly, but you just accept the contracts where polling ends.

C

What we call is a glue assembly that that the.net team is provided in order to make this hook up and so you'll notice that I'll have an error. Let me go back to the the form as you'll notice. The windows api is no longer an error, but we have this problem about this one, because this is an async operation. So what we simply need to do is add a sync to that, and that should make the error. Assuming I can click there. We go make the error go away and now I can run my application.

A

And so the expectation here is that this will show your your geolocation latitude and longitude down the application. That's correct if it ever presents itself.

C

There we go that's right and so I can go find out where I am in life by clicking that button and it takes a little bit. But there you go it calculated where, where I was using those API, so those windows, api's I, think.

A

We're seeing can you try moving the window around a little bit? It looks a little off on here. Maybe it's a projection.

C

Projection issue. Sorry, hmm you.

A

Want to take a screenshot and then like copy it and paint and see if that works. Oh.

C

B

C

Me just share my entire desktop. That's probably the problem I see.

A

Ya doing teams screen projection and development in visual studio sometimes causes some little performance. It goes I've discovered just.

B

To summarize, but just it didn't, you can use all the internet guys it's not showing.

A

um That's alright. We can do another demo just.

C

Trust me: it works yeah.

A

So I mean to summarize that, and it's essentially you're a nougat package away from the full power of Windows 10 in your art. That's.

C

Right I mean there are some limitations on the api's or a certain api's that require a package, and those api's would not be available. We have that pretty well documented out on MSDN to give you those api's and that, of course, will be identified in the blog, but you know the the newer api's that you're interested in, like you know, ai and NL, you know those should be available. I'm cool, all right. If.

A

You want to start protecting your screen, then I think that.

C

This doctrine, you see Gustavo's.

A

Face as well, so we have a lot more of exciting announcements coming up for you in just a couple of weeks at Microsoft, build that is I, believe, may 6th May 8th this year, and so we'll have more demos, more more blog posts, more content and things that are coming soon. We, we can't share all of that with you, but we're very excited. We've got some time left and we wanted to open it up to kind of a discussion with the community.

A

So if you do have any questions we'll be here for some some moments to help an answer, we're also looking for ideas on on the stand-ups going forward. So one of the things that we had as an idea and I wanted to just kind of check in with the community, would it be useful for us to do like an interview with someone from the community? That's done the the updating process from dotnet framework to dotnet, core and kind of understand their experience and what they had to work through to get there.

A

Is that an an interesting concept? Let us know what you think. Let us know what questions you have otherwise, we'll just sit here, looking pretty and that's most of what we had for you today.

A

So one time poker says: yes, I think it would be great to have the feedback of a customer also, if you know of someone that has done work to update from framework Sakura or if you yourself has done the work to upgrade from framework to core tweet at us, I'll put our Twitter's in the twitch chat.

B

So what I can do I can show portability analyzer and talk a little bit about it.

A

Yeah sure you want to project it and go ahead and again ask questions if you want so always going to do another demo about the portability analyzer process. That's my screen! There we go.

B

Okay, that is my skin great, so they have a blog post on pretty analyzer that is called I have been forums and WPF applications, radio for dotnet core it's available and cognate blog, and here you can download print ability analyzer. Once you do that, you will get the easy and I'm gonna just run it and show you it's super simple: I'll walk you through the process. First, why do we want to run for the built analyzer? What it does?

B

It looks at your assemblies and it takes all a api's that you're using and compares it to the api's that are included in that nut core and that way, if you are using something that is not supported in the net for 3, you will get prompted. So, let's just.

B

Run this pretty bility analyzer against the itself point to build analyzer. This is how you specify the folder to your binaries. You hit analyze depending on how big your application is. It might take some time, but usually a few seconds and you can open the PERT ability report.

B

Ok, so here we see all assemblies and how compatible they are to donate core 3 and 100% means it's fully compatible. You can go ahead and port it to go right now and I believe ok, I'm, happy. We got something so here for this assembly has a dependency it severely 0.3 percent, but ok- and this one too that's something that is not included in that net course. So to find out what exactly you can go to details, tab and we'll have all the guys or members methods that are not supported in that net core.

B

You can see the full name. You can see the assembly where they're used in your code, it's not supported in dotnet core and unfortunately, we have not populated all recommended changes, because it's like an incredibly large amount of org. We have some there working on it, but right now the recommendation would be to go ahead and see if you can refactor your code, somehow so you're not using those api's or they're for some that we did not bring to court they're already substitutions, more new, modern, more powerful guys that have same functionality.

B

So in case you have not 100% compatibility, you need to first do some refactoring. In your code till you get 100% once you have 100%, you can go ahead and retarget your implication from framework to court and.

A

Only we had a question in the chat about that per monitored, efia DPI awareness, so jm2 mentioned that they were starting a new app with perf, monitor v2, and they had to go back to DPI unaware because dragging between the monitors with different DPI's made label and button controls wander and get the wrong font size right.

B

So pair monitor, v2 is not fully supported, yes, neither by vin forums nor by many other controls. But if you found out issue that would be super helpful. If you could report it and we will work on it and while you can use some other DPI mode to enable workflow for your application, once everything is supported, you can switch back to permanently.

A

Right, thank you. Kevin Gustavo Leah. Anything else had any further questions from folks on the on the stream. Was this helpful was this useful? Do you want to see more desktop community stand-ups going forward? This is kind of an experiment for us based for some success. We had with a twitch full-day stream event going on. Okay.

B

We have another question: will there be supporting 304 system run time interrupt services if we needed access to in those api's tests.

A

You have a more context on that question, which specific api's are you trying to use there.

A

I'm great so we'll look for a little more info on that question and then we can help out and again, if you have any feedback on how this can be even better in the future. Obviously, every time we want to do this, we want to be more useful to you. We really appreciate you taking the time to join us today, and so we hope you got something useful out of it. Let.

B

Us know if there any other topics we have not covered, but you would like to hear about.

A

I'm interested in more done that framework to Dominic or migrations, there's a lot of legacy code. Yes, are you porting some of your code yourself, a off fling, I, hope, I said that right and then test, for example, creating user access tokens for processes?

A

Yes, I believe system run time. Interrupt. Services is supported and done neck Worth Rio.

A

Do you know we can we can follow up to if, if you want to tweet at one of us, the Twitter's are a little above we can. We can get a more definitive answer based off of the scenario specifically interested in.

B

Where's the best photo progress on their purity note if you have in forums and updates in general. Yes,.

A

So the the github repositories is where you'll see the most recent updates to everything that's been going on there, so I would I would subscribe to those or follow those are star the repositories and keep an eye out for. What's going on. Also.

B

Are the blog they're all with every new preview version we post a blog and be all the new functionality that we add all new tricks for migration? We always blog about it on the dotnet blog. So you can follow that as well. And if you have any questions, please send us emails, we're happy to help and.

A

So I think next time for the stand-up may be. What would you either in a month or two months, depending on how the schedule works out, we'll bring in someone who's gone through the process of updating an application from frameworks decor and we'll do more of like an interview, style approach where we'll understand what motivated them to go through the work to do it? What were the challenges they encountered? What benefits do they observe and things like that I think based off of some of the comments.

A

That would be a really helpful experience, for example, a window service creating a process under the logged in user accounts. Do you know I have no idea we'll have to go look into that. Well, have.

B

To look into that I I think you should be able to do.

A

That with donek or three and the probably the the contracts nuga package to get that logged in user account identity information, but we can. We can follow up. I'll, take the action item, cool.

B

A

Great and that tez, if you want to tweet at me, I'll get you in touch with Kevin to follow up if you have Twitter. If not, let me know, I see I'm waiting for done echo or three to hit before looking into migrating stay tuned for more information about kind of scheduling and things like that. A build we're excited to announce a whole bunch of things there, so you should have some more information in just a couple of weeks. Actually, it's coming up really fast and yes, 300 is a big release.

A

It is not just a desktop release. Obviously it supports pretty much any sort of workload, whether it's server web IOT, desktop machine learning, all sorts of stuff, but it is a pretty incredible platform. Currently I'm.

B

Pretty sure and my company won't want to update until designer support is really build that potentially be this year. That's.

A

B

Great point yet I understand so we're planning on releasing the first preview version of the designer in the poll with the general release, octet net cursory, but it will be a preview version. Not all functionality will be there. Yet it's just a lot of work.

B

So what you can do if you're looking into port in the future, you can start and use the approach with two project files or tooling projects, and you can just update dotnet core your runtime apart and still use the designer for another framework or you can wait till the designer is there. It definitely will be. It just will take some time.

A

I'm replying to one of the links, so if you type that into your browser and you go to the are your windows forms and WPF applications ready for dotnet core 3 Oh blog, that's the link to the portability analyzer tool, one other question we had, which version of.net core supports dotnet standard 2.1. I believe that is done at core 3.0.

B

The latest version of core and core standards- it's 2.1, but the general advice is to target for your libraries target to point all unless you, if you want to be compatible with as many applications as possible, yeah.

A

Great, a one-time poker. Let me know if that worked for you on on the links. So again, if you, if you missed any of the links, we have almost all of them at that akms slash net core, desktop link that just brings you to a single web page with all the links we talked about great. So this was a lot of fun for all of us.

A

I think we look forward to the next one of these, where well, we'll do an interview with someone who sported kind of a larger scale of desktop application from framework to core. um If there's any other things you want to see in these stand-ups, definitely let us know tweet at us and we're definitely excited to incorporate your feedback to make this an awesome thing. Great awesome thanks. Everyone have a.

C

A