DotNet Geeks

Interactive Silverlight

rsshivs — Sat, 29 Aug 2009 18:43:23 +0000

Events and Event Handlers

A Silverlight event is something that occurs while a Silverlight application is running.

This “something” could be a mouse click, a mouse movement, keyboard input, the

application receiving or losing the focus, the application being fully loaded, or something

else altogether. All events are tied to an object, so it makes a difference whether

the mouse click occurs while the mouse pointer is, say, over a given rectangle or text

block.

Silverlight currently supports more than two dozen events, and future releases may

have even more. This chapter focuses on the most important ones, and provides the

background knowledge you’ll need to work with previously unknown events.

An event handler is a piece of code that is executed once an event occurs or is fired. The

concept of both events and event handlers is very similar to the concept of JavaScript

events in HTML.

Events and Event Handlers

A Silverlight event is something that occurs while a Silverlight application is running.

This “something” could be a mouse click, a mouse movement, keyboard input, the

application receiving or losing the focus, the application being fully loaded, or something

else altogether. All events are tied to an object, so it makes a difference whether

the mouse click occurs while the mouse pointer is, say, over a given rectangle or text

block.

Silverlight currently supports more than two dozen events, and future releases may

have even more. This chapter focuses on the most important ones, and provides the

background knowledge you’ll need to work with previously unknown events.

An event handler is a piece of code that is executed once an event occurs or is fired. The

concept of both events and event handlers is very similar to the concept of JavaScript

events in HTML.

Using Shapes

rsshivs — Sat, 29 Aug 2009 18:16:11 +0000

Most typical Silverlight visual elements are shapes: geometrical elements that make up

the visual experience of the application

Most typical Silverlight visual elements are shapes: geometrical elements that make up

the visual experience of the application

There are several of them, and many of them are specific to certain shapes, but the

following three properties are shared among all shapes:

Fill

How to fill the inner area of a shape, e.g., by providing a color

Stroke

How to paint the outline of a shape, e.g., by providing a color

StrokeThickness

The width of the outline, in pixels (must not be an integral value)

The easiest one is a linear curve, but they are easy to draw without any

extra help from Silverlight. However, there are more complex variants. A quadratic

Bézier curve (called that because in the defining formula values are squared) uses a socalled

control point to shape the exact look of the curve

XAML

rsshivs — Sat, 29 Aug 2009 18:10:48 +0000

XAML is an XML dialect, so we will use a lot of angle brackets throughout this book.

In this chapter, we will have a look at the most important XAML elements. It is virtually

impossible to cover them all in a book of this size, but we will present as many as

possible to let you dive into XAML with maximum speed.

If you have already worked with XAML for WPF applications, you already know most

of what is covered in this chapter (and most of Chapter 6, as well). However, there are

some subtle differences: Silverlight does not support the full XAML format like WPF,

but only a subset. Future versions of Silverlight will increase the percentage of supported

elements and attributes, but some things just cannot work in a web browser as they

do in a desktop application.

The root element of every XAML file is

Silverlight content. “Positioning Elements will show other uses for the

For now, just remember to put this element at the beginning of each XAML file

and supply the correct namespaces as follows:

Difference Between JVM and CLR.

rsshivs — Sat, 25 Apr 2009 12:26:50 +0000

CLR will Cache the Native Code and load it whenever needed.

JVM doesn’t Cache Native code everytime it will compile and run it.

CLR does JIT compilation.

JVM does Interpretation.

Due to this ASP.Net is 4 times faster than JSP Servlet.

What is a JIT Compiler?

rsshivs — Fri, 24 Apr 2009 11:51:33 +0000

.Net Assemblies needs to be JIT Compiled.

A JIT Compiler can Convert MSIL Code to Native Code.

A Native Code is proproitary to a Machine it can’t be run in another Machine.

MSIL is Platform Independent.

There are 3 types od JIT Compilers

Standard JIT
Pre JIT
Eco-JIT

1) Standard JIT

Only Current Class requiered is loaded in .Net on Demand.No Extra Memory is Allocated .

2)Pre – JIT

Compiles and make Native Code before executing.Wecan’t run this without Caching.We can’t run this in mobile devices.

Ngen.exe is a tool used for generating the Native Code for entire class.

C:>Copy D:\Hello.exe C:\Echo\

C:\Echo>Ngen Hello.exe

using Pre-JIT compiler is preferrable.

Native Code is not portable and is not saved along the Exe.

After Native code generation we can’t delete the EXE/Assembly because Ngen will convert only MSIL to Native Code.It will not have Registry or Metadata.

Eco – JIT

It generates the Native code for that particular Class/Assembly ,runs it and the deletes it inorder to save memory.

This is mainly used in mobile devices like PDA etc.

In this feature .Net acts like Java.

What is a Meta Data?

rsshivs — Fri, 24 Apr 2009 11:36:35 +0000

Meta Data is the data about a data.

Assembly Description

Assembly Description has all the information about the Assembly

eg.

Assembly Name.
Assembly Version.
URL.
Author.
Hashcode – A Unique number allocated for each Assembly.
Strong Name – Digital Certificates (Optional Feature).
Culture – Its the Language in which it displays the messages(default EN-US).
Custom Attribute – User Defined Property.

Type Deescription

Type Name
Access Modifier
Base Type
Members – Attributes,Methods,Constructors,Etc.

Dot Net Assemblies are Self contained/Defined Assemblies.

To install a .Net Application just do X-copy.i.e,Copy – Paste.No need to install in the Registry.

Types

rsshivs — Thu, 23 Apr 2009 11:30:04 +0000

There are Two Types in DotNet

1)Value Type

2)Refrence Type

Structures,Enums,Int Float,etc are Value Types

Classes,Interface ,Delegates,etc are Reference Types.

A Software in Dotnet is the collection of Value Types and Reference Types.

What is PEEP?

rsshivs — Thu, 23 Apr 2009 11:15:15 +0000

PEEP – Portable Executable Entry Point.

It is the Starting point and the Ending point of any Application.In DotNet Main Method is the Portable Executable Entry Point.Application Without Main is called a Class Library.

A Class Library doesn’t have a PEEP.

Silverlight Life Cycle

rsshivs — Mon, 13 Apr 2009 10:00:46 +0000

The user request the HTML entry page in the browser.
The Silverlight plug in is loaded.It downloads the XAP file with your application.
The Silverlight plug in reads the AppManifest.xml file from the XAP to find out what assemblies your application uses.It creates the Silverlight runtime environment and then loads your application assembly into it.
The Silverlight plug in creates an instance of your custom application class.
The default constructor of the application class raises the Startup event.
Your application handles the startup event and creates the Startup page.

Silverlight Website Types

rsshivs — Sat, 11 Apr 2009 09:37:58 +0000

Using Visual Studio 2008 You can create 2 type of Websites:
1)HTML web site: In this case, the entry point to your Silverlight application is a basic HTML file that includes a Silverlight content region.
2)ASP.NET web site: In this case, Visual Studio creates two projects?one to contain the Silverlight application files, and one to hold the server-side ASP.NET web site that will be deployed alongside your Silverlight files.

The entry point to your Silverlight application can be an ordinary HTML file or an ASP.NET web form that also includes server-generated content.
No matter which option you choose, your Silverlight application will run the same way,the client browser will receive an HTML web page, that HTML page will include a Silverlight content region, and the Silverlight
code will run on the local computer, not the web server.
However, the ASP.NET web approach makes it easier to mix ASP.NET and Silverlight content.