MAUI Mac VS - Warning CS8785: Generator 'CodeBehindGenerator' failed - CS0103 Initialize component does not exist

Question

MAUI Mac VS - Warning CS8785: Generator 'CodeBehindGenerator' failed - CS0103 Initialize component does not exist

Leo Wagner de Souza 696

I have a MAUI app, that was migrated from Xamarin Forms some time ago.

The app builds for iOS and Android from the command line (Jenkins build).

The app builds for Android from a Windows machine.

Now, I'm using a MacBook Pro with VS for Mac as development environment.

However, when I try to build from Mac VS, I get the error:

CS0103: InitializeComponent does not exist in the current context.

I know that the MAUI InitializeComponent method is generated by MAUI source generator, so I looked in the logs, and found:

/Users/lsouza/Documents/Dev/AHT/windows/Aht.SMT.Mobile/Aht.SMT.Mobile.Maui/CSC: Warning CS8785: Generator 'CodeBehindGenerator' failed to generate source. It will not contribute to the output and compilation errors may occur as a result. Exception was of type 'NullReferenceException' with message 'Object reference not set to an instance of an object.' (CS8785) (Aht.SMT.Mobile.Maui)

A blank MAUI solution builds perfectly in Mac VS, but not this one.

Any ideas on how to solve this NullReferenceException on CodeBehindGenerator?

Wenyan Zhang (Shanghai Wicresoft Co,.Ltd.) 36,436 Reputation points Microsoft External Staff

2023-08-04T05:49:47.7333333+00:00
By searching the source code in the MAUI Repo, it's hard to determine which object is null and why this error occurs. For further investigation, there are several questions to ask for you:

Do you try to clean the bin/obj folder?

What the detailed VS version?

What's the detailed MAUI version?

You want to build your MAUI project on iOS platform via VS for Mac, right? Which iOS device are you running on?

How did you migrate the Xamarin.Forms project to MAUI? maybe with the .NET Upgrade Assistant? You could try to check if some namespaces haven't changed, see
Namespace changes.
Leo Wagner de Souza 696 Reputation points

2023-08-04T20:56:01.5533333+00:00

Hello @Wenyan Zhang (Shanghai Wicresoft Co,.Ltd.) !

The problem is solved. Another developer added a dependency to the project, but stored the source code in his personal Git account.

When I pulled the code from the company Git, this dependency was left out.

So, when the CodeBehindGenerator tried to parse the page XAML, it found this tags, which it could not resolve, throwing the null exception.

The strange thing is that it did not generate the InitializeComponent for any page, and not just to the page that used the broken XAML tag.

Fix the broken dependency fixed the CodeBehindGenerator and the InitializeComponent.

1 answer

Your answer

Wenyan Zhang (Shanghai Wicresoft Co,.Ltd.) 36,436 Reputation points Microsoft External Staff

2023-08-04T05:49:47.7333333+00:00

By searching the source code in the MAUI Repo, it's hard to determine which object is null and why this error occurs. For further investigation, there are several questions to ask for you:

Do you try to clean the bin/obj folder?

What the detailed VS version?

What's the detailed MAUI version?

You want to build your MAUI project on iOS platform via VS for Mac, right? Which iOS device are you running on?

How did you migrate the Xamarin.Forms project to MAUI? maybe with the .NET Upgrade Assistant? You could try to check if some namespaces haven't changed, see
Namespace changes.
Leo Wagner de Souza 696 Reputation points

2023-08-04T20:56:01.5533333+00:00

Hello @Wenyan Zhang (Shanghai Wicresoft Co,.Ltd.) !

The problem is solved. Another developer added a dependency to the project, but stored the source code in his personal Git account.

When I pulled the code from the company Git, this dependency was left out.

So, when the CodeBehindGenerator tried to parse the page XAML, it found this tags, which it could not resolve, throwing the null exception.

The strange thing is that it did not generate the InitializeComponent for any page, and not just to the page that used the broken XAML tag.

Fix the broken dependency fixed the CodeBehindGenerator and the InitializeComponent.

Answer 1

Leo Wagner de Souza 696

The problem is solved. Another developer added a dependency to the project, but stored the source code in his personal Git account.

When I pulled the code from the company Git, this dependency was left out.

So, when the CodeBehindGenerator tried to parse the page XAML, it found this tags, which it could not resolve, throwing the null exception.

The strange thing is that it did not generate the InitializeComponent for any page, and not just to the page that used the broken XAML tag.

Fix the broken dependency fixed the CodeBehindGenerator and the InitializeComponent.

Wenyan Zhang (Shanghai Wicresoft Co,.Ltd.) 36,436 Reputation points Microsoft External Staff

2023-08-07T03:40:39.7366667+00:00

Glad you solved the problem. Thanks for your sharing.

Share via

MAUI Mac VS - Warning CS8785: Generator 'CodeBehindGenerator' failed - CS0103 Initialize component does not exist

1 answer

Your answer