Windows Phone 8 Development for Absolute Beginners

Part 4: Introduction to XAML

Download this episode

Download Video

Download captions

Download Captions


Source Code:
PDF Version:

In this lesson, I want to talk about the XAML syntax we wrote in our first pass at the SoundBoard app. Hopefully you could see how the XAML we wrote impacted what we saw in the Phone preview pane. It's relatively easy to figure out the absolute basics of XAML just by looking at it, but I want to point out some of the features and functions that may not be obvious at first glance.

At a high level, here's our game plan in this lesson:

  1. We'll talk about the purpose and nature of XAML, comparing it to C#
  2. We'll talk about the special features of XAML ... little hidden features of the language that may not become obvious by just staring at it

My aim is by the end of this lesson you'll have enough knowledge that you can look at the XAML we write in the remainder of this series and be able to take a pretty good guess at what it's doing before I even try to explain it.

1. What is XAML?

In the previous lesson, I made a passing remark about XAML and how it looks similar to HTML. That's no accident. XAML is really just XML, the eXtensible Markup Language. I'll explain that relationship in a moment, but at a higher level, XML looks like HTML insomuch that they share a common ancestry. Whereas HTML is specific to structuring a web page document, XML is more generic. By "generic" I mean that you can use it for any purpose you devise and you can define the names of the elements and attributes to suit your needs. In the past, developers have used XML for things like storing application settings, or using it as a means of transferring data between two systems that were never meant to work together. To use XML, you define a schema, which declares the proper names of elements and their attributes. A schema is like a contract. Everyone agrees—both the producer of the XML and the consumer of the XML abide by that contract in order to communicate with each other. So, a schema is an important part of XML. Keep that in mind … we’ll come back to that in a moment.

XAML is a special usage of XML. Obviously, we see that, at least in this case, XAML has something to do with defining a user interface in our Phone's interface. So in that regard, it feels very much like HTML. But there’s a big difference … XAML is actually used to create instances of classes and set the values of the properties. So, for example, in the previous lesson we defined a Button control in XAML:

... that line of code is roughly equivalent to this in C#:

I've added this C# code in the constructor of my MainPage class. I'll talk about the relationship between the MainPage.xaml and MainPage.xaml.cs in just a moment, but we've already seen how we can define behavior by writing procedural C# code in the MainPage.xaml.cs file. Here, I'm merely writing code that will execute as soon as a new instance of the MainPage class is created by writing the code in the constructor of that class.

At this point, I now have two buttons ... one defined declaratively in XAML that has the content of "Hello World" and will quack when we click the button, and a new second button that has the content of "Quack". When we run the application:

we can see only one button. That's because the button we just created procedurally in C#, in the constructor of the MainPage class, is sitting on top of the first button we created in the previous lesson in XAML. Just to prove it, I'll add one more line of C# code that will set a margin on the new Quack button, moving it to the left 210 pixels:

The Margin property of the Button is of type Thickness, a general purpose class that represents 4 dimensions. In this case, we create a new Thickness class and set it's first constructor argument to 210 pixels. When we run the application again:

... we can now see both buttons.

The larger issue is that we have two (almost) identical buttons ... one created declaratively in XAML and the other procedurally in C#.

When I create a new XAML element like so:


I'm basically creating a new instance of the Button class.

When I set attributes on the Button element, I'm basically setting properties on the instance of the Button class.

The important take away is this: XAML is simply a way to create instances of classes and set those objects' properties in a much more simplified, succinct syntax. What took us 10 lines of C# code we were able to accomplish in just one line of XAML (even if I did separate it on to different lines in my editor, it's still MUCH SHORTER than it would have been had I used C# to create my objects.

Furthermore, using XAML I have this immediate feedback in the Phone preview pane. I can see the impact of my changes instantly. In the case of the procedural C# code I wrote, I would have to run the app each time I wanted to see how my tweaks to the code actually worked.

2. Introducing Type Converters

