Wahlin on .NET

What's New in Silverlight 3?

The newest version of Microsoft's answer to Flash is now out. Dan gives a quick rundown of what's different, from the improved graphics and networking support to new controls and styles.

Silverlight 3 has been officially released and available for download! This is definitely exciting for me, personally, because my company has been working on a Silverlight 3 client application for the past few months and really enjoyed the new features.

Speaking of which, here are some of the key features Silverlight 3 brings to the table:

Out-of-Browser Support

Users can run a Silverlight 3 application in the browser or run it directly from the desktop even when they're not connected to the Internet. This supports several sync scenarios that can be useful when a connection isn't always available.

Enhanced Graphics Support

New features include GPU acceleration, perspective 3-D support, bitmap and pixel APIs for dynamically generating images, videos, etc. Animations can also be eased in and out and perform many other cool effects. Pixel shaders allow objects to have different effects applied to them, like shadows and blurs.

New Controls

Silverlight 3 provides many new controls that can be used to build solid line-of-business (LOB) applications. Controls can be bound to each other using element-to-element binding, and validation can also be performed more easily. Several new controls are also available in the Silverlight 3 toolkit released by Microsoft.

Better Navigation

Navigating between Silverlight "pages" is now built-in along with better search engine optimization (SEO) support and deep linking.

Enhanced Text Rendering

One knock against Silverlight 2 was that text didn't render as clearly as it should in some situations. Silverlight 3 includes a major update to the text-rendering engine. Text renders very crisply now.

Enhanced Styles 

Silverlight 3 provides merged dictionary support, allowing multiple style files to be merged into an application (similar to how a standard Web application can use multiple CSS files). This allows themes and other styles to be switched much more easily. Styles can also be based on other styles, similar to inheritance in OO languages.

Faster Transfer of Data 

Windows Communication Foundation (WCF) support was available in Silverlight 2 but Silverlight 3 now adds support for binary XML serialization, which allows data to be transferred between a Silverlight application and a WCF service much faster than before.

Assembly Caching 

Silverlight 3 allows developers to store assemblies on a central company server and Silverlight 3 applications can then download them as needed rather than downloading everything upfront in a single .XAP file. This can significantly speed-up application load times.

Enhanced Networking Support 

A new client networking (ClientHttp) stack is available that supports more verbs than simply GET/POST. Applications that fully leverage REST APIs will benefit from this new feature.

HD Media Support 

Silverlight 3 includes support for GPU acceleration (as mentioned earlier) as well as 1080p HD videos to be played over the Web. New codec support for H.264, AAC audio and MPEG-4 content is also included. If you need to provide media solutions, then Silverlight covers all of the major scenarios now.

Here are some other changes to Visual Studio and Silverlight applications in general:

  • The Visual Studio 2008 designer has been removed for Silverlight 3 applications. A lot of developers turned it off, anyway, so all of the dev efforts have gone into the designer that'll be available in Visual Studio 2010. Expression Blend 3 can also be used, of course.

  • The Silverlight ASP.NET server control isn't used now. It simply emitted the object and associated params tags, anyway.

  • Expression Blend 3 has also been released, along with a new feature called SketchFlow. SketchFlow allows application prototypes and mock-ups to be created more easily in order to get customer feedback. Though I rarely used Blend for coding previously, it now includes code intellisense, which is a nice feature to have and adds support for behaviors, importing Adobe Photoshop and Illustrator files, and integrating sample data into applications.

To get started with Silverlight 3, go here.

About the Author

Dan Wahlin (Microsoft MVP for ASP.NET and XML Web Services) is the founder of The Wahlin Group which specializes in .NET and SharePoint onsite, online and video training and consulting solutions. Dan also founded the XML for ASP.NET Developers Web site, which focuses on using ASP.NET, XML, AJAX, Silverlight and Web Services in Microsoft's .NET platform. He's also on the INETA Speaker's Bureau and speaks at conferences and user groups around the world. Dan has written several books on .NET including "Professional Silverlight 2 for ASP.NET Developers," "Professional ASP.NET 3.5 AJAX, ASP.NET 2.0 MVP Hacks and Tips," and "XML for ASP.NET Developers." Read Dan's blog here.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube