I am glad it was helpful. This video might shed some more light on the subject: kzfaq.info/get/bejne/r9dgl7acppfaoIE.html

@@IAmTimCorey Thank you very much. I didn't expect such a fast response!

You are welcome.

You are welcome.

Thank you. Not sure if you realize it, but by adding this detail, it adds a keyword search type experience for users when doing searches within the entire channel. You Rock!

@@IAmTimCorey I did not know that.

You are welcome.

Great to hear!

You are welcome.

You are welcome.

Agree with this. Please Tim make a Community Toolkit tutorial. There are none out there.

Great!

You are welcome.

lol I'm glad it was helpful.

Here are my thoughts: kzfaq.info/get/bejne/r9dgl7acppfaoIE.html In genreal, none of these are dead but I'm not a huge fan of UWP.

Stick with WPF, or do some Xamarin Forms if you haven’t already.

Back when Windows Phone/Windows 10 Mobile was a thing, UWP was interesting because of the promise of having an app run on phones, tablets, and desktops. Phones are gone, and Windows 10 runs WPF and WinForms apps on tablets and desktops, so... ¯\_(ツ)_/¯ Look on Dice or some other job site for UWP listings versus WPF or Xamarin: that should also give you an idea.

No, yes and no. Think about it. If you code something in pure UWP, it will run only on Windows 10. (OK, on hologram and Xbox as well, but let's be realistic, what app will run on all three of them :) So I doubt that any self-respecting developer will want to limit his choices like that. What I would suggest is coding a normal desktop application and then convert it to UWP: developer.microsoft.com/en-us/windows/bridges/desktop/ I personally code my apps in C++ and then convert them to UWP, but you can use .NET and WebForms, etc. There are quite a few gotchas (rules) that you need to follow to be able to convert them, but all-in-all, if it succeeds, in the end you will have a working desktop app (that in theory can run on anything from Windows XP and up) and you can use UWP infrastructure to post your converted UWP app in the Windows Store. (And get maybe 2 or 3 extra downloads a month ... 'cause let's face it, Windows Store for now is only good for growing crickets.)

@@gatep5 Indeed, WPF seems to be a tried-and-true solution and the choice go-to for many Windows Desktop developers. However I think one of the biggest attractions towards UWP is its deployment options. The integrated Windows Store deployment functionality I think gives it an edge over WPF- where in my experience- I've used utilities such as Inno Setup to create MSI/EXE files, or the WIndows Desktop Bridge; If you're not deploying your application, then it's just sitting there on your PC. Nevertheless, I do prefer WPF because of its richness, but tech is progressing-- I think its worth-while for any Windows developer to at least be aware of UWP and better still somewhat capable to develop on the platform.

Tune in tomorrow. ;-)

Glad it helped!

Pretty much. UWP is not the way forward.

@@IAmTimCorey But what is the way forward ?

I don't have a book to recommend. The way I would suggest is to go through the wizard and add just one item. Read the code, figure out how it works, then recreate it from scratch. Then do it again with the next item. Learning from code this way will be hugely beneficial to the development of your skills.

Not yet! I have added it to my list

@@IAmTimCorey Okay, looking forward for it, Tim. Thank you!

Look at docs.microsoft.com They have examples there of how to work with UWP applications.

Unfortunately, I probably won't be doing that. UWP is no longer being improved by Microsoft. They are moving away from it. It is still supported, but their efforts are going towards WinUI and MAUI instead.

@@IAmTimCorey Hmm :( btw loved your tutorial

I don't think UWP can do interop.

You are definitely correct. That is hard to get right.

Thank you!

You want one central app to pull the files from the machines of the sub-servers? That sounds like a Worker Service as the main service. Unless it needs a UI, it can just sit in the background and do its thing on a schedule.

Thanks for sharing.

It's a separate exension.. I searched for Caliburn.Micro extension and installed it, now it appears as an option.

I'm glad you figured it out.

No, sorry. That's fairly specific too, so I don't think that will be covered this year.

@@IAmTimCorey NO worries. I finally figured it all out this past spring during mandatory stay at home orders during the pandemic. Here is my final result which has double encryption... no one is getting to this data inside my app :-) : Password-Vault found here in the Microsoft Store by RS Creations: www.microsoft.com/store/apps/9N639H9BNZ9Q . Even the backup file is encrypted.

That is more of what .NET MAUI will do (the successor to Xamarin) next year.

I'm not sure if you are actually asking for a mocking framework (which is used in unit testing to replace dependencies) or if you are thinking of something else. If you are asking about a mocking framework, check out Moq: kzfaq.info/get/bejne/et2SjNuBksvYfY0.html

