To make the model independent of the platform on which it is deployed, we need a way to construct file paths in XSLT transformations. A function that inserts the appropriate path separator for the current platform would help achieve this.
I would rather see a function similar to Path.Combine. I think it provides more value (you don’t have to think about leading/trailing separator etc.).
Sure, that’s even better.
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.
Function documentation is here: