lib is not working on my project

[UnluckyD]

I tried add this lib in my study project, but i failed. Just like my teamlead.

if file have extension .axaml - i can use names of UI items, but they equal null
if file have extension .xaml - i can't use it at all.

https://github.com/UnluckyD/NameGeneratorTest - my test project
https://github.com/SkillChat/SkillChat - big study project

[MarkusKgit]

It seems the lib is generating it's own InitializeComponent() method where the Controls are assigned. Since you also provided one, it gets used instead. The short term solution would be to delete your custom InitializeComponent method. But I think it is something that should be improved by the code gen side (if that's even possible)?

[worldbeater]

If you'd like to disable InitializeComponent method generation, just put the following code into your csproj file as documented here https://github.com/AvaloniaUI/Avalonia.NameGenerator#advanced-usage If you are using InitializeComponent mode, then make sure you are calling that method in your constructor before accessing the properties.

<PropertyGroup>
  <AvaloniaNameGeneratorBehavior>OnlyProperties</AvaloniaNameGeneratorBehavior>
</PropertyGroup>

Next, if for some reasons the refs aren't generated, please make sure you put the AdditionalFiles directive with a mask that includes your files into csproj, we are mentioning this here and that's super important
https://github.com/AvaloniaUI/Avalonia.NameGenerator#getting-started

[radiolondra]

e.g.
in my WindowsMain.axaml I have a <UserControl x:Name="Mainframe">....
if you try to get reference to that Mainframe directly, it'll be null.
Instead, in my WindowsMain.cs I added:
private UserControl mainframe;
and in the MainWindow ctor, after the InitializeComponents call:
mainframe = this.Get<UserControl>("Mainframe");

Now all references can be done using mainframe instead of Mainframe.
e.g. mainframe.Content = new MyControl();

[worldbeater]

The fix suggested at #69 (comment) worked, opened a PR with the fix in the repro repository https://github.com/UnluckyD/NameGeneratorTest/pull/1. So this means there was a bug in the provided repro. Planning to update the documentation in order to indicate that one should not keep their own InitializeComponent methods in their classes, as such methods override the generated partial InitializeComponent method. Closing the issue as resolved for now.

Please use Right click -> Go to -> Go to declaration or usages tool in the future. This might allow you to demystify the process of code generation a bit. Also, the relevant documentation sections might help:

• https://github.com/AvaloniaUI/Avalonia.NameGenerator#what-do-the-generated-sources-look-like
• https://github.com/AvaloniaUI/Avalonia.NameGenerator#advanced-usage

[IldarKhayrutdinov]

It doesn’t work for me either, a simple empty window. When edit and saving the form Avalonia Diagnostics window outputs:
18:55:45.964 [Error] No executable found

Visual Studio 2022 v17.3.0
SDK: 6.0.400
Project target: .Net 6.0

I tried recommendations from readme (including https://github.com/AvaloniaUI/Avalonia.NameGenerator#advanced-usage).
Maybe my project file is wrong.

Is it possible to enable diagnostic output? I tried to add the generator as project reference Avalonia.NameGenerator.csproj from sources, but I couldn't find a breakpoint that breaking executing.

[worldbeater]

@IldarKhayrutdinov could you upload a repro for us to look around and figure out what's going wrong there? Also in the dependents section on GitHub your can view sources of applications that are already using XamlNameReferenceGenerator in order to get started quickly: https://github.com/AvaloniaUI/Avalonia.NameGenerator/network/dependents
E.g. XAML file, code-behind file

Also referencing the project sources is a bit tricky, you have to do git submodule update --init --recursive after cloning the repository and then you have to add the <AdditionalFiles /> directive into your csproj file https://github.com/AvaloniaUI/Avalonia.NameGenerator#getting-started

[IldarKhayrutdinov]

@worldbeater thanks for advice, I'll analyze dependens, maybe it will help me. If it doesn't help after weekends I'll create a minimal reproduction project.

Also referencing the project sources is a bit tricky, you have to do git submodule update --init --recursive after cloning the repository and then you have to add the <AdditionalFiles /> directive into your csproj file https://github.com/AvaloniaUI/Avalonia.NameGenerator#getting-started

yes, I have performed these requirements, my local NameGenerator project builds successfully, AdditionalFiles also added for main project.

[IldarKhayrutdinov]

@worldbeater how do to run debugging of NameGenerator?

[IldarKhayrutdinov]

@worldbeater finally, I found the reason: if the project contains a form with xaml errors, the generator will not work for all forms of the project (incl valid ones). I'm in process of migrating from WPF.
Test project: AvaloniaApplication1.zip