VB.NET项目编译后功能失效，控件与代码关联异常求助

Hey there, let’s work through this problem step by step— I’ve dealt with similar quirky form designer glitches before, so I think we can get this sorted out for you!

First: Fixing the Unchanged Form Icon #

The icon not updating after compilation is likely due to cached build files, an invalid icon format, or the way you modified the form. Here’s what to try:

• Verify your icon file: Make sure you’re using a valid .ico file with standard Windows sizes (16x16, 32x32, 48x48 pixels are mandatory for proper display). If you converted an image to ICO, use Paint’s "Save As" -> ICO format to ensure it’s compatible.
• Bypass the theme restriction without cutting containers: Instead of moving your container to another form, directly edit the form’s designer code:
  1. In the Solution Explorer, expand your form’s node (click the arrow next to the .vb file) to reveal the .Designer.vb file.
  2. Open it and look for a line like:

     Me.Icon = CType(resources.GetObject("$this.Icon"), System.Drawing.Icon)
     

  3. Replace it with either:
     • A direct path to your ICO file (ensure the file is set to "Copy to Output Directory" in its properties):

       Me.Icon = New System.Drawing.Icon("YourIcon.ico")
       

     • Or, if you added the icon to your project’s resources (right-click project -> Properties -> Resources -> Add Resource -> Add Existing File):

       Me.Icon = My.Resources.YourIconName
       

• Clean and rebuild your project: Old build caches often block visual changes from showing up. Go to Build -> Clean Solution, then Build -> Rebuild Solution. You can also manually delete the bin and obj folders in your project directory to clear all cached files.

Next: Fixing Control-Code Disassociation #

Cutting and pasting containers can break the hidden links between controls and your code (even if the control names look correct). Here’s how to fix it:

• Double-check control names: In the form designer, select each problematic control, open the Properties window, and confirm the (Name) property matches exactly what you’re using in your code (VB.NET is case-insensitive, but the designer relies on exact name matches under the hood).
• Repair the Designer file: Open the .Designer.vb file again and verify two things for each broken control:
  1. There’s a Friend WithEvents declaration for the control, e.g.:

     Friend WithEvents btnSubmit As System.Windows.Forms.Button
     

  2. In the InitializeComponent() method, there’s code to instantiate the control and add it to the container, e.g.:

     Me.btnSubmit = New System.Windows.Forms.Button()
     Me.YourContainerControl.Controls.Add(Me.btnSubmit)
     

  If either line is missing, add them manually (match the control type and name correctly).
• Quick re-bind trick: If editing the designer file feels overwhelming, delete the broken control, drag a new one onto the form, set its (Name) property to the original name, then re-link any event handlers (double-click the control to re-generate the event method, or select the existing method from the Events tab in Properties).

A Quick Tip for Future Changes #

Since you’re getting back into programming, try to avoid cutting entire containers between forms— it’s easy to corrupt the designer’s auto-generated code. For small tweaks like icons, using the resource system or direct designer code edits is far more reliable.

内容的提问来源于stack exchange，提问作者Y. gui