Visual studio 2005 & Windows 7

Question

bokr66 0 Newbie Poster

15 Years Ago

Hi,

I have a problem with an VB aplication programmed in Visual studio 2005. Recently i was upgraded my computer with windows XP to Windows 7 Ultimate (fresh instalation). After that I made reinstallation Visual studio 2005 and service pack 1 for Vista/win7. My problem now is when I run my old VB project (made by same version VS2005 on XP), I can't see anything on form () of that application. I Can see my code in and everything is running well, only I can't do any changes on form (editin old or adding new components), because I see only a blank screen in file (see attached picture).

Can anyone tell me what's wrong or missing.

Thanks in advance,

Bojan

Dani AI

Generated 9 Months Ago

Good catch by — when the Designer shows a blank surface the problem is usually in how the designer-generated code and the user code are split, or a design-time error preventing the designer from creating the form instance. Visual Basic WinForms uses partial classes to keep generated layout code separate from user code; the designer expects those partial parts to match exactly (same type name/namespace) and to expose the generated InitializeComponent routine. (learn.microsoft.com)

Quick checklist to triage the problem (do these in order):

Confirm both files use the same fully qualified class and namespace and that each declaration is marked Partial.
Ensure the form constructor calls InitializeComponent() (the designer-generated initialization method) so controls get created at design time. Example:
```
Public Sub New()
  InitializeComponent()
End Sub
```
If InitializeComponent is missing or the constructor is wrong, the designer cannot render the form. (learn.microsoft.com)

Other common causes and checks:

Open the Output window before opening the Designer; design-time type‑load or missing‑assembly exceptions will appear there and explain why controls can’t be created (third‑party controls or broken references are frequent culprits).
Verify each .vb file’s Build Action is set to Compile in the Properties window; if the designer file isn’t compiled the designer won’t see the members. Finally, do a Clean + Rebuild and delete bin/obj if needed. (learn.microsoft.com)

Safe repair tips and best practice:

Back up files first. If Designer.vb was accidentally emptied or misplaced, recreate the Designer partial (or add a new form and copy only the generated InitializeComponent section into a .Designer.vb file). Avoid hand-editing designer code unless necessary; put custom logic only in Form1.vb. If the form still won’t open, remove third‑party controls temporarily to isolate the failure. (learn.microsoft.com)

If these checks don’t reveal the cause, include the Designer error text from the Output pane and the top lines of both Form1.vb and Form1.Designer.vb when asking for more help — that information usually identifies the mismatch or missing dependency quickly.

Reply to this topic

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.

bokr66 0 Newbie Poster · Answer 1 · 2010-10-08T16:29:25+00:00

I Solve my problem. I have my code written in file and nothing in Form1.vb. When I move (cut & paste) all code to , run debugging, right click on (in Solution explorer)
and point to view Designer the form appears in windov [Design].
That's what I want. Thank all, who trying to help me.
With Best Regards,
Bojan