UI design with XAML in Visual Studio 2017 - 1

XAML is a XML based language that Microsoft developed to create a applications the easy way. XAML is declarative that means that whatever
you declare up front is what you get. There is no more secret to it.
Universal Windows Projects use this language to build applications.

In this slideshow I show a step-by-step procedure to create an application with XAML which has just a button that displays Hello. It has some color and size to it. Although you will be seeing 18 or more slides once you grasp the spirit, you would do it under a minute.

In order to work with XAML you need Visual Studio 2017 Community. The good news is it is free. What is more BLEND, its comprehensive designer also installed at the same time. You may also need Windows SDK for Windows 10 which can be found on the Internet. There are various versions.

In developing on Windows Platform be sure to use the intellisense feature that takes out all the mystery out and gives you a very practical and intelligent way to work with design.

In this slideshow I show a step-by-step procedure to create an application with XAML which has just a button that displays Hello. It has some color and size to it. Although you will be seeing 18 or more slides once you grasp the spirit, you would do it under a minute.

So let us get on with this slideshow.

Comments

Post a Comment

Popular posts from this blog

UWP: Displaying formatted text in a TextBox Control

Image
The entry you make in a text box control is of data type text and sometimes you need to format it as a currency with thousands separator while displaying. Also, if the number of decimal places you enter is more than 2, you need to round it up to 2 in the output. How do you code this in a UWP app? Create a UWP page starting from a Blank UWP project with three controls as shown. There are two text boxes and a button. You enter a number in the top textbox (txt1) and click the button, the formatted currency will be displayed in the bottom textbox(txt2). The app displays as shown. Now provide for a click event for the button and insert code as shown: Convert_1 The string entered in txt1 is converted to data-type double, it is then 'rounded'. The rounded number is then formatted to show the currency symbol and the 1000's place delimiter you find, for example in Excel formatting. Here is the app after entering a number and c
Read more

UWP: XAML's ComboBox Control -Part 1

Image
Microsoft's Universal Windows Framework apps are well supported by Microsoft and you could use it for not only Windows but for other devices as well. You can also use UWP for cross-platform use. In the Universal Windows Platform (UWP) projects there is an advantage of one code that works on different device families (phone, tablet, desktop etc.). However, the UWP projects depend on using XAML.  ComboBox details can be seen in the Object Explorer of Visual Studio 2017 Community used in writing this post. In this post, I will show you how you may work with this controls for a UWP project. Getting the ComboBox Control Placing ComboBox on the Design area Adding ComboBoxItems We start with a Windows Universal blank C# project with the name JComboBox as shown. You will be asked for what target and minimum versions of Windows 10 that you want. The higher the version the more feature support. The Build version 16299 is chosen for both as shown i
Read more

Handling AppManifest Validation error

This error may show up if one chooses an image file that does not comply with the enumeration. Here is the description of the error: Severity Code Description Project File Line Suppression State Error  Validation error. error C00CE169: App manifest validation error: The app manifest must be valid as per schema: Line 26, Column 25, Reason: '' violates enumeration constraint of 'badge badgeAndTileText'. The attribute 'Notification' with value '' failed to parse. XXXXXX C:\Users\Owner\source\repos\xxxxxx\bin\ARM\Debug\AppxManifest.xml   I chose a resource for Badge in the Assets and Visual Studio spawned this error. The only way to get out of this was to comment out (or better remove) the following line in the AppManifest .xml Make sure you save the file after the removal as every time you Build, the AppManifest.xml gets recreated.
Read more