Introduction of code-behind XAML Silverlight


Introduction

Usually every XAML file has a corresponding code-behind page and code-behind language could have C# (this is default) or VB. At very first time when we create a new project, project selection windows has option to choose development language. Here it is:


Well, look at the screenshot given below, recall the Visual Studio ASP.Net development, we create new project and project explorer lists the files and a file named Default.aspx is default for our entire web project (in general), in Blend MainPage.xaml has the same role here (in general but both are very different stocks, will talk later). Also recall web.config file, app.xaml same role here (in general but both are very different stocks, will talk later). We start our editing or development in Blend from MainPage.xaml page and it is very important to understand the logics of both pages.



Both screenshots has same page code-front (bottom one) and code-behind (just above the bottom one) shown.

As in Code-Front

 x:Class=”SilverlightApplication1.MainPage”

In above code, ‘SilverlightApplication1’ is namespace name of this project and ‘MainPage’ is class name of this project. Remember, namespace name should always be same as project title and class name should always be same as File name for which we are writing code-behind (no use of extension name here).


Why we use additional namespaces like ‘using System; etc…’?

In almost every code-behind file we see already declared list of namespaces, what’s these? We see at first glance, namespaces represented in C++ as ‘include<iostream.h>’ or in VB ‘import System’ or in C# ‘using System’ these all appears at very top lines. A namespace is just a grouping of related classes. It’s a method of putting or using classes inside code. In java we use it as ‘package’. Namespaces are logical grouping rather than physical grouping. ‘using’ alias make it easier to qualify or identifier to a namespace or class in C#. Look at the above image that has list of namespaces, all these appears by default. There are huge list of more namespaces in .Net library that we will use as required.


InitializeComponent() method plays most important role in Silverlight, we should never delete the InitializeComponent() call from the constructor.

Comments

Post a Comment

Popular posts from this blog

Migrating database from ASP.NET Identity to ASP.NET Core Identity

Image
As you know ASP.NET Core Identity (table structure) is different from what we had earlier in ASP.NET Identity. Actually the identity system which we have today with .NET Core is very mature and continuously evolved be it ASP.NET Membership, ASP.NET Identity 1, ASP.NET Identity 2 and now ASP.NET Core Identity. Recently I had to migrate few application to ASP.NET Core and similar its identity database. Because the table schema is changed, i had to re-think and create migration script which I would like to share with you today. It is very simple and easy, just three step and I had everything ready: STEP 1 : Change name of existing tables STEP 2 : Create ASP.NET Core Identity tables STEP 3 : Migrate data from old tables (ASP.NET Identity) to new tables (ASP.NET Core Identity) Script:  https://gist.github.com/itorian/c699e8534b392a6c726ec66c48100072 You should also watch my video, where I demoed migration.
Read More »

Customize User's Profile in ASP.NET Identity System

Image
Note: You should read this post instead, I found below walkthrough will not work on ASP.NET Identity 2. I will re-work on this post soon. In this post you will learn how to customize User’s Profile and add some more fields like FirstName, LastName, EmailID etc with ASP.NET Identity System. In my last post I listed some of the great new features introduced with Identity system .
Read More »

Lambda two tables and three tables inner join code samples

In this blog post you will learn inner join using lambda queries. There will be two samples, in first sample you will see how you can join two tables and in second sample you will see how you can extend even further to join three tables and so on. I will sample in-memory data, but the same implementation will work with IQueryable (lazy query) too. Here's the code snippet:- namespace ConsoleApp1 {     class Program     {         static void Main()         {             var table1 = new List<Table1>();             table1.Add( new Table1 { Id = 1, Name = "Name 1" , Address = "Address 1" });             table1.Add( new Table1 { Id = 2, Name = "Name 2" , Address = "Address 2" });             table1.Add( new Table1 { Id = 3, Name = "Name 3" , Address = "Address 3" });             table1.Add( new Table1 { Id = 4, Name = "Name 4" , Address = "Address 4" });   
Read More »