Search

Toaday I got a comment from a blog reader named Fracisco…I think he wanted to know how to load new pages into a Silverlight website.  Just for him, and because I think many of you have the same problem, I made a video tutorial where I show you how to:

1. Create a Content Holder UserControl;

2. Make two pages called HomePage and AboutUs;

3. In App.xaml load ContentHolder instead of MainPage.xaml (the default action of a SL app) [...]

Hope, you read my first chapter of the Silverlight Tutorial “Silverlight Tutorials Chapter 1: Introduction to Silverlight”. In that post, we learned about the very basic informations on Silverlight, it’s System Requirements, pre-requisite to create a Silverlight application, XAP file, XAML file and hosting a Silverlight application.

In this chapter we will first discuss on how to create a new Silverlight project and the structure of it. Later in this chapter we will discuss on UserControls and various ways of developement. After reading this chapter you will be able to create a HelloSilverlight application and UserControls for your application.

Recently I had a developer ask me how he could fire an event from the CheckBox that I had put in the Style of the UserControl I gave him. 

I thought about it and, the problem is that objects in a Style are not really part of the Visual Tree until the Style is attached at runtime. 

This example is the result on making heavy experimental use of effects on a Textblock element. It has a visual appearance that reminds me of Jugendstil (Art Nouveau). Therefore I called it "Digital Jugendstil".

Let’s say you want to create a standardized “gadget” for your application, from which anyone can derive and create their own gadgets.

The desire:

• Provide a base gadget that has some sort of standardized chrome and some behavior to be inherited by all derived controls.

Richard Waddell demonstrates how to replace interfaces with Base Classes that inherit from UserControl.

ooNaverse sidebars are separate projects that focus on narrow issues within the ooNaverse. In this case, the demo just shows that a Position property can be implemented in an abstract base class (ooNaThing) with no UI that inherits from UserControl and in turn be inherited by a subclass (Seeker) that does define a UI (xaml file). Clicking on the page will cause the ooNaSeeker object to move to the click point by updating the Position property, which incidentally is a Dependency property and so will support animation of the ‘higher’ order class that inherits from it (Seeker). I provide the source mainly so you can have a working example where you can just lift the code if you want.

Adam Kinney announces that the first sections of the new Flash to Silverlight Guide are now ready.

The purpose of this guide is to familiarize developers and designers with Silverlight concepts by relating them to Flash concepts. Comparisons are drawn between each pair of concepts in effort to map knowledge from one platform to another.

In this blog post Joel Cochran shares a technique for centering a Silverlight application.

Last weekend, I was working on a Silverlight application and I wanted to stretch the background brush across the entire browser, but retain the content in a fixed space in the middle of the screen.  I could have done this by creating a gradient and then applying it as the background in my HTML/CSS, but I wanted the ease of design and flexibility that I have within Silverlight.  Here is what I did to accomplish the trick.

A week ago, I was discussing with one of my clients about developing Silverlight user controls and exchange data between them. There were a few interesting points that came up during the discussion and I thought this would make a good article.