March 2009 CTP of Silverlight LOB Controls from Infragistics Now Available

I know I’m one week late to announce this in my blog. March 2009 CTP of Silverlight LOB controls from Infragistics is now available for download! I’ve been watching out for this as early as the first week of March and I was surprised to read in a blog this morning that the March CTP was released last March 23. I don’t know yet what really are in it but what is significant to know is that this release is built on Silverlight 3 Beta. That’s the main reason I haven’t explored it yet. My project is currently developed in Silverlight 2 and I will have to setup another development environment to test if my source code will work in Silverlight 3 Beta. For the meantime, I’ll just believe while not seeing for myself what’s new based on the following links:

Product Overview: http://www.infragistics.com/Product.aspx?id=7781#Overview

Release Blog: http://blogs.infragistics.com/blogs/devin_rader/archive/2009/03/25/netadvantage-webclient-silverlight-march-2009-ctp.aspx

I know you gonna ask this same question: Why Silverlight 3 Beta for this CTP? Here’s the answer: http://blogs.infragistics.com/blogs/jason_beres/archive/2009/03/27/silverlight-product-version-strategy.aspx

I’ll just wait for the right time to upgrade to Silverlight 3 Beta and that may be as early as next week after demos to the project stakeholders are all done. J

By Design, Infragistics’ XamWebMenu Root Items Can’t Have Icons

When I first tried to use XamWebMenu control (Silverlight LOB CTP Feb. 2009 version) for the application menu bar of my Silverlight project, I encountered what I thought was a bug in XamWebMenu. I could assign an image file to the Icon property of the top-level XamWebMenuItem but the image wouldn’t show up. I posted this query to the Infragistics’ forum:

And here’s the reply:

This code works and here’s the output:

About the issue on the VS2008 crashing and exiting when I resize the Preview and xaml windows, I found out by isolating the Xaml tags that this was happening when the XamWebSeparator was included in the Xaml. I haven’t asked Infragistics’ about this but I’ll post it again here when I have an answer.