I didn't need to install an extension but I am not sure. Maybe try just updating Windows and seeing if that is all it takes?

​@@IAmTimCorey For now, I have the latest (supported version) for Windows and cannot upgrade to version 2004 (which I found out that it needs after installing the SDK). However, I can run everything else (including a blank document). So, is there any other alternative tutorial for that. If not, I'd be happy to learn Xamarin for mobile development (any videos that you suggest?). Also, a tutorial on creating a zip archiver would be amazing as no other KZfaqr has done that yet. Thanks for your time :D

on 2022 it's just "Template Studio for UWP" now

That is a question I can't give you a direct answer on. It depends on your team's skill, what you are building, the scope of the project, who will use it, and a LOT more. Sorry.

i tried making desktop program using electron with react and it was a mess. i am in this video to learn native development. java fx would be a great choice if you want cross platform compatibility

Just build apps with .NET MAUI.

It is. You have to install the UWP package when installing Visual Studio though. You can add the package now using the first option under the Tools menu.

dnSpy does work on UWP apps. As for a service to translate your apps, I'm not sure what you mean. If you mean automatically, I'm not sure but even if there is, it won't be perfect. If you mean a paid service, yes, there are services out there to localize your applications.

@@IAmTimCorey it does? Are you sure? Can you name UWP app that dnSpy works on?

Get some student kid on Fiverr a little bit of money to localize it. Program resources are hard to automatically translate because of the requirement to need the shortest possible translation and the little context in which the words appear. Manual translators need screenshots or you get the same ackward translation as using Bing translate.

I understand the basic thought, but this isn't as clear cut as you would hope. Not everyone follows the Microsoft support. For instance, banks and hospitals are notorious for being very far behind the curve. The government is also usually well behind the curve. The slowness to adopt in these areas usually is because of security (a new OS needs to be thoroughly vetted for safety reasons) and compatibility (all of the apps also need to be able to run on the new OS and need to be vetted all over again). So if you are building apps that target any of those markets, you are less likely to be able to use UWP at all. Home users are a mixed bag. While they are more likely to have Windows 10 (because they bought a PC in the past few years), they are less likely to know if the updates stop working (virus, poor configuration, etc.) Small businesses tend to try to make their money last longer, so they don't upgrade as often (and they use older apps that might not support the newest OS). At the end of the day, it all depends on your market. You can't just assume that even the general numbers apply to your audience. And those general numbers are still not really in favor of Windows 10. As of January, 2020, Windows 10 had a 57% market share, but Windows 7 had a 25% market share: www.netmarketshare.com/operating-system-market-share.aspx?options=%7B%22filter%22%3A%7B%22%24and%22%3A%5B%7B%22deviceType%22%3A%7B%22%24in%22%3A%5B%22Desktop%2Flaptop%22%5D%7D%7D%5D%7D%2C%22dateLabel%22%3A%22Custom%22%2C%22attributes%22%3A%22share%22%2C%22group%22%3A%22platformVersion%22%2C%22sort%22%3A%7B%22share%22%3A-1%7D%2C%22id%22%3A%22platformsDesktopVersions%22%2C%22dateInterval%22%3A%22Monthly%22%2C%22dateStart%22%3A%222020-01%22%2C%22dateEnd%22%3A%222020-01%22%2C%22segments%22%3A%22-1000%22%7D

We have gone past windows support dates on many occasions because of applications that our organization runs that cannot upgrade. What types of apps? Well apps with support contracts that use earlier versions of sql that haven't been upgraded, bridge and middle ware apps that may use specific supported drivers for high end scanners and expensive mail sorters etc. For a document work flow application we literally had to hold off then finally jump 6-7 versions and upgrade from sql 2005 then 2012 then upgrade 2 more versions (64 bit win 8 then win 10) and finally sql 2016, but only after we upgraded from Oracle 10g to 12c and I think Mulesoft was about the only thing that didn't get upgraded. These integrated apps are used heavily by our call center, licensing, accounting, enforcement and legal and would shut down our call center and other sectors if these apps couldn't communicate and work flow items. The Win XP to Win 7 upgrade was a nightmare, windows 7 will be missed, but the upgrade to 10 was not as bad. We skipped 8 since some of the LTS contracts wouldn't support the Client apps on Win 8 without additional costly fees. On the bright side the OS and server upgrades are getting smoother since and not as costly which benefits the taxpayers (state government), but we still wince when Microsoft, Oracle, and various vendors decide to force upgrades. The lawmakers at the budget requests always ask why and didn't we just upgrade software. If they only knew.

We appreciate the suggestion and I have added it to Tim's list.

Unfortunately, UWP has been deprecated, so I won’t be creating new material for it.

