cheapesthostings.com

WPF Page Hosted Windows Applications and XAML Browser Applications (XBAPs) In WPF, you can also make page based applications. These page based applications are of two types: 1. Pages Hosted in Windows Application 2. Stand-alone XAML Browser Application(XBAPs) Lets try to understand these WPF Page based applications: 1. Pages Hosted in Windows Application In this approach, you create your windows application and host some of the pages in that Windows application using NavigationWindow or Frame. This approach is generally used in WPF applications to integrate some kind of wizard in your application, to show some help contents and documentation. Hosting Pages in Navigation Window System.Windows.Controls.Page class is used as top level container instead of Windows.  <Page...> ... ... </Page> But actually, there is one more top level container known as NavigationWindow (derives from Windows class) in which Page container is hosted. The NavigationWindow looks like an ordinary win

Localization and Satellite Assemblies in WPF: How to support Localization in your WPF application? In WPF applications, the unit of localization is the XAML file (technically, the compiled BAML resource that is embedded in your application). If you want to support three languages, you need to include three BAML resources. Satellite assemblies play an important role in localization of WPF applications. When you create a localized WPF application, you place each localized BAML resource in a separate satellite assembly. To add localization support to your WPF application, just go to your .csproj file and add <UICulture>en-US</UICulture> under <PropertyGroup> element. Now Build your project and you will get a folder named en-US created where your exe is placed.  If you go inside this folder, you will get an assembly with the same name as that of your exe but with different extensions. For example, if your application exe name is MySampleApplication.exe , its name woul

WPF Elements and Controls: Basic Concepts and Questions In this article, I have covered very basic concepts of WPF Elements and Controls in the form of questions and answers like the difference between elements, controls, content controls, headered content controls and layout containers, difference between tooltip and popup, difference between radiobutton and checkboxes, lexicon file etc. Last question illustrates the difference between resource files and content files in WPF ( this question is out of the blog post title as these files are not WPF elements ). 1. What is the difference between WPF Elements and WPF Controls? There is a difference between WPF Elements and WPF Controls. All the WPF Controls are WPF Elements but vice-versa is not true. Any WPF element which can receive focus and accepts inputs from keyboard or mouse is called WPF Control. For example: Textbox, Button are WPF Controls. Exceptions: Tooltip and Label are also considered as WPF Controls because Tooltip appear

WPF XAML: Property-Attribute and Property-Element Syntax for Simple and Complex Properties Property-Attribute and Property-Element are the two approaches in WPF XAML to set the properties of the elements. I will take a very simple example to clear the concepts of both of the Property-Attribute and Property-Element approaches. Lets try to set the background property of the grid. I want to fill the background of the grid with some gradient color. Lets see how can we do this using XAML in WPF? Suppose I have to set the background of the grid to Green. I will set it like this: <Grid Name="MyGrid" Background="Green" > .... .... </Grid> In the above case, I have used Property-Attribute syntax for setting the Background property. WPF has used default brush and painted the area with solid color. But what if you want to use some complex brush and want to paint the background with gradients instead of simple solid color?  In this scenario, you will have to use Pro

WPF XAML Namespaces, Prefixes and Conventions In WPF, XAML contains namespaces for defining controls for your XAML document. You can also map other .NET namespaces to XML namespaces and use them in XAML document. There are some conventions for using prefixes with these namespaces in XAML. Lets go point to point to explore everything about XAML namespaces, prefixes used with namespaces and conventions for using prefixes in XAML. <Window x:Class="SampleApplication.MainWindow"   xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"   xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"   Title="MainWindow" Height="350" Width="525">   <Grid>          </Grid> </Window> 1. xmlns  attribute is a specialized attribute in the world of XML that is reserved for declaring namespaces. 2. The above default XAML code contains two XAML namespaces.  http://schemas.microsoft.com/winfx/2006/xaml/presentati