Derived symbol value is empty when it is in Symbol geneator

[chunyu3]

in dotnet 7.0.2, When we reference a derived symbol in a symbol generator, the generated symbol value does not contain the derived symbol.
run
dotnet new *** --ClientName test

The value of PackageName :
Actual: Package.
expected: Package.Test

It works fine in dotnet 3.1.

"symbols": {
"clientName": {
      "type": "parameter",
      "datatype": "text",
      "isRequired": true,
      "description": "client name"
    },
"ClientNameCapitalCase": {
      "type": "derived",
      "datatype": "text",
      "valueSource": "clientName",
      "valueTransform": "firstUpperCase",
      "replaces": "Template"
    },
"PackageName": {
      "type": "generated",
      "generator": "join",
      "parameters": {
        "symbols": [
          {
            "type": "const",
            "value": "Package"
          },
          {
            "type": "ref",
            "value": "ClientNameCapitalCase"
          }
        ],
        "separator": "."
      },
    },
}

[YuliiaKovalova]

Hi @chunyu3,

Thank you for reporting the bug.
We are investigating the issue.

[GangWang01]

It was reproduced with dotnet 7.0.2. Root cause is the wrong order processing generated symbol and computed symbol at

templating/src/Microsoft.TemplateEngine.Orchestrator.RunnableProjects/RunnableProjectGenerator.cs

Lines 376 to 387 in a51479c

	MacrosOperationConfig? macroProcessor = null;
	if (runConfig.GeneratedSymbolMacros != null)
	{
	macroProcessor = new MacrosOperationConfig();
	macroProcessor.ProcessMacros(environmentSettings, runConfig.GeneratedSymbolMacros, variableCollection);
	}
	if (runConfig.ComputedMacros != null)
	{
	macroProcessor ??= new MacrosOperationConfig();
	macroProcessor.ProcessMacros(environmentSettings, runConfig.ComputedMacros, variableCollection);
	}

. Release/7.0.3xx should also have this problem.

This issue was fixed in PR #5223 that refactored at

templating/src/Microsoft.TemplateEngine.Orchestrator.RunnableProjects/MacroProcessor.cs

Lines 27 to 79 in 3ea9033

	bool deterministicMode = IsDeterministicModeEnabled(environmentSettings);
	foreach (BaseMacroConfig config in runConfig.ComputedMacros)
	{
	try
	{
	if (deterministicMode)
	{
	config.EvaluateDeterministically(environmentSettings, variables);
	}
	else
	{
	config.Evaluate(environmentSettings, variables);
	}
	}
	catch (Exception ex)
	{
	throw new MacroProcessingException(config, ex);
	}
	}
	if (!runConfig.GeneratedSymbolMacros.Any())
	{
	return;
	}
	Dictionary<string, IGeneratedSymbolMacro> generatedSymbolMacros = environmentSettings.Components.OfType<IGeneratedSymbolMacro>().ToDictionary(m => m.Type, m => m);
	foreach (IGeneratedSymbolConfig config in runConfig.GeneratedSymbolMacros)
	{
	if (generatedSymbolMacros.TryGetValue(config.Type, out IGeneratedSymbolMacro generatedSymbolMacro))
	{
	try
	{
	if (deterministicMode && generatedSymbolMacro is IDeterministicModeMacro<IGeneratedSymbolConfig> deterministicMacro)
	{
	deterministicMacro.EvaluateDeterministically(environmentSettings, variables, config);
	}
	else
	{
	generatedSymbolMacro.Evaluate(environmentSettings, variables, config);
	}
	}
	//TemplateAuthoringException means that config was invalid, just pass it.
	catch (Exception ex) when (ex is not TemplateAuthoringException)
	{
	throw new MacroProcessingException(config, ex);
	}
	}
	else
	{
	environmentSettings.Host.Logger.LogWarning(LocalizableStrings.MacroProcessor_Warning_UnknownMacro, config.VariableName, config.Type);
	}
	}

. dotnet 8.0.100-preview.2 has the fix.

BTW, .NET 6.0 doesn't have this problem.

[YuliiaKovalova]

Hi @chunyu3,

Could you specify the urgency of this fix for your tasks? Do you have a workaround?

[chunyu3]

Thanks @YuliiaKovalova and @GangWang01 for the quick resolve. Yes, it will block our project to generate the correct project via template and it has current no workaround now.
@YuliiaKovalova , when can I get a release version contains this resolution? Thanks. And is it possible to release a hotfix for .Net 7?

[YuliiaKovalova]

Hi @chunyu3,

We are discussing possible solutions behind the scene. I will give you more information once know more.

[YuliiaKovalova]

Hi @chunyu3 ,

The issue is fixed for release/7.0.2xx.
Please expect to receive these changes with the next patch - preliminary in the middle of June.
Thank you for your patience!

Best Regards,
Yuliia Kovalova

[chunyu3]

7.0.2

Thanks for your help!