If you have a keen eye, you might notice the difference in the XAML and C# versions when it comes to the HorizontalAlignment attribute / property … If you tried:

myButton.HorizontalAlignment = “Left”;

… you would get a compilation error. The XAML parser will perform a conversion to turn the string value "Left" into the enumeration value System.Windows.HorizontalAlignment.Left through the use of a Type Converter. A Type Converter is a class that can translate from a string value into a strong type—there are several of these built into the Windows 8 API that we’ll use throughout this series. In this example, the HorizontalAlignment property, when it was developed by Microsoft’s developers, was marked with a special attribute in the source code which signals to the XAML parser to run the string value through a type converter method to try and match the literal string "Left" with the enumeration value System.Windows.HorizontalAlignment.Left.

Just for fun, take a look at what happens when you attempt to misspell “Left”:

… you’ll get a compilation error because the Type Converter can’t find an exact match that it can convert into the enumeration value System.Windows.HorizontalAlignment.Left.

So, the first characteristic of XAML is that it is a succinct means of creating instances of classes. In the context of building a Windows 8 application, it is used to create instances of user interface elements, however XAML is not just a user interface technology—it could be used for other purposes in other technologies.

3. Understanding XAML Namespace Declarations

Next, let's talk about all that XAML code at the very top of the MainPage.xaml file ... we ignored it until now.

At the very top of the file, we see the following:

While you're looking this over, remember what I said a moment ago—about schemas being a part of XML. If that's the case, then where does this XAML promise to adhere to a schema?

See lines 3 through 8 ... there are SIX schemas this MainPage.xaml is promising to adhere to. Each is defined with the xmlns attribute. The first xmlns defined in line 3 is the default namespace—in other words, there's no colon and no word after the colon like you see in lines 4 through 8.