Try doing a build first. Sometimes you need to bring in NuGet packages that have not been downloaded yet. Otherwise, compare what you did with what I did. You might be missing something minor.

@@IAmTimCorey OK, thanks.

Yeah, there isn't anything horrible in UWP, it is more that there are small issues that act like sand in your shoe when developing.

It all depends on the audience. There are a lot of people out there with older laptops/desktops. Even people on Windows 10 don't always have the latest updates. What Microsoft supports doesn't really affect what people use.

ViewModels are UI. They are at the same "layer" level as your Views. If you put them in a class library, that class library becomes a UI library, not a core library.

You probably didn't install the UWP package when you installed Visual Studio. In the Tools menu, select "Get Tools and Features". That will let you configure what is installed in Visual Studio. Select the Universal Windows Platform option and install it.

@@IAmTimCorey I selected the option Universal Windows platform . Before installing .but didn't work.

My guess is that you need an update to either Visual Studio or Windows. Then the plug-in should update itself with the latest options.

WinUI 3 is not very high on my list of things to cover, specifically because Microsoft doesn't put a lot of effort into it and because it is so limited in where it can be deployed. Even Microsoft recommends WinForms and WPF over WinUI 3. But as to your questions, building an API is almost always a good idea. It allows for more secure communication to the database and it allows you to have multiple UIs that work off of the same logic. This allows you to build a WinUI 3 project today and then easily transition to an Uno project tomorrow so that you can have your app deployed everywhere.

Personally, I prefer WPF because of the freedom, but both will do the job.

Not sure that you mean by data visualization. There is support for graphs, charts, datagrids, and more.

@@IAmTimCorey Yes, I meant all of that. I didn't find any charts, datagrids or graphs "out of the box" and the only options that I've found is by third-party packages. There is something that I'm missing? :(

Charts and graphs come from third parties. Microsoft provides the platform, you get the additional tools and UI you need from third parties (which can be free - for example, Syncfusion is free if you are on a team of 5 or less and your company/you makes less than $1 million per year).

Thanks.

And they now declared in May 2020 that they will even backport Edge to Windows 7. So it is more a LOL then EOL. Too many important big businesses still depend on it.

It is high on the suggestion list.

@@IAmTimCorey yeah please do a chat app and store message in SQL

@@vandeljasonstrypper6734 - isn't this being phased out for Blazor?

I don’t have a recommendation, sorry.

Not sure. Maybe you have a different version of the tool.

This probably won't help you, as it is 5 months past, but might help others: I am using Visual Studio 2019, but the steps should be the same in VS2017. Create a new UWF project (you can just delete it later). Click "Project" -> "Manage NuGet Packages..." Then select the "Browse" tab. Search "Caliburn.Micro" and install the latest version v3.2.0 by Rob Eisenberg. It will ask to install supporting files, click OK. Close and trash that project then follow along with the tutorial as normal (I am sure there is a way to install it with PowerShell but I don't use NuGet that often). The option should now be available as shown in the video. Note: Caliburn.Micro is no longer under active development at the time of writing this comment. The original creator, Rob Eisenberg, stepped away from the code years ago; it was being maintained by Nigel Sampson. In June of 2020 Nigel stepped away from the maintenance of this code as app development is no longer the primary focus of their new job. Nigel will still continue to host the webpage and has pushed the release candidate for v4.x, but is looking for interested, responsible developers to transition and continue the opensource project. You can find the website in the NuGet package Info pane or by searching Caliburn.Micro . Good luck.

@@hattoff Thank you very much for writing this, I didn't figure it out myself.

You need to go through the Microsoft Store.

@@IAmTimCorey Nice!! Thanks for the pointer Tim!

Thanks for the suggestion. Please add it to the list on the suggestion site so others can vote on it as well: suggestions.iamtimcorey.com/

UWP is still supported. It hasn't lost support. I'm not sure what you are asking about.

@@IAmTimCorey If is it a good idea to start brand new project in UWP after .NET 5 will be released.

I can't guarantee the future but Microsoft is putting a lot of faith in UWP as the future.

UWP never stopped being supported.

It has always been supported.

That sounds like an issue on your PC.

Oh right i have visual studio *code* lol

No, I think the issue here is the plethora of options. If you had a really simple system, it wouldn't do what you want. So you would add a feature or two to make it perfect. Now imagine hundreds of thousands of people did that. Think of all of the options you would have. That's the issue. .NET Core applications have done a better job at hiding the complexity at startup. Look at how easy it is to get started with a Blazor Server app even though you are using dependency injection, application logging, HTTPS redirects and enforcement, SignalR, and more. UWP is just messy. Don't overlook what we are doing by reading the code, though. That is one of the best ways to learn how to build code, by reading code. Don't discount that as bad.

