InfoQ Homepage Silverlight Content on InfoQ
-
WAF and Caliburn: 2 WPF Application Frameworks
WPF Application Framework (WAF) and Caliburn are two open source frameworks providing the foundation to developers to write WPF/Silverlight applications based on the Model-View-ViewModel (MVVM) pattern using a layered architecture.
-
Microsoft Aims Its Latest Tool, LightSwitch, at Professionals. Is it a Tool for Pros?
Microsoft has announced a new product, Visual Studio LightSwitch, during VSLive! keynote in Redmond. LightSwitch is a VS product tailored for easy creation of Line of Business (LoB) applications. Some developers wonder if LightSwitch is truly for professionals, comparing it with Access.
-
Fixing Data Binding Problems in WPF/Silverlight
The data binding in WPF and Silverlight is amazing in all regards. Its power and flexibility are beyond compare. Unfortunately its resistance to traditional debugging techniques is equally impressive for the wrong reasons. There is no way to really step through the data binding process, but we collected some other techniques that developers may find useful.
-
Karl Shifflett Shows How to make VS 2010’s Binding Builder Actually Work
Visual Studio 2010 comes with a feature they call the “Binding Builder”. This tool, launched from the properties pane, helps developers quickly construct XAML bindings for WPF and Silverlight. But without some help, it doesn’t work when the data context is only set at runtime. Karl Shifflett shows how to work around this using design-time markup extensions.
-
Prism Prevents One Incomplete Feature from Derailing an Entire Release
Having modular code does not help when applications still have to be deployed in an all-or-nothing fashion. Prism addresses this by allowing you do deploy a WPF or Silverlight shell to the users separately from any specific functionality. Individual features are released out-of-band as modules that may be stored locally, on a corporate file share, or served up by a web site.
-
F# Now Supports Silverlight
Slipped into the Silverlight Tools for Visual Studio release is F# for Silverlight 4. While C# or VB is still recommended for UI design, F# offers some interesting capabilities for the business tier, especially if it is heavy on computations or data processing logic.
-
WPF vs. Silverlight: Choosing the Right Technology for a Project
There is some confusion about when to use WPF and when to use Silverlight. Choosing the right technology for a project depends on precise requirements the application has and the differences between WPF and Silverlight’s capabilities.
-
Silverlight 4 Tools for Visual Studio 2010 Brings Tools for WPF Developers Too
Silverlight 4 was released back in April without essential development tools.Recently it was announced that Silverlight 4 Tools for Visual Studio 2010 is ready. In addition to basic Silverlight 4 support and templates for RIA Services, there are many IDE enhancements to make working with Silverlight, WPF, and XAML easier.
-
Silverlight Toolkit Has Dropped Support for Silverlight 3 and Visual Studio 2008
The Silverlight Toolkit has been an integral part of the Silverlight platform since it first appeared in 2008. Now on its seventh edition, support for Visual Studio 2008 and Silverlight 3 have been dropped in favor of recently released Visual Studio 2010 and Silverlight 4.
-
Silverlight for Mobile Platforms – the Current Status
Microsoft seems to be pushing Silverlight into a cross-platform web application framework for mobile devices. Silverlight is already available for Windows Phone 7 and Symbian^1, and it seems it is being also ported to Android and iPhone.
-
Once Again .NET has Been Announced for the Nokia S60 Platform
It seems like every year we relay the announcement that the .NET platform is going to be available on the Nokia S60. In 2007 the now defunct Red Five Labs was talking about Net60, a version of the .NET Compact Framework. Then in 2008 Nokia announced that Silverlight 2 would be demonstrated at the MIX08 conference. Two full years later, we are just now seeing a public Silverlight for Symbian beta.
-
Windows Phone 7 Will Not Support Native Code
The development story for Windows Phone 7 has been revealed. As suspected, it is heavily based on Silverlight, XNA, and Flash. So much in fact that only managed code is allowed on the platform.
-
Silverlight 4’s COM+ Automation Raises Security and Portability Concerns
Silverlight 4 supports COM+ Automation when running as an Out-Of-Browser (OOB) application with elevated privileges. Microsoft indicated that this support is a result of enterprise customers requesting such a feature, offering as an example Office automation from Silverlight.
-
Moonlight 2.0 Comes with a New Covenant
Moonlight 2.0 (final version) comes with a promise from Microsoft to help the developing of Moonlight 3 and 4, and a new MS Covenant to end users protecting them from patent infringement by using Moonlight.
-
Silverlight 4 Brings Assembly Sharing with .NET
Assemblies built in Silverlight 2 and 3 are not binary compatible with the .NET Framework, so if you want to share code you need generally need to dual-compile. With Siverlight 4 and .NET 4, you will be able to use some Silverlight-based assemblies from within .NET 4.