Let me clarify what I have seen is the expression language is translated but even though it may point to a file path the external resources identify it as a content body and not a file path.
On Mon, Mar 3, 2025 at 5:54 PM Dan S <[email protected]> wrote: > Thanks for the response Dave. I do have a follow up question though. If > these two properties are collapsed into one which identifies external > resources, will that mean it can no longer support expression language? I > was under the impression one cannot have both. Currently the Config File > property descriptor supports expression language at the environment level. >
