The original version of this posting got lost in a recent database crash so that sort of gives me an opportunity to revisit my thoughts, a few weeks on from the original post with some more thoughts.  

Recently I have been in email correspondence with Vince Bonfanti of New Atlanta  in particular about BlueDragon.NET and that really started as a result of 4 clients of ours who had varying degrees of different problems in getting IIS7 to work reliably, initially with ColdFusion 8, I blogged about that here.  In essence, I think a good number of those issues relate to weakness in the web server connector and I have felt it to be somewhat weak for some time now.  What concerns me in particular is that this is the most critical link that ColdFusion needs and depends on.  Vince revealed to me that New Atlanta have rewritten the web server connector for IIS in native .NET code from it's current C++ version used by other CFML vendors.  Here are a few good meaty blog posts about BlueDragon.NET, I like the fact that the Microsoft piece mentions nothing nor even hints at migrating people off CF to .NET...

Bill Staples, Manager IIS Development at Microsoft about BlueDragon.NET

A Comparison Of BlueDragon.NET and ColdFusion 8 .NET Capabilities

Running CFML Natively On .NET instead Of JavaEE

I think the way that IIS7 is architected certainly lends itself to BlueDragon.NET more than previous versions of IIS, the fact that New Atlanta now has integrated capabilities within the IIS7 admin tool is another point worthy of consideration.