Studio version: 23.10
When creating a project from a template that contains .cs classes referenced in .xaml’s, the .xaml’s are still referencing template name .Core assemblies, breaking all references.
Repro:
- Create a template with a custom class in a .cs file
- Create a workflow that uses that type (doesn’t matter if it’s an argument or variable)
- Create a new project from that template
- Observe that the workflow now contains missing type errors
- Observe that also:
a. All unknown types are shown as Strings
b. All arguments with unknown types are changed to Properties
Workaround:
Change assembly namespace mapping (xaml header), and assembly import references (assembly reference section) to the new project name.
Also:
Same thing happens on project rename.
If the user clicks yes on the prompt to auto-import namespaces, the action happens for whole project. This breaks all other workflows as well, unknowingly to the user (can be seen on commit).
Expected behavior:
Classes from template/on rename, should have assembly references automatically adjusted. Why? Because the generated assembly naming is not controlled by the user, and therefore the user should not be expected to fix it. Effectively it’s an internal implementation detail that is outside reasonable user control.