Closed HJLeee closed 8 months ago
good catch! Seems like this issue stems from the Safe Naming Rule of dotnet templating.
E.g, if user use My-App
as the name, the generated content will be as follows:
However, the tizen-manifest.xml
file doesn't recognize the names converted according to this rule.
@sung-su, @JoonghyunCho could you check and make sure the tizen-manifest.xml
file aligns with orginal name when it genereted?
Here are the options I can think of right now to fix the issue:
tizen-workload
, for exec
value.
: Looks most preferred, but not simple. More investigation is required for conditional template generation.<AssemblyName>TizenApp1</AssemblyName>
property in TizenApp1.csproj
to make the name of dll fit to the naming rule.
: Easy to apply, but then it is Tizen specific. Not sure if there could be the side effects.Let me more think about the solution.
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days
Please refer the following for reproduction.