Support Statement: Refactor Remove, Reauthor and Spec codes

Here is a re-engineering example using the "Refactor, Remove" and a "Refactor, Reauthor" statements of gmStudio.

Screen.ActiveControl is a very difficult operation to upgrade because it is weakly typed and typically used in multi-type code like the function at hand.  Also the .NET Clipboard is a bit different from VB6 in a few ways.  Typically this type of code is best reworked by hand.  Fortunately, copy/paste is probably a tiny feature compared to the real logic in the app.  I am curious to see what our translation was.

A quick thing you can do for code that you plan to rework by hand is use a Refactor/Remove-stubout command in your translation script.  It's a "punt" but it does document the code you plan to rework, and it gets it out of the way of other build issues.  Stubout is a inexpensive and reasonable technique for methods that are highly-platform specific.  The stub-out I like to use here is status=conditional that wraps the translated code in #if and hides it from the compiler effectively hiding the build errors.

<Compile ...>
<Fix ...>
...
</Fix>
<Refactor>
<Remove identifier="Panel.frmPhoenMain.mnuEditPaste_Click" migStatus="Stubout" />
</Refactor>

</Compile>

<Refactor>
<Reauthor subprogram="Panel.frmPhoenMain.mnuEditPaste_Click"><![CDATA[
      public static void mnuEditPaste_Click(object sender, EventArgs e)
      {
 ... hand written code here ...
      }
]]></Reauthor>
</Refactor>