Silverlight and Google Chrome

Interesting response from a Silverlight MSFT on their forum regarding Chrome:

Hello, currently we don’t have plans to support Chrome. We will support it in the future if it gains enough market share.


So, this is interesting, I thought Silverlight’s whole concept was to be able to run on the different browsers ? 

To completely ignore Chrome will be a bad idea.  It’s one thing to say ‘we are working to add support for Chrome vs. we don’t have plans to support Chrome’.

Flash works…

Google Chrome

blog here

First thoughts:

1. sounds really good – the comic ( outlines some of the features of Chrome – in particular is how they will sandbox each tab, also the ‘V8’ engine for javascript – anything that makes javascript run even faster is good for all of us web developers  🙂

2. will it steal from IE, or from Firefox.  For example, although aimed at IE, FF is already open source and Google spends alot of money to make it the default search engine for FF.  Although, Mozilla CEO has blogged about how Google will continue to contribute to Mozilla.  I’m thinking that it would steal from the Firefox user base instead of the IE one.  But, that being said, I know that as a FF user, the plugins are a major part of why I like to use Firefox – but at the same time, I’ve seen first hand how easy it is to bring down FF with some javascript/ajax  running wild  🙂

3. this will probably mean more incapability issues for us web developers to worry about.  IE6 obviously is the biggest nightmare – but currently I test all my web apps with IE 7 and FF 3.0.  I end up bouncing back and forth as well because FireBug is so good – so I debug and test with FF but then run IE to validate it does what it is suspose too.  It will be a pain to add yet another browser to this fold.  (I ignore Safari right now…)

We’ll see – on the flip side, it might be a brower-killer that competes with Microsoft… who knows!  Stay tuned!

So…definitely read that comic – it’s cool, even for the experts out there  🙂  Not only does it talk about Chrome’s sandbox tabs (and ‘Chrome Bot’ – lol), but explains what happens with the other browsers tabs…  good stuff in and of itself  🙂

I watched the launch today, read the comic – I’m impressed…

More on V8  here:


SQL Server 2008 Report Builder 2.0 RC1 Ready for Download

Microsoft has released SQL Server 2008 Report Builder 2.0 RC1. The Report Builder has full support for SQL Server 2008 Reporting Services including: various report layouts, data visualizations and formatted text.

According to Microsoft, “SQL Server 2008 Report Builder 2.0 provides an intuitive report authoring environment for business and power users.”

Report Builder RC0 was first released as part of SQL Server 2008 RC0, but it was not included in SQL Server 2008 RTM. Report Builder RC1 is released now, as a stand alone installer, with the following features on top of RC0:

  • Easy to use wizards for creating table, matrix and chart data regions.
  • Support for directly opening and editing reports stored on the report server.
  • Support for using server resources such as shared data sources.
  • A query designer for Microsoft SQL Server data sources.
  • Enhancements to the Report Builder 2.0 ribbon.


This is interesting, as I have a customer right now that is interested in creating their own reports with Reporting Services…looks like I might need to explore this in greater detail – we’re currently running SQL 2005.

Additionally, I can only hope the SQL 2008 Reporting services includes VS 2008 support.

I’m not sure if NHibernate runs on SQL 2008 as there was no 2008 dialect released with the latest version of NHibernate .

Guess I might have to see…  🙂

ASP.NET MVC Preview 5 and Form Posting Scenarios

Scott Guthrie covers the new features of Preview 5:

These new features include:

  • The ability to publish a single action URL and dispatch it differently depending on the HTTP Verb
  • Model Binders that allow rich parameter objects to be constructed from form input values and passed to action methods
  • Helper methods that enable incoming form input values to be mapped to existing model object instances within action methods
  • Improved support for handling input and validation errors (for example: automatically highlighting bad fields and preserving end-user entered form values when the form is redisplayed to the user)


Scott covers each of those items in his blog post.