' Instead of: Me.Button1.Anchor = AnchorStyles.Top Or AnchorStyles.Right ' Use the VB6-compatible approach: Private Sub Form1_Load(sender As Object, e As EventArgs) Handles MyBase.Load ' This tells the migration runtime to emulate VB6's resize logic Me.VB6Anchor(Me.Button1) = "TopRight" Me.VB6Anchor(Me.TextBox1) = "TopLeftWidth" Me.VB6Anchor(Me.OKButton) = "BottomRight" End Sub
| VB6 Position | VB6Anchor String | Effect | |--------------|------------------|--------| | Top, Right-aligned | "TopRight" | Stays same distance from top & right edge | | Bottom, Left-aligned | "BottomLeft" | Stays same distance from bottom & left | | Fill width | "TopLeftWidth" | Top fixed, left fixed, width scales | | Fill all | "All" | Control resizes with form (like Dock=Fill ) | If you have 50+ forms, don’t edit each manually. Use the post-migration script: code architects vb migration partner
By a Code Architects Consultant
The standard .NET Anchor property behaves differently. Instead, use the Migration Partner’s interceptor: ' Instead of: Me
One of the most frustrating “death by a thousand cuts” issues in VB6 to VB.NET migration is . VB6’s default scaling mode ( Twips per pixel) and control anchoring behavior are fundamentally different from .NET’s Pixel -based, Anchor / Dock system. VB6’s default scaling mode ( Twips per pixel)