rdlc code 39

rdlc code 39

rdlc code 39

rdlc code 39

rdlc code 39

rdlc code 39,

rdlc code 39,

rdlc code 39,
rdlc code 39,
rdlc code 39,

rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,

rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,

rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,
rdlc code 39,

first look at this in 15 when you saw how scripting was used to instantiate and manipulate the control. In this chapter, you ll take a look at how you can manipulate your XAML UI. It s a very high-level overview, so for more details, take a look at a book such as Introducing Silverlight 1.0 (Microsoft Press, 2007).

Listing 8-17. Marking a Class with the [Serializable] Attribute [Serializable] public class Employee { private int intID; private string strFName; private string strLName; private string strHPhone; private string strNotes; public int EmployeeID { get { return intID; } set { intID = value; } } public string FirstName { get { return strFName; } set { strFName = value; } } public string LastName { get { return strLName; } set { strLName = value; } }

Naturally you will want to customize the available feeds to suit the audience of your portal. The default list includes some 0.9-style feeds, as shown in Figure 9-2, along with some 2.0-style feeds, as shown in Figure 9-3.

In a programming sense, XAML tags should be treated as objects, with their attributes directly analogous to properties. Thus, when programming, you can just say <OBJECT>. <PROPERTY>=<VALUE>. One exception to this is when you are addressing attached properties that already have a dot syntax, such as Canvas.Left. In this case, you will use setValue and getValue to write and read properties, respectively. In JavaScript, your object will be a var, so you will need to set a var value to the object that you want to manipulate. You do this using the findName method of the Silverlight control to seek through its XAML content to get a handle on the object that you want. You can then access its programming model. To do this, the object must be named, and in XAML, you name an object using its x:Name attribute. That s a lot of theory, which upon first reading might be a little confusing, but with a little practice, you ll see that it is straightforward. Here s an example of a XAML document containing a TextBlock called txt:

public string HomePhone { get { return strHPhone; } set { strHPhone = value; } } public string Notes { get { return strNotes; } set { strNotes = value; } } } As you can see, the [Serializable] attribute is a class-level attribute. Hence it is placed at the top of the Employee class and marked as a serializable class. Listing 8-18 shows the Click event handler of the Serialize button. This time the code uses the SoapFormatter class. Listing 8-18. Serializing Objects by Using the SoapFormatter Class private void button1_Click(object sender, EventArgs e) { Employee emp = new Employee(); emp.EmployeeID = int.Parse(textBox1.Text); emp.FirstName = textBox2.Text; emp.LastName = textBox3.Text; emp.HomePhone = textBox4.Text; emp.Notes = textBox5.Text; FileStream stream = new FileStream(Application.StartupPath + @"\employee.xml", FileMode.Create); SoapFormatter formatter = new SoapFormatter(); formatter.Serialize(stream, emp);

The RSS Portlet discussed here is not yet a polished piece of work suitable for all situations, but it illustrates the techniques required to display an RSS feed in a portlet. Since it is open source software, it provides an excellent basis for developing a custom RSS portlet for your own purposes.

<Canvas xmlns="http://schemas.microsoft.com/client/2007" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" Width="640" Height="480" Background="White" x:Name="Page"> <TextBlock Width="197" Height="59" Text="This is the first text" TextWrapping="Wrap" Canvas.Left="96" Canvas.Top="35" x:Name="txt"/> </Canvas>

It is possible that you will want to make information from your application available as an RSS stream that third parties may subscribe to. For example, an information portal could represent the names of the available portlets as an RSS feed for interested parties. They would then be aware when new functionality was made available to them. Probably the simplest way to create a valid RSS stream is to write a JavaServer Pages (JSP) page. You cannot make an RSS stream available directly from a portlet since a portlet by definition must be displayed as part of a valid HTML page, whereas an RSS stream is an XML document. The RSS stream must be made visible through a servlet (either created directly or as a JSP page). Although we normally use JSP to generate HTML there is nothing to stop us from using it to generate other document types. A simple example of an RSS 2.0 compliant JSP page follows: