I got to play with FusionDebug for the first time the other day and i’ve got to say i’m impressed. Since the year dot i’ve lived without step debugging in ColdFusion - it’s always been present in Visual Studio but we were always limited to dotting CFDUMPs around cf templates to aid in debugging. No more…or rather, I’m just catching up!
FusionDebug 2.0 was released not so long ago, I never saw v1.0 but the sales team at Integral say that 2.0 is leaps and bounds better that the first release.
Anyway, my first playing with it was with a Fusebox5 application i was building - I’d set it all up as the instructions say and all worked great, even going cross project in Eclipse to a project of CFCs - as i stepped through code it jumped between my open projects in Eclispe. Anyway, at one point i put a breakpoint in a layout file and that caused FusionDebug issues with looking up the source code - due to the parsed files that Fusebox uses. So i pinged the FusionDebug mailing list and found out about a feature of Eclispe I never knew about - linked folders in projects. It’s only accessible via FILE > NEW > FOLDER and then you click the Advanced button you enter a folder alias but then a path to the folder. In my case, I removed the existing ‘parsed’ folder and added a new parsed folder linked via a UNC path to the parsed folder on the file server - and now when i debug FusionDebug is all happy as it has access to the source code that it requires.
Recent Comments