Blog

First of all, if you don’t currently use the ColdFusion debugger (or FusionDebug), you are really missing something big. These tools are huge productivity enhancers, especially for dealing with complicated code and tracking down elusive bugs. If you want more info on debugging in CF, check out this post from Charlie Arehart.That said, there are a couple of things I’d like to see improved in CF 9. Firstly, Adobe needs to make it easier to install/setup the debugger. It’s not too painful right now, but I do think it’s too complicated. If they made it as easy to setup as ColdFusion itself, I’d be a happy camper.Another improvement I’d like to see is how you actually start the debugger. Today you have to create a new debugger profile for every project. This kind of makes sense, because you have to define the web URL that the debugger needs to run from (the CF instance it needs to work with). However, I think it would be awesome if you could just fire off the debugger, and then it would ask you what URL you are debugging against, and then it would figure the rest out from there. And then the debugger would remember that URL for the rest of your Eclipse session, or maybe it could store it in a config file, tied to your current project (or if you aren’t in a project, tied to the current file you are editing).