[CONNECT Update 5] UNC Path in Configuration File makes Customizing Tools Read-Only

_USTN_WORKSPACEROOT = //Server/Root/Bentley/CONNECT/$(_USTN_WORKSPACENAME)/

Using a UNC path in a workspace folder specification makes some tools read-only (see this post) when using the Customization dialog.  Changing to a mapped network drive letter enables editing...

# L:/ is a mapped Windows drive as //Server/Root/
_USTN_WORKSPACEROOT = L:/Bentley/CONNECT/$(_USTN_WORKSPACENAME)/

Bentley Systems: is that intentional?  If so, please clarify why using UNC paths in configuration variables doesn't work as we might reasonably expect. If not, please change the configuration file processor so that we can use UNC paths.

Parents Reply Children
No Data