Mobilize Blog

Save the date(s) for .NET Conf - Sept 12-14. Virtual conference includes technical sessions and how-to's, demos and much more. #dotNETConf is the place to be starting Sept 12. 

Another great Microsoft event in the bag. This week Richard Campbell (of ".NET Rocks!" fame), Sara Faatz of Progress Software and I headed to Las Vegas to hang out with 14K other Microsoft partners and to host a developer-focused Twitter party. Check out Richard Campbell's Twitter feed to see all of the posts - lots of great technical content plus we shot some great video as well. Companies like Docker, GrapeCity, Infragistics, LEADTOOLS, Syncfusion, Progress and many more contributed content and prizes. If you didn't attend Inspire, check out my favorite developer session "DevOps on Azure: loved by developers, trusted by the enterprise". There's some great stuff on open source investments, customer insights and partner opportunity. 

In our last blog post, we looked at how to change the styling of individual elements in our migrated Angular application. Just a reminder in case you haven't been following along, this is a simple hello world app migrated from Windows Forms to HTML and ASP.NET Core with WebMAP5.

Find the selector, edit the css file, and rebuild it. You can change the global styles.css file or individual css files for each component.

Or, as we will show in this post, you can change the whole kit and caboodle.

Progress Kendo UI has a full set of web components for Angular. And it happens to be our reference implementation for WebMAP. 

Kendo UI has three themes that are available: the default theme, which is what we implemented, a Bootstrap theme, and a material theme. Today we'll take our little hello world app and switch it to the hyper-cool material theme.

To set the stage, here's what our hello world app looks like using the default Kendo theme (which is the WebMAP default):

It's not bad, but there's room for improvement. Let's get busy.

Installing the Kendo UI material theme

Th is is easy-peasy. Open up the angular folder in Visual Studio Code, get a terminal, and install using NPM:

npm install --save @progress/kendo-theme-material

Once the theme has been installed, you can verify it by looking in node_modules\@progress\kendo-theme-material\dist where you should find the all.css file, a minified version of the styling for the theme. If you want to see what the theme does, the Kendo UI documentation has great examples.

Ok, all we have to do now is include the theme in our app and rebuild it. 

In our .angular-cli.json file we need to change the styles from kendo-theme-default to kendo-theme-material, like so:

All that remains is to execute an ng build command in the terminal and the front end code will be changed to the new theme. 

Here's our app running in material theme:

Themes are a great way to jumpstart a complete re-do of the look and feel of an app. And, of course, you can always go into the global styles or individual component styles to override something you want to change. We covered that recently. And of course, having done this for our "hello world" applet, I wanted to try it on our more red-blooded demo app--Salmon King Seafood. Here's a quick screen shot of the opening form with the material theme applied:

I had to tweak some styles a bit because not all the fonts looked great. Somehow we lost our background color, but that would also be an easy fix. We do get the coolness of the 3D buttons and form fields, so this is a nice upgrade. It's also a nice reminder of how easy it is to upgrade the look and feel of an app once it's correctly architected for the web.

We recently updated our WebMAP architecture posts to reflect the significant improvements that WebMAP5 makes in generated app code (compared to previous versions). If you haven't seen them, this is a good time to check out the details here, here, and here.

Before we jump into the last installment, let's briefly review what we leaned in part 1 and part 2. If you're just jumping into this here, you probably want to go back to the beginning and read from there.

It's been a couple of weeks and now we're fully recovered from the massive information dump we received at Microsoft Build 2018. Between tons of technical sessions, lots of new announcements, reconnecting with old friends, attending lots of parties and best of all, getting to hang out with bunnies and small horses (yes, Build had a petting zoo this year...), we had another great show. We have a yearly tradition of picking out our favorite sessions from Build so without further ado... 

Instead of boring old words today I just decided to show you some Build 2018. So check out the completely unedited video. And congrats to our XBox winners. We went a little crazy and gave away three, not two.

Tuesday May 8 dawned foggy with a promise of clear blue skies later. There was no fogginess in Microsoft's announcement of .NET Core 3, however where they are doing  a lot of work to make older technologies like WPF and Win32 play nice on Windows 10. They even got Paint to run on on .NET Core 3 without access to the sources. So that implies that implementing this on your old code could be as easy as replacing some libs.

Build is Microsoft's annual homage to dorkiness and it's here in full glory. The de rigueur attire is a teeshirt with some kind of nerdy slogan or product (acceptable alternatives include beer but only craft beer), jeans, and a backpack apparently stuffed with the owner's entire worldly goods. 

When I first joined Mobilize.Net--actually before I joined Mobilize.Net, since I was interviewing for the job--and I heard the business model was tools to do code conversion,