Incorrect slashes used in "OpenVisualStudioFilesInternalViaDTE" causes DTE issues

Tested in Windows 10, using Unreal Engine version 4.16.3 and Visual Studio 2015.

When using a game project hosted on a network share such as

\Wts-5c2eafeab51\Shared\VehicleGame\Source\VehicleGame

“FVisualStudioSourceCodeAccessor::OpenVisualStudioFilesInternalViaDTE” gets reversed slashes, such as

//Wts-5c2eafeab51/Shared/VehicleGame/Source/VehicleGame

When the reversed slashes are used at

if ( SUCCEEDED(ItemOperations->OpenFile(COMStrFileName, COMStrKind, &Window)) )

The file opens, but the DTE document will be malformed. The malformed DTE document causes issues for our Visual Studio plugin, Visual Assist.

This is a Visual Studio bug, but if you would be so kind as to send the correct Windows network path style slashes we would be grateful.

The issues Chris alludes to prevent any extension to Visual Studio, including Visual Assist, from editing the shared document. When Visual Assist attempts to edit, Visual Studio displays the vague message: “The operation could not be completed. Unspecified error.”

The user’s workaround is to close the document and open it from within Visual Studio.

The UE4 editor could avoid the bug in Visual Studio, thereby preventing extensions from faltering, if the editor preserved the file name’s backslashes.