The bit-arts Fusion product is not an object file linker and does not deal with COFF files. From the documentation it appears that Fusion packages all the dependent files into what appears to be a single EXE (just as VFP does with a project). An assembly language header controls the runtime injection of executable code into the process space (DLL's etc) and ultimately invokes the original programs entry point.

How would this technique help us leverage CLR compatibility? I don't think it does or would.

Regards
Neil