J
John Blight
Does anyone know the mechanism behind Visio's Document.FullName property?
It would help, when trying to match files, if I could employ the same method
that Visio does. I don't want to use Visio's object model, as there is too
much overhead in opening a document in Visio just to get that information.
For example, when a Visio document is opened from a SharePoint location via
a mapped drive, Visio's Document.FullName will return an HTTP-prefixed path.
In order to match files, I'm currently converting paths to UNC, but I wonder
if there is a method that's more consistent with Visio's method of
identifying files.
It would help, when trying to match files, if I could employ the same method
that Visio does. I don't want to use Visio's object model, as there is too
much overhead in opening a document in Visio just to get that information.
For example, when a Visio document is opened from a SharePoint location via
a mapped drive, Visio's Document.FullName will return an HTTP-prefixed path.
In order to match files, I'm currently converting paths to UNC, but I wonder
if there is a method that's more consistent with Visio's method of
identifying files.