Thanks for the reply. Yeah, I think I will stay away from UWP for now. I come from Windows Forms with MFC, but most of my experience is in developing C for embedded microcontrollers. Most of the code on the embedded devices I had worked on was written by me (no RTOS). I'm trying to come up to speed with WPF and .NET Core now that I'm out of a fulltime job and need to find a source of income soon. Also, thanks for all your your fabulous videos.

Interesting. First time only when you launched, or every time?

every time, unfortunately

Visual Studio is slow compared to VSCode because Visual Studio is doing a lot more. However, those lockups seem suspicious. Do you have a spinning hard drive? That may be the issue. Otherwise, submit a feedback response about it.

my installations on an nvme.. ig ill just chalk it up to the program having to do a lot of shit as you said

They stopped working on it for a while, then they restarted but they renamed it to "Template Studio". You need to pick the one you want (WPF, UWP, or WinUI): github.com/microsoft/TemplateStudio The extensions are in the Visual Studio Marketplace as well.

It is.

I think WPF because there is less restrictions and less hoops to jump through.

@@IAmTimCorey yep i noticed when trying uwp app dev

Thanks for the suggestion. Please add it to the list on the suggestion site so others can vote on it as well: suggestions.iamtimcorey.com/

I do not accept sponsorships for my videos. I did briefly at one time, but have not since.

@@IAmTimCorey what about an affiliate program?

Yeah, I did a video on my thoughts about desktop apps in C# ( kzfaq.info/get/bejne/r9dgl7acppfaoIE.html ). WPF and WinForms are actually pretty modern. They just got backed by .NET Core ( kzfaq.info/get/bejne/q8ljp6ZnxNOppp8.html ), they are now supported with MSIX deployers ( video coming next week), and you can put them in the Store. Working in the cloud is a great option, though, if you don't mind web. Razor Pages, Blazor, and even third-party frameworks like Avalonia and Platform Uno are great options.

Microsoft got rid of their own app ad platform, but you can certainly use another one in your UWP app. Not sure what performance issues you are talking about - UWP compiles to native code and is typically faster than standard .NET. The UWP sandbox is generally a very good thing, you can still write unsafe code and get "full system access" if you want, though. Any .Net library targeting the ".NET Standard" will work on UWP and the .NET Framework - most libraries are moving in this direction for maximum compatibility.

@@dnwheeler UWP xaml elements really getting mess up when you on high resolution display, Acrylic, Gridview I have been reported this for them years ago but they still haven't fixed it

There still is. They just called it Template Studio instead of Windows Template Studio: github.com/microsoft/TemplateStudio

@@IAmTimCorey You're a champion!

I Alt+Tabbed, which shows the desktop background. I tried to do it quick, but it still showed up. The "Corey" is the desktop background art I was using at the time, which said "I Am Tim Corey" in script and it had logos for KZfaq, Twitter, etc.

Nope, that wasn't the point of this video. I can't start from scratch each video. I do have a video on how to install Visual Studio though: kzfaq.info/get/bejne/fZddjcmjnpOXqqc.html

Why?

I wouldn't think so. While you might not be able to use the template code that the wizard builds for you, you can learn from it and use it as a sample for what you want to do. That way you don't need to manually figure out each step. You can see it done for you and then just bring over what you want.

Trying to maintain legacy applications while innovating is very difficult. I agree that I don't think they have done a great job, but it is a hard job to get right. Don't forget that a bit reason why UWP struggles so much is because people won't get off of Windows 8, 7, and even XP. Creating a new OS/system would be even worse. Virtualization isn't really the solution, either, since you would end up basically running multiple older operating systems in parallel with your main system, which would cause all kinds of security holes.

@@IAmTimCorey I think Microsoft has done too good of a job supporting legacy apps but It's a double edge sword. You trade off having a better operating system with apps written for Windows 95 still able to run. I think Apple has a better balance on this thus a cleaner architecture. Look how they pulled off moving off Intel to ARM with virtually zero issue. I think it's possible for Microsoft to clean up by rewriting all their GDI windows APIs with what've learned so far. They can then support legacy apps with a Windows 10 sub system that's decoupled from the host OS via virtualization. They can then pour all their resources into a single development stack native to the OS API. Eventually after a decade, they can drop the legacy Windows support. Imagine all the new employment opportunities this will bring to the market. It's a bold move and I think it's possible from a technology standpoint. Whether Microsoft can pull it off is a different story. The failures of Microsoft beginning from Windows Vista to present has really been shameful.

Thank you!