The rest of the namespaces in lines 4 through 8 will use name / colon combination. So, just to be clear ... the :x or :phone is the NAMESPACE, that is associated with a SCHEMA (what we've called a contract). Each element and attribute in the rest of this MainPage.xaml MUST ADHERE TO AT LEAST ONE OF THESE SCHEMA's, otherwise the document is said to be invalid. In other words, if there's an element or attribute expressed in this XAML file that is not defined in one of these namespaces, then there's no guarantees that the compiler—the program that will parse through our source code and create an executable that will run on the Phone—the compiler will not be able to understand how to carry out that particular instruction.

So, in this example:

<Grid x:Name="LayoutRoot" Background="Transparent">

We would expect the element Grid and attribute Background to be part of the default schema corresponding with the default namespace defined at the location in line 3.

However, x:Name is part of the schema corresponding with the x: namespace defined at the location in line 4.

I have a bright idea ... let's try to navigate to default namespace to learn more about what makes up a namespace in the first place:

What?! The schema doesn’t actually exist at that URL! That’s because the schema is not published in the sense that you can go to that URL and view it. Instead, a schema is simply a unique name, similar to how we used Namespaces in C# to identify two classes that may have the same name—the schema (and therefore, the namespace in our XAML) keeps class names sorted out, kind of like a last name or surname. This URL, or more properly, we should refer to it as a URI (Uniform Resource IDENTIFIER … rather than LOCATOR) is used as a namespace identifier. The XML namespaces are instructions to the various applications that will parse through the XAML … the Windows Runtime XAML parser will be seeking to turn it into executable code, while the Visual Studio and Blend designers will be seeking to turn it into a design-time experience.

So, the second XML Namespace defines a mapping, x: as belonging to this schema:

Therefore, any elements or attribute names that are preceded by the x: prefix means that they adhere to this second schema.

But, what’s the difference? It’s subtle, but the second schema defines the intrinsic rules for XAML in general. The first schema defines the contract / rules for Windows 8 specific usage of XAML. In other words, the fact that we can work with the Grid, Button, MediaElement and the other Windows Phone 8 XAML elements without using a prefix means that they are defined in the default namespace.

Lines 5 & 6 define namespaces and schemas for the Phone and Shell, which are at a different URI, one that takes is cues from the Microsoft.Phone CLR namespace as defined in assemblies that were installed on our computers after we installed the Windows Phone 8 API. As you can see, the very first line:


indicates that the PhoneApplicationPage class itself is part of this definition. The PhoneApplicationPage derives from Windows.System.Controls.Page ... that just happens to be the same class that is a parent to Windows Presentation Foundation page classes, and Windows Store app page classes. It has a lot of the base functionality shared by all three of these project types. So, the upside is that you're able to leverage what you learn in this series to building WPF desktop apps and Windows Store apps. There will be differences, but there's a lot in common, too!

Lines 7 & 8 define namespaces and schemas that are used to allow Visual Studio's Phone Preview Pane on the left to display properly. These instructions are ignored at runtime, which is what line 9 is doing—when compiling the XAML code, ignore anything prefixed with :d.

Ok, I know there are some questions left unanswered … we could spend a lot of time talking about the specifics, but the main takeaway is that this code at the very top of each XAML file you add to your phone project does have a purpose, it defines the rules that your XAML code must follow. You'll almost never need to modify this code, but if you remove it, you could potentially break your application. So, I would encourage you to not fiddle around with it unless you have a good reason to. There are a few additional attributes in lines 10 through 14 ... we may talk about them later in this series.

4. Understanding the relationship between the .xaml and .xaml.cs files

In Visual Studio’s Solution Designer, you can see that the XAML files have an arrow which means that we can expand them to reveal a C# file by the same name, the only difference is that it has a .cs file name extension appended to the end. If you look at the .cs version of the file, you’ll see that it defines a MainPage class, and furthermore, it defines it as a PARTIAL class:

The other half of the equation is defined in lines 1 & 2 of the MainPage.xaml:


While it doesn't use the term Partial like it's procedural counterpart, it does indicated the relationship between the two.

Why is this important? This relationship means that the compiler will combine the output of the MainPage.xaml and the MainPage.xaml.cs files into a SINGLE CLASS. This means that they are two parts of a whole. That’s an important concept … that the XAML gets compiled into Intermediate Language just like the C# gets compiled into Intermediate Language and they are both partial implementations of a single class. This allows you to create an instance of a class in one file then use it in the other file, so to speak. This is what allows me to create an instance of the MediaElement class called _audioPlayer in XAML and then call its methods or set its properties in C#. We’ll see more examples of this later in this lesson.

5. Understanding Default Properties

Since XAML is essentially an XML document, we can embed elements inside of other elements. We've already seen an example of this:

<Grid ...>
<Grid ... >
<MediaElement ... />
<Button ... />

Here PhoneApplicationPage "contains" a Grid and the Grid "contains" a MediaElement and Button. Or, perhaps more correctly in XAML parlance, UserControl's Content property is set to Grid, and Grid's Children collection includes the MediaElement and Button. Depending on the type of control you're working with, the default property can be populated using this embedded style syntax. So, you could do this:

<Button Content="Hello World" ... />

... or this ...

<Button ... >
Hello World

since the Content property is the default property of the Button class.

6. Understanding Complex Properties and the Property Element Syntax

In some cases, merely setting attribute values masks the complexity of what's going on behind the scenes. A good example of this is setting Background="Red". We've already seen this procedurally in C# -- to accomplish the same thing:

myButton.Background = newSolidColorBrush(Colors.Red);

... we have to create a new instance of a SolidColorBrush and pass in an enumerated Colors value. This is another great example of a property type converter that we learned about earlier in this lesson. But some attributes are simply too complex to be represented as attributes.

When a properties is not easily represented as a XAML attribute, it's referred to as a "complex property". To demonstrate this, first I'm going to remove the Background="Red" attribute from the Button, remove "Hello World!" as the default property, and add it back with a Content="Hello World!" attribute:

Next, in the Properties pane, I'm going to set the Background property to a linear gradient brush.

  1. Select the Brush property to reveal the Brush editor.
  2. Make sure that Background is selected.
  3. Select the Linear Brush tab (middle tab).
  4. Move the selector all the way to the upper-right hand side of the color editor.

I should now see the following in the Phone Preview pane:

... but more importantly, let's look at the XAML that was generated by the Brush editor:

The XAML required to create that background cannot be easily set in a simple literal string like before when we simply used the word "Red". Instead, notice how the Background property is broken out into its own element:

<Button ... >

This is called "property element" syntax and is in the form <Control.Property>.

A good example is the LinearGradientBrush. The term “brush” means that we’re working with an object that represents a color or colors. Think of “brush” like a paint brush … this particular paint brush will create a gradient that is linear—the color will change from top to bottom or left to right. Now, admittedly, you would NEVER want to do what I’m doing in this code example because it goes against the aesthetic of all Windows Phone 8 applications. But, let’s pretend for now that we’re expressing our individuality by using a gradient color as the background color for a Button.

As you can see (below), if we want to define a LinearGradientBrush, we have to supply a lot of information in order to render the brush correctly ... the colors, at what point that color should break into the next color, etc. The LinearGradientBrush has a collection of GradientStop objects which define the colors and their positions in the gradient (i.e., their "Offset").

However, the XAML representing the LinearGradientBrush in the code snippet above is actually SHORTENED automatically by Visual Studio. Here's what it should be:

<LinearGradientBrush EndPoint="0.5,1" StartPoint="0.5,0">
<GradientStop Color="Red" Offset="1" />
<GradientStop Color="Black" Offset="0" />


Notice how the <LinearGradientBrush.GradientStops> and <GradientStopCollection> elements are omitted? This is done for conciseness and compactness and is made possible by an intelligent XAML parser. First of all, the GradientStops property is the default property for the LinearGradientBrush. Next, GradientStops is of type GradientStopCollection and implements IList<T>, the T in this case would be of type GradientStop. Given that, it is possible for the XAML parser to deduce that the only thing that could be nested inside the <LinearGradientBrush ... /> is one or more instances of GradientBrush, each being implicitly .Add()'ed to the GradientStopCollection.

So the moral of the story is that XAML allows us to create instances of classes declaratively, and we have a granular fidelity of control to design user interface elements. Even so, the XAML parser is intelligent and doesn’t require us to include redundant code—as long as it has enough information to create the object graph correctly.


To recap, we've learned about the syntax of XAML. Most of XAML is pretty straightforward, but there are a few things that are not quite as obvious:

  1. XAML is simply an implementation of XML, and relies heavily on schemas and namespaces to adhere to "contracts" so that different applications can create, interpret, display, or compile the XAML code.
  2. The purpose of XAML is to allow for a compact, concise syntax to create instances of classes and set their properties. We compared the procedural version of a button created in C# versus one created declaratively in XAML and saw how much less code was required.
  3. XAML requires less code due to it's built-in features like property type converters which allows a simple string value be converted into an instance of a class.
  4. For more complex property settings, XAML offers property element syntax which harnesses the intelligent XAML parser to rely on default properties and deduction to reduce the amount of XAML code required to express a design.
  5. We learned about the embedded syntax style and the embedded nature of elements which suggests a relationships between visual elements. For example, the PhoneApplicationPage contains a Grid for layout, which in turn contains input or other types of controls. These are represented with opening and closing elements representing containment or ownership.
  6. We learned about default properties; each control has a default property that can be set using that same style of embedded syntax.

Next, let's learn more about the Grid for layout, we'll learn about XAML's attached property syntax and how events are wired up in the next lesson.



Available formats for this video:

Actual format may change based on video formats available and browser capability.

    The Discussion

    • QuocTruong

      Thanks you. This lesson very helpful.

    • Muhammad​Faizan

      I find XAML more easy than HTML and CSS because you can design and create on the same Mark up, which is not the case with HTML !! or not favorable to do so !!

    • Yaman Maarrawi

      Thanks BOB! Is it possible if I relied on XAML instead of C#?

    • BobTabor

      @QuocTruong: Thank you!

      @Yaman Maarrawi: I'm not really sure what you're asking.  You will want to do your layout in XAML and respond to events using C#.  So ... rely on both?


    • Darko

      Excellent tutorials. Deeply explained and very useful for beginners. Bob you are awesome....I appreciate your work a lot!

    • BobTabor

      @Darko: Thanks Darko!

    • Progr

      Thanks for this lesson. But I am russian and i don't speak english very well and google translate not very correct, but i understend your lessons. Thanks

    • Everton

      Hi BOB!
      Do you have some video about WP8 Development with HTML5?

    • Rida221

      hey BOB!

      i thought i'd never learn to make windows phone app but thanks to you now it doesnot sound much insane to me!! GOD bless you bro for this initiative (Y) 

    • Clint

      @Everton: WP8 doesn't directly support HTML applications like Windows Store applications currently.  You could do a WebViewer and there are examples out that do that.

    • BobTabor

      @Progr: I'm glad you are able to get some benefit from the videos despite our language differences.  Thank you, my friend.

      @Rida221: Very nice,  thank you!  Glad they helped.

    • Yale

      Very helpful, thank you Bob! What about the style of Buttons in Windows Phone 8? In Windows 8, we can find the App.Resources commented in the App.xaml. But in Windows phone 8, how can I create a appBarButton outside of the AppBar, for example?

    • Clint

      @Yale: you can't leverage an appbarbutton outside the appbar but if you want the look/feel, Coding4Fun Toolkit's round button, that is chances are the closest.

      For styling, check out

    • Santosh

      Hey Bob,

      As per my knowledge,Windows phone users is very low than Android.Is it useful to learn windows phone.

    • itsaboutcode


      While setting the background color of the button, you used SolidColorBrush class but it's not coming in code intelli-sense. Can you help to fix this issue.

      I have fixed it by comparing my code with the solution provided. Actually we have to use the following name space which was missing from documentation.


    • BobTabor

      @Santosh: "The smaller the niche, the bigger the market."  A rich man (actually, the richest man I know) told me that and I've lived by it for the last dozen years.  I see great opportunity where there are millions of users but only thousands of developers.  Just try getting your app noticed in the sea of crap filling the other platform's app stores.  So as far as I'm concerned, yes.


      Can you point me to the exact step (above, in the text) where it is missing?  I can make a change.  Thanks!  But just FYI ... in the future, no matter where in .NET examples you see this ... you type in a class name you want to use but it acts like it doesn't recognize it ... this is what professionals do:  they use the shortcut the Ctrl + .   (period) to show the quick-tasks menu under the class name.  It will show the option to add the appropriate using statements.  I do this dozens of time each day and you should too.  Big Smile  Good luck!

    • BolleraSanju

      Execellent Tutorial !! No words to express!!

      I Started with C#... Tutorials  And Now I Am With Windows Phone Development..... Smiley

      Thanks a Tonn BOB!!

    • Gene

      Hi Bob,
      Regarding this line
      myButton.Background = new SolidColorBrush(Colors.Red);
      I am having an error on the SolidColorBrush as it has the red line below it. It is my first day trying to create my first app for Windows 8 and I am not sure where is problem that makes the red line to appear. Hope that you can assist me with this so that I could put colors in the Background of the button. Thanks in advance!

    • Gene

      Oh Bob, No worries about my question. I forgotten to add the using statement System.Windows.Media for that new instant to be able to execute. Thanks once again! Great tutorial!

    • Doctor Who

      Thank you, @Bob and @Clint, for these tutorials. This particular one covered ground that I'm, for the most part already familiar with, but even so there were things I didn't know about. For example, I didn't realize that a xmlns that wasn't named ((e.g.: :x="(something)") is known as the default namespace. Very handy!

      One question I'd like to ask. I'm going to be going along, doing the code as you do it. In my PetSounds project I've got a blue, wavy line under many of the static resources, like PhoneFontFamilyNormal or OhoneTextNormalStyle. If I move my mouse over any of these I get a popup that says:


      XAML: Resource 'PhoneFontFamilyNormal' is not found

      I don't understand why this should be, after all I am following your instructions, so what am I missing?

    • Clint

      @Doctor Who: do you have resharper installed?

    • Doctor Who

      , Clint wrote

      @Doctor Who: do you have resharper installed?

      Nuts, I've just asked this same question again, but on the next lesson in this series. I'm sorry for duplicating my question.

      No, I don't have resharper installed, but I do have the Telerik tools installed, so maybe that's what's going on.

    • Clint
      @Doctor Who: my gut says that is causing it. Doesn't happen on a "clean" version of vs
    • Clint
      @Doctor Who: like 2 versions ago with resharper, it would do what you are describing.
    • Simon

      What software are you using to record the screen and webcam at the same time? I am interested in creating help videos for my work and this is a much more personable way to create these help files.
      Thank you

    • BobTabor

      @Simon: I'd prefer to answer that offline.  Contact me at bob at you know the rest .net  Smiley

    • Ajay

      I am following the series. But when I type "myButton.Background = new solidcolorbrush(;", I am getting an error . Can you please help me with that ?

    • Clint

      @Ajay: c# is a strongly cased language which means upper and lower case letters are different.  Also SystemColors, not sure where you got that from.  Code should be:

      myButton.Background = new SystemColorBrush(Colors.Red);

      When you run into trouble, view our sample code for the lesson, those fully compile and run.

    • Rajeev Ulaganathan

      Hi Bob... i'm from India.
      I watched your video and tutorials in pdf, really awesome bob. .
      Its very easy to understand and its amazing. .
      I need a suggestion. Now i know well about Java and Android. . suppose that i learn Windows Mobile App development, will it cause problem to my career in future ?
      Cause My hobby is that always learning something. So Please Help me. .
      What i want to do further ? But i need my future should be brightfull. .

      Thanks in advance . . i hope really someone will help me. .

    • BobTabor

      @Rajeev Ulaganathan: There are two school of thought ... one is to be a generalist, the other, a craftsman.  You can go deep or wide, but not both ... just not enough time.  Personally?  I'm "all in" with Microsoft technologies.  I never even tried to install Eclipse or XCode or anything else.  To me, that didn't help me towards mastery and craftsmanship of Microsoft's API's and technologies.  And even at that, I'm still very narrowly focused within that niche.  So, I would say figure out where you want your career to go and pursue that.  

    • reza farhang

      @Bob tabor : How can i download these video with lower quality?
      iinternet speed in iran is low

    • BobTabor

      @reza farhang:  Yeah, mid-quality is the lowest unfortunately.  This is more of a Channel9 / company issue than a Bob / screencast guy issue.  To get Microsoft's attention, you should add that feedback ... see link in the footer of each page (below).  As of now, you could let it run for a while OR could grab the MP3 and listen along with the text.  I realize that's not idea, but at least you'll be able to get something out of it.  I tried to add screenshots at key moments.  Hope that helps, even if it is an unsatisfying answer.  Sad

    • Shalom29

      Great tutorial...learning a lot with them thumbs up to the team!

    • greenguard

      Awesome work ... thank u so much sir ... this help me alot :)
      Sir can u give me ur email address ???

    • dglambert


      I know it makes more sense to use XAML to write our apps and I am just being nit picky, but the reason you couldn't see both buttons in your example when running our app is because they were overlapped, but rather than messing with the margin couldn't you have just used HorizontalAlignment.Right???


    • dglambert

      Also still being picky, if you wanted to write using C# couldn't you have used Object initializers like so..

      Button myButton = new Button { Name = "MeowButton", Height = 200, Width = 200, 
      VerticalAlignment = System.Windows.VerticalAlignment.Top,
      HorizontalAlignment = System.Windows.HorizontalAlignment.Right,
      Background = new SolidColorBrush(Colors.Red), Content = "Meow"};

      This way you can still have very succinct code.


    • BobTabor

      @dglambert: In all things related to software development, there are many ways to achieve just about any goal.  Smiley  The objective was not to teach how to write succinct code or every possible alternative regarding layout.  The objective is to expose the qualities of XAML.  If you missed that, then I failed you.  I wanted you to see the forrest, not the trees.  

    • Chubbybrett

      @Ajay: I am following the series. But when I type "myButton.Background = new solidcolorbrush(;", I am getting an error . Can you please help me with that ? 

      I was having the same issue.  Here is how I fixed it.  Looking at the MainPage.xaml.cs file provided with tutorial, I noticed my setup was missing a namspace system.  I was missing line 11 which is: 

      using System.Windows.Media;

      If you add that, the system will now read SolidColorBrush(Colors.Red);

      I am a true beginner and was pulling my hair out but this resolved it.

      Hope this helps.

    • NinjaSpider

      Great tutorial...learning a lot with but can u say how windows phone is better than android?


    • BobTabor

      @NinjaSpider: I recently purchased a Samsung Galaxy S4 and an iPhone 5s along with my Nokia Lumia 920 ... yes, I have three phones ... I'm trying to learn development across all three in my spare time.

      I don't know enough yet to comment on the TECHNICAL differences between the phone hardware or OS's.  I only know my personal preferences from a consumer perspective at this point.  I know there are others who are much more well versed in the technical areas than I am.

      My impressions of the Samsung Galaxy S4 ... 

      (1) It's a tweakers dream ... you can change just about everything about the phone and which apps handle phone events, even the start screen, tapping on the button, etc.

      (2) It's too much power for the average person.  It's as if they shipped R2-D2 in a kit and let you assemble and change out his functionality to your liking.  However, unless you're prepared to tinker with your phone for days it will be maddening.  At some point I had to have a friend walk me through how to get the most out of the phone.

      (3) Worst, it serves three masters.  It has multiple personality disorder.  Google, AT&T and Samsung are all vying for control of the device.  My contacts are owned by AT&T and Google can't see them ... not sure how that happened, but makes sending texts absolutely frustrating.  You can't uninstall the apps from any of those companies.  I complained to a friend at Samsung and he agreed with me.  He also said that when his wife got a new phone he had to set it up for her and she didn't like it.

      For me, simplicity is the key.  I just want my phone to work, I don't need to tweak everything if it's obvious from the start.

    • Dan

      Thanks, that was a great overview of xaml.

    • sama20073

      I understand so much new item I don't know it before In xaml but when I show your course I feel something difficult in understand hhh that for reason my English language is some poor but rely is very good explain and easy to understood.

      thank you for this explain Mr. Bob.  

    • varunsinghal

      Sir first of all the entire series is amazing and i would really like to thank all those people who have put in their valuable time and energy in making this series a success.

      Next sir i have three questions:

      1. Why <grid x:Name="ContentPanel"> cant be written as  < grid Name="ContentPanel"> (line 30).

      2. What are phone , shell , x , mc after collen in lines 4-8.

      3. What is the fundamental difference between schemas and namespaces . or are they synonymous, i am a bit confused .

      Thanks in advance Sir

    • Clint


      1. it can, but needs to be Grid with a capital G
      2. those are namespaces declared at the top, most of the time you won't have to deal with them unless you are doing more advanced stuff like referencing items in different assemblies
      3. schema declares what something should look like, a namespace is where something lives / scope of it. for namespace. for schema
    • JasminMankad

      Hello Sir,

      I am from India and a huge fan after C# series.

      I am just wondering about a thing. In this lesson you have told about how to declare a Button member in C# page (MainPage.xaml.cs). So my question is if an app has buttons declared using C# code then if it has better performance than ones with XAML or not, as XAML integrally does type conversions. 

    • Clint
      @JasminMankad: no. I don't recommend pre optimize as well. Optimize when you need to.
    • Hieu

      Hi Bob, why do i creat new button by C#, the preview not change, but when run in emulator, it run correctly.

      // Sorry about my English Big Smile

    • Duncanma

      @Hieu:The preview is just showing you what the XAML will look like, so if you create a button (or another UI element) via code (C#) then that won't show up until the code runs.

    • Hieu

      @Duncanma:Yep, Thanks u Big Smile

    • ravikrana

      Hi Bob . How can i add media element such as image instead of Red button such as i did it using XAML . Here is my code

      <Grid x:Name="ContentPanel" Grid.Row="1" Margin="12,0,12,0">
      <Button Name="playaudiobutton"
      Height="200" Width="200" HorizontalAlignment="Left" VerticalAlignment="Top" Background="Purple" Click="playaudiobutton_Click_2" >
      <Image Source="/Assets/AnimalsPic/quack.png" ></Image>
      <MediaElement x:Name="QuackMediaElement"


    • BobTabor

      @ravikrana: I'm not sure what you're asking ... it looks like you've already done what you're asking to do?  Please clarify.

    • mpestana

      Hi guys.
      To change the position for the "Meow" button in C# we could just edit the "mybutton.horizontalallignment" to the right instead writing the Margin specifications number in a diferente line, am i correct? I mean, less code, less work :D

      Many Thanks Bob. Love these series.

    • isamubr

      Hello. First congratulation for the great videos. There is a typo in the writen part.

      In the part 4, the namespace is PetSounds and not SoundBoard.

      The text wrong is <phone:PhoneApplicationPage

    • krunal

      Hey BOB,

      Grt Job & thanks a Lot.....

    • Ronald Munodawafa

      Thank you so much for these episodes on Channel 9. They are really useful and I never thought I would actually reach out to learn XAML. I find XAML easier than Drag and Drop development. I feel I can actually write all my code away from my computer in text files and then simply import them into Visual Studio. Windows Phone development is pretty much a simplified procedure - much better and faster than development on other platforms - thanks to you guys. My goal is to push app development on Windows Phone to its limit in terms of aesthetic, efficiency and usefulness. When you chose .wav files for your assets I assumed you would have to use a library to manipulate lossy compression formats like MPEG-4 and Windows Media. But I was wrong. I commend the guys at Microsoft. Great job!

    • shostakovich

      thax for Absolute Beginners..:D

    • Adurability

      Thanks Bob Tabor, Am new on this platform and already enjoying your series... 

    • Adurability

      @Bob Will I need to download window 8 emulator separately???? 

    • cipher2079

      Great Job as Always..Thank you.

    • Qiuhaibo

      Great tutorial!!!Now I have a question raised :When I use the Name or x: Name?

    • cipher2079

      Part 4 was fun. I think you did a great job speaking in Spanish though i cant lie it was kinda funny but overall fun and lots of much need information about XAML...Thank you!! 

    • Jesus Garcia

      Hi Bob, When I write this line of code:
      myButton.Background = new SolidColorBrush(Colors.Red);
      from Solid to Colors. this appears underlined by a red line.
      How can I add this element?

      THanks for your help

    • nisarg

      cant find solidcolorbrush attribute..

    • Nisarg

      When I write this line of code:
      myButton.Background = new SolidColorBrush(Colors.Red);
      from Solid to Colors. this appears underlined by a red line.
      How can I add this element?

    • Andrea

      Do you know if in windows phone 8.0 or 8.1 is it possible to read contact groups from an app? I need to write an app to send sms to group with more than 25 users.
      In windows phone 8 groups have limit of 25 users. You can bypass those limit from outlook, but windows phone in those groups remove the "send sms" button..

    • ahmed

      my virtualization technology is disabled
      i have an optiplex 960 case
      and i have a bios version A03
      how could i fix this problem
      thanks in advance

    • Simon

      Hi, How can I reverse the option where to choose whether to create a Windows Phone App 8.0 or 8.1, Please?

    Comments closed

    Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums, or Contact Us and let us know.