I've been spending some time recently giving the new Bluedragon.net a once over with a view to possibly replacing some of my existing CFMX servers. A major reason for this is to eventually move to .NET proper and ditch the CFML. (I should note here the choice of .NET over Java is due to the Windows 2003 install base).

So, I've been looking at BD thinking about how much hassle there would be migrating across (guarantee it won't all work straight off no matter what New Atlanta say) and what the benefits would be. But then I though, why bother with BD.NET? Why not just start building new components in native .NET (e.g C# or similar)? I can currently run .NET on my servers due to the fact I already have IIS, I can access my .NET components via Web Services, I don't have to fork out a few thousand quid for BD licenses and I also end up in ultimately (and arguably) a better place - the .NET framework.

So the question raises itself - if you want to move to .NET - why bother with BlueDragon?

Note the the Java version of this argument isn't so strong as CFMX is already on Java so there would be no extra step in moving from CFML to Native Java/.NET.