Finally, a place where I can claim First Post. I’m currently working on a Silverlight game based on the classic “Solar Wars” space commerce/cargo game (which is itself based on Dope Wars, et al). Another inspiration for this game is Ambrosia’s Escape Velocity. I spent countless hours being a galactic menace in that game.

One of the things I’ve noticed about editing XAML files in Visual Studio 2008 is that sometimes you’ll need to close the file you’re working on then re-open it in order to see certain changes take effect, in particular when you change the ImageSource attribute on an element.  That took me a while to figure

Last night I decided that my Silverlight game wasn’t heading in the direction it should, so I went back to a previous iteration with some insights from my recent effort. I’ve had a problem getting the vision of the game solid in my head. At first I had built a top-down, ship-centric shooter but I

I was using a pretty lame technique to move the background starfield under the player’s ship and the more I struggled with it, the more I saw its flaws.  I had 4 panels, each was the same size as the game screen and a pretty nice starfield pattern.  I would move the panels according to

Silverlight is a cut down version of the Windows Presentation Foundation, and was formally known as Windows Presentation Foundation Everywhere (WPF/E). This cut down version includes the base class library and WPF libraries that allow .NET developers to program .NET code that can be hosted in any web browser and on

In this post, we’ll discuss how to resolve two common issues which come while migrating Silverlight Beta 1 Apps to Beta 2. Below I am showing Beta 1 code and its equivalent code in Beta 2 Compile time error 1.  Does not contain a definition for InitializeFromXaml //Beta 1 System.IO.Stream s = this.GetType().Assembly.GetManifestResourceStream("MyNamespace.UserControl1.xaml");       FrameworkElement control =

Whenever we create a new Silverlight Application project in Visual Studio, it gives us a chance to Add a Host Web Project or HTML page. That host application actually renders Silverlight content by reading the .xap file which contains compiled binary of XAML and resources. Sometimes you may run into a situation when you default html

Today we’ll touch the three most lauded concepts introduced by the XAML (eXtensible Application Markup Language). XAML to me seems like XML + .NET. By that I mean XAML provides you the best of both worlds by leveraging descriptive nature of XML and object-oriented nature of .NET. It allows you to instantiate a .NET object

As we have seen in the previous post XAML provides new generation of opportunities by which we can describe an object. Here we’ll cover the remaining two concepts Attached Properties Markup Extensions Going back to previous example of TextBlock which is shown below <TextBlock Text=”Title:” Style=”{StaticResource TextBlockStyle}” Grid.Row=”0″ Grid.Column=”0″ HorizontalAlignment=”Right”></TextBlock> Attached Properties refers to the ability by

Sometimes we have requirement of adding multiple Silverlight UserControls over same ASP.NET web page (aspx). Like when you want to host silverlight web parts on a single aspx page in separate areas. All silverlight controls are zipped into a single .xap file. And the <asp:Silverlight> tag refers to xap file using source attribute as shown in