What is Silver Light?
Microsoft's Silverlight technology, launched at the NAB conference two weeks ago and pitched hard to developers at the Mix '07 conference this week, is being taken as a competitor to Adobe's Flash.
Since it is a framework for providing rich applications to the Internet
browser, it is indeed that. But though Silverlight and Flash are
competing technologies, Microsoft's offering is different from Adobe's
in key ways.
More than just a platform
Silverlight is being pushed side-by-side with Microsoft's Live
services for developers. Microsoft is opening up APIs (application
program interfaces) for its search engine, for Virtual Earth, for its
instant messaging service, and for other services, under generous, but
not unlimited, licensing terms. These services will allow the creation
of interesting online applications that take advantage of existing
Microsoft networks and resources. For example, Match.com
today demoed a new version of its service that can connect directly to
other Match.com subscribers who are MSN Messenger users. Mash-ups are
nothing new, of course, but it is important that Microsoft is giving
developers access to its computing resources as well as its user base.
Silverlight supports the display of high-definition video files,
and importantly, Microsoft will do the heavy lifting of sending them
over the Net. Streaming large media files is expensive, but Microsoft
will (optionally) host Silverlight media files and applications. This
will enable smaller developers to deliver large and high-definition
files quickly and reliably, without paying content distribution network
fees. Microsoft is promising reliable 700kbps throughput for media
files, and free distribution of all content on its network for one year.
After that, distribution will continue to be free up to 1 million
streamed minutes a month. Fees after that have not been set.
Also, Silverlight applications are delivered to a browser in a text-based markup language called XAML.
That's no big deal for Web users once they land on a site. But search
engines, like Google, can scan XAML. They can't dive into compiled Flash
applications. Flash-heavy sites do often wrap their applications in Web
code that search engines can crawl, although it's extra work for
developers and designers to do it, and may not yield search results that
are as good as they would be if the search engine was indexing the
actual application instead of keywords tacked on after the fact.
Silverlight applications will be more findable.
One thing Silverlight isn't though, is a competitor to Apollo (hands-on),
Adobe's technology that lets developers take their online applications
and make them into standalone desktop apps. Apollo developers will be
able to take advantage of capabilities that make applications behave
properly whether they are online or not. Silverlight does not yet offer
those capabilities, although I heard that apps written in Silverlight
will be able to modify the "chrome" or basic user interface of a browser
while they are running, to further obscure the difference between a
browser-based app and traditional software.
What is the purpose of using silverlight?
Silverlight is a plugin from Microsoft that is a lot like
Macromedia Flash. If a developer has developed something for their site
written with Silverlight instead of Flash, you won't be able to view it
without the plugin. There are many features that Silverlight has that
Flash does not, however, Flash is still the more popular of the two
plugins. For more information on Silverlight, browse the links given below
Hope this links help you alot
XAML Stands for --->
Extensible Application Markup Language
Purpose of XAML:
XAML is an XML-based
declarative markup language suitable for representing nested object
hierarchies, such as those of CLR objects. This makes it a good choice
for building user interfaces (which are inherently nested and
hierachical). This is how Windows Presentation Foundation employs XAML.
Windows Workflow on the other hand employs XAML to orchestrate
workflows.
Windows Forms was built as a managed wrapper over Win32, and is as
such limited by what Win32 can do. XAML when used in WPF works to
achieve the same goal: building user interfaces on Windows. But WPF was
developed from the ground up to be Microsoft's next-generation
presentation subsystem -- with a new composition system, uniform
programming model for documents, graphics, effects, animation and UI.
WPF is currently not a replacement for WinForms. You will find that
there are some things that WinForms does exceptionally well, and others
that WPF excels in. Besides, there is good interoperability between
these two technologies, so your solutions can potentially use the best
of both worlds.