2,892 questions
Click “View Details”, investigate and show the details and try determining the problematic line of InitializeComponent.
Null reference when callling InitializeComponent
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(105.60000000000001, 62%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPT%3C/text%3E%3C/svg%3E)
Peter Toye
191
Reputation points
I have just converted a VB Windows Forms project from .NET 4.7 to .NET 5. When I try to run it I get a Null Reference exception on the call to InitializeComponent at the head of the call of New() to the main form - see the screen shot. This is odd because there's nothing to reference apart from Me, which has surely been instantiated by the time this call is made - certainly hovering the cursor over local field names gives a value.
It's possible that I've left something out of the project file when editing it, but I can't see what.
Developer technologies VB
Accepted answer
-
Viorel 122.5K Reputation points2021-05-16T17:49:28.083+00:00 -
Peter Toye 191 Reputation points
2021-05-17T08:14:12.023+00:00 @Viorel Thanks for the idea - but as I've written below, the error occurs when calling InitializeComponent, not within it. Here's a screenshot of the details - but they don't make much sense to me :(
The call stack is simply the line in the code of the call to InitializeComponent.
-
Viorel 122.5K Reputation points
2021-05-17T08:28:22.74+00:00 Did you investigate the full multi-line text of StackTrace?
-
Peter Toye 191 Reputation points
2021-05-17T10:04:00.11+00:00 @Viorel I see what you mean; the error seems to be in a completely different place from the exception. What a pain. I'll investigate the suspicious item, but you seem to have hit upon the way of finding the answer. Thanks.
-
Peter Toye 191 Reputation points
2021-05-17T11:05:01.647+00:00 @Viorel I've now identified the problem thanks to your help. If you post it as an answer I can accept it and you get brownie points.
-
Peter Toye 191 Reputation points
2021-05-17T14:17:15.147+00:00 @Viorel ops just realised that it was an answer - the 'Accept' was off the screen.
Sign in to comment -
1 additional answer
Sort by: Most helpful
-
Karen Payne MVP 35,586 Reputation points Volunteer Moderator2021-05-16T17:23:17.9+00:00 For a .NET 5 form, InitializeComponent is in the form designer file not in user code (when double clicking on the form)
-
Peter Toye 191 Reputation points
2021-05-17T08:08:26.197+00:00 @Karen Payne MVP Thanks. As it happens, I already knew that. My version of InitializeComponent is similar to yours.
The problem is that the error occurs on the call to InitializeComponent, not within it. I tried changing the call to Me.InitializeComponent but the same happens. And I can't see what Object the error message is referring to as, apart from Me, there isn't any reference to an object. If there was a problem with a component being initialised the error should be flagged on the relevant line in the xxxx.Designer.vb file - but it isn't!
Sign in to comment -