Cant Execute a source generator on a file using TrySetAttributeAsync

[prabhav-mehra]

I have a extension which creates a xml file based on another xml file, in a different format. I see the button in menu etc, but the source generator on the file doesn't run. I took the code snippet from the "SingleFileSourceGenerator" example.

 [Command(PackageIds.MyCommand)]
  internal sealed class MyCommand : BaseCommand<MyCommand>
  {
      
      protected override Task InitializeCompletedAsync()
      {
          Command.Supported = false;
          return base.InitializeCompletedAsync();
      }

      protected override async Task ExecuteAsync(OleMenuCmdEventArgs e)
      {
          var file = await VS.Solutions.GetActiveItemAsync() as PhysicalFile;
        
          await file.TrySetAttributeAsync("custom tool", AndroidRestrictionGenerator.Name);
      }
  }

the file.TrySetAttributeAsync returns true and the file also exisits, I checked by getting the full path.

I came across the VSIXSynchronizer code which has a different way of doing this, which actually partially works for me. This is the code for that.

  public static async Task InitializeAsync(AsyncPackage package)
  {

      await ThreadHelper.JoinableTaskFactory.SwitchToMainThreadAsync();


      var dte = await package.GetServiceAsync(typeof(DTE)) as DTE2;
      Assumes.Present(dte);
    
      var commandService = await package.GetServiceAsync(typeof(IMenuCommandService)) as IMenuCommandService;
   
      Assumes.Present(commandService);
      var cmdId = new CommandID(PackageGuids.InsertGuid, PackageIds.MyCommand);

      var cmd = new OleMenuCommand((s, e) => { OnExecute(dte); }, cmdId)
      {

          // This will defer visibility control to the VisibilityConstraints section in the .vsct file
          //Supported = false
      };

      commandService.AddCommand(cmd);
 }

 private async static void OnExecute(DTE2 dte)
 {
           
      ThreadHelper.ThrowIfNotOnUIThread();

      ProjectItem item = dte.SelectedItems.Item(1).ProjectItem;
    
      var ext = Path.GetExtension(item?.FileNames[1] ?? "")?.ToLowerInvariant();

      if (_generators.TryGetValue(ext, out var generator))
      {
          
          item.Properties.Item("CustomTool").Value = generator;
      }
}

The above code works partially for me. If I set GetDefaultExtension() in my source generator as ".cs" it creates one file with correct xml (which is fine but ofcourse I need a .xml extension). When I change the extension to ".xml" it goes in an infinite loop of creating the files and creates the file with name {FileName}(1^n).xml. So if file file name is test.xml, it creates test1.xml, test11.xml, test111.xml and so on till I stop the program (this doesnt happen when I change the extension to .cs).

UPDATE:
I got the first example to work partially but I do see the multiple file being generated still. So it does create FileName}(1^n).xml with the newer code.