Artinsoft+vbuc+v401042273+verified ((top)) -

using System.Windows.Forms; namespace MigrationHelpers { public static class ToolTipHelper { private static ToolTip _sharedToolTip = new ToolTip();

public bool AppliesTo(string vb6ControlName, string vb6PropertyName) { // Apply this logic only to Labels and the ToolTipText property return vb6ControlName.Equals("VB.Label", System.StringComparison.OrdinalIgnoreCase) && vb6PropertyName.Equals("ToolTipText", System.StringComparison.OrdinalIgnoreCase); } artinsoft+vbuc+v401042273+verified

public CodeExpression MapProperty(MemberMigrationContext context) { // 1. Identify the target control (the Label) var targetControl = context.SourceExpression; using System

CustomLabelMapper.cs

In VB6, ToolTipText is a native property of controls. In .NET Windows Forms, tooltips are managed by a separate ToolTip component dragged onto the form. The standard VBUC migration often maps this to a helper method or ignores it. We will develop a feature to inject the specific ToolTip setup logic into the Form_Load event. 1. Analysis of the Source (VB6) VB6 Code Example: The standard VBUC migration often maps this to

// 2. Access the parent form's components collection to add a ToolTip // We need a reference to a ToolTip object. // Ideally, the VBUC already added a ToolTip component to the form. // If not, we reference a helper or a global tool tip. // Strategy: Call a helper method that sets the tooltip. // This creates code like: Helper.SetToolTip(Label1, "Text"); var toolTipHelper = new CodeTypeReferenceExpression("MigrationHelpers.ToolTipHelper"); var value = context.ValueExpression;

Here is the design and implementation for this migration feature. Objective: Create a custom VBUC Extension Mapper to upgrade VB6 Label controls to .NET Label controls while injecting code to handle the ToolTipText property using a System.Windows.Forms.ToolTip component.