J
John Blight
I have a problem in matching Visio documents.
We may open a Visio document through a conventional drive-letter path, and
indentify that document in our object model through that path.
However, Visio's Document.FullName property may express that path
differently, e.g. if the document is in SharePoint, it will return an
http
refixed path.
I don't want to use the Visio object model to create document objects that
can be compared, as this would be too cumbersome in the context in which the
comparison is made.
Does anyone know the mechanism behind Visio's FullName property?
Alternatively, does anyone know of any file system methods of matching files
where the paths may be expressed differently? .NET's FileInfo objects seem to
be of little help here.
We may open a Visio document through a conventional drive-letter path, and
indentify that document in our object model through that path.
However, Visio's Document.FullName property may express that path
differently, e.g. if the document is in SharePoint, it will return an
http
refixed path.I don't want to use the Visio object model to create document objects that
can be compared, as this would be too cumbersome in the context in which the
comparison is made.
Does anyone know the mechanism behind Visio's FullName property?
Alternatively, does anyone know of any file system methods of matching files
where the paths may be expressed differently? .NET's FileInfo objects seem to
be of little help here.