With gmStudio, the VB6/ASP/COM analysis and re-engineering tool from Great Migrations, you can control these things by changing the 'surface forms' used by the 'string machine' as it interprets the pcode generated by its compiler and authors it in the desired notation. For example, here are the default surface forms for Len:
<subcode id="Len">
<vbn role="function" narg="1" code="Strings.Len(%1d)"/>
<csh role="function" narg="1" code="VBNET.Strings.Len(%1d)"/>
</subcode>
To customize the C# code emitted for the Len operation you can apply an override and create a custom translation configuration:
<subcode id="Len">
<csh role="function" narg="1" code="%1d.Length"/>
</subcode>
The placeholder %1d indicates where the original parameter should be emitted into the C# code stream.
This is a simplification of a very simple case, but that's the idea.
NOTE: the default surface forms are closer to the original semantics of VB6. For example string.Length throws an exception in C# if the argument is null, but VBNET.Strings.Len() returns 0. That said, if you never expect a null string then throwing an exception when one occurs might be advantageous -- or not -- at least you have the choice.
