InitializeComponent() is not recognized in brand new Avalonia 11.0.4 projects

[dprevato]

Describe the bug
I just started a new project, using Avalonia, but I have the error "CS0103: The name InitializeComponent does not exist in the current context", in MainWindow.axaml.cs, without any code added from my part. All the required DLLs are present, I'm using Community.Toolkit.Mvvm v8.2.1. No idea about how to resolve the problem. Someone can help me?
To Reproduce
Steps to reproduce the behavior:

1. Create a new project, using the following settings:

• template "Avalonia .NET Core MVVM App"
• Framework ".NET 7.0"
• MVVM Toolkit "Community Toolkit", Avalonia Version "11.0.0-rc1"
• use compiled bindings

2. Build the brand new project; I see the preview of the MainWindow.
3. Open the file "MainWindow.xaml.cs: there is the error "Cannot resolve symbol 'InitializeComponent'". The message appears only as tooltip when I move the mouse cursor over the function call, but no error is listed in the Error List window.
4. I tried to update the nuget packages to the version 11.0.4, with no avail.

Expected behavior
I expect to have the method InitializeComponent resolved, so I can start to write my own code.

Desktop (please complete the following information):

• OS: Windows 11 Professional;
• Version 11.0.0-rc1 AND 11.0.4

[timunie]

rc1 is pretty outdated. Please update your templates to use latest version.

[timunie]

Let's make it a Q&A for now, as it's not reproducable using latest templates. Please upgrade and try again. If it still fails, file a minimal sample. Thx 🙏

[timunie]

@dprevato please attach the new project that doesn't work for you here for us to inspect.

[dprevato]

I created two projects, one using the command dotnet new avalonia.app, and the second using Visual Studio and the template "Avalonia .NET App" (that, I presume, is the same template). As you can see, the project created in command line works perfectly, the code generator produced the code for the method InitializeComponent. In the app created in Visual Studio, I have the error. The projects in the archive are exactly as they where created, I've not made any build, so you can test.
AvaloniaTests.zip

I have to stress that there is no code of mine, no XAML, not a single bit. One template works, the other not.

[timunie]

🤔
I took your sample, opened it and just hit [F5], nothing more. I get:

So I see no issue on my side. Files are generated as desired, see left tree. I'm out of ideas now. Sometimes VS is blocking source gen, as a file was marked as locked. You can try to clean generated files by forcing a deletion. See:

• Visual Studio does not reload source generator assemblies when they change on disk dotnet/roslyn#48083
• https://learn.microsoft.com/en-us/answers/questions/1184090/looking-for-assistance-clearing-the-cache-for-upda

[thevortexcloud]

Certainly sounds like a Visual Studio problem. Which would not surprise me. Visual Studio does have a habit of breaking in weird subtle ways.

You can try compiling it from the command line too to see if that can get around it as a work around for the moment.

[Erik-Egnatosyan]

I have the same issue. I'm using Rider and newest version of avalonia and .net 9 (i try on .net 8 and still doesn't work). I'm updating everything that's is possible and nothing has changed. I deleted the file bin, obj, temp etc. The problem is still here and seems its not the problem of IDE.

[dprevato]

I think exactly the same, now. I'll follow your advice, and create my templates from the command line. Thank you for the assistance :) Il giorno gio 28 set 2023 alle ore 11:13 thevortexcloud < ***@***.***> ha scritto:

…

Certainly sounds like a Visual Studio problem. Which would not surprise me. Visual Studio does have a habit of breaking in weird subtle ways. You can try compiling it from the command line too to see if that can get around it as a work around for the moment. — Reply to this email directly, view it on GitHub <#13035 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADJFWFJW7GQ27M6X6I7KCZLX4U5SHANCNFSM6AAAAAA5I7TPVM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[dprevato]

OK, I made some other tries, and I found that, with dotnet new, the template avalonia.app works fine, but the avalonia.mvvm one creates the error, like when I create the solution in Visual Studio. Pity. But this make me think that Visual Studio is not the one to blame, after all

[timunie]

@dprevato do you have the exact build number of your VS at hand probably?

/cc @Takoooooo if you have an idea.

[dprevato]

Yep. The Visual Studio Enterprise version is 17.7.4, build number 17.7.34031.279

[dprevato]

I'm continuing to study the problem, and I noticed that the InitializeComponent method is defined in the Core.Views.MainWindow.g.cs file, and not only that: if I hover the mouse over the call that doesn't resolve, here is the definition and the description, as they are found in the other self-generated partial class. At runtime the error disappears, therefore you can live without solving it; but, forgive me, I feel as if I were in front of a splendid, perfectly white wall (Avalonia), with a speck in the corner: no matter how much effort I make, the eye continually falls on the speck :)

[thevortexcloud]

So to be clear it builds fine? Because if it does I'm back to thinking it's a Visual Studio problem.

[dprevato]

It builds fine and execute fine; I also think that it is some problem in Visual Studio, which does not connect the two partial MainWindow classes at design-time but does so at runtime; but we know well that the most fascinating part of the job is solving bugs...

[kivikko]

Try removing a reference to the XamlNameReferenceGenerator from your project.

[zeke202207]

I also encountered the same problem. Is there a solution?thanks @dprevato

[workgroupengineering]

You've probably mixed up multiple different versions of avalonia. Open your csproj and check the Avalonia PackageReference versions. If you use third-party components, also check which version of Avalonia they depend on.

[thevortexcloud]

As mentioned previously the problem can be caused by several things. That said the most likely cause for existing apps is invalid XAML. It all gets fed into a source generator and if it can't be parsed the source generator will fail, resulting in that method not existing.

[dprevato]

As I said above, the workaround I found is simply ignore the error, as the project compiles and runs without problems. I know, it's not a solution, but one cannot remain forever stuck, if he can avoid it... :)

[zeke202207]

You are right, maybe I have a little OCD, this problem will always be a pimple in the heart. Thank you @dprevato , Thank you all!

[thevortexcloud]

The tl;dr for this thread is don't trust Visual Studio with build errors. It does weird things and it often lies. Always check the actual build output.

[chenjing1294]

@dprevato

[AnnDevNet]

A possible track, unless the correction comes from another of my modifications :-)

I had the same problem in Debug but not in Release so I deleted this line from the project
<PackageReference Condition="'$(Configuration)' == 'Debug'" Include="Avalonia.Diagnostics" Version="11.2.1" />
I rebuild everything in debug (and in release) and no more errors.
I put the line back in place for the Avalonia.Diagnostics package and rebuild everything, and still no errors.
I also checked that adding an x:Name in the xaml added a reference to the auto-generated .g.cs file, when saving the xaml.

[MAC293]

Hi guys!
Are you still encountering this issue since the last time?
Mine is a little bit different, I get a "Cannot resolve symbol InitializeComponent()". I'm on MVVM AvaloniaUI on VS2022 using NET 8.

It's pretty odd when I change the target framework to 9, the problem disappears, but if I reboot VS, the issue comes back. It's a temporary fix. I don't get it. Even though, it runs with no problems. However, when looking for a method of any control it becomes such a tedious task, the autocomplete is dead cause of this.

Is there a definitive solution?

Regards

[timunie]

this comes from the source generators most likely. Nothing we can do here I guess.

[MAC293]

What a bummer. I've seen guys having it working correctly. It all comes down to their configuration. It's so damn annoying.

Thanks, dude.