Wpf 'initializecomponent' is not declared.

Question

1.00/5 (1 vote)

See more:

Public Sub New() InitializeComponent() End Sub

I use VB.Net and WPF but code keeps getting the message

'InitializeComponent' is not declared.

I can't find anywhere why designer does this.

Thank you

What I have tried:

I have search on Google.
But I can't find .

Posted 14-May-24 8:36am

quator

Updated 14-May-24 10:53am

Dave Kreskowiak

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Pete O'Hanlon · Answer 1 · 2024-05-14T09:06:00

Solution 1

~~Just add a method to the class called InitializeComponent. That will do it~~.

As quator noted, this is code that has a special purpose. The way that WPF works is that the XAML is compiled down to code. Crucially, the code in your class is a partial class.

Reasons for the failure can include the XAML file not being the right resource type. Make sure it's set to Page, not Resource in the Build action. The commonest cause is that you have an incorrect x:Class definition so the compilation doesn't tie the partial classes together.

Posted 14-May-24 9:06am

Pete O'Hanlon

Updated 14-May-24 9:45am

v2

Comments

quator 14-May-24 15:23pm

This is not the correct answer, the rest of the program will not work as it should.

Pete O'Hanlon 14-May-24 15:34pm

You are, of course, correct. This is what happens when you answer a question from memory.

quator 14-May-24 15:29pm

InitializeComponent() is created by the designer, but that does not always go well. You have no influence on that. If you are lucky, you close visual studio and then start it again and those "red lines" are gone.