WE 2013.5 File to read not found or unreadable when using a networked solution

[v1nce]

I got a working scss (css/foo.scss) in a working solution (D:\My Documents\Visual Studio 2013\Projects\project)

When I open the solution as if it came from a network (\computername\D$\My Documents\Visual Studio 2013\Projects\project then sass compilation fails saying

Compilation Error occurred (see error list to navigate to the error location):
Error found:
Code: undefined Message: File to read not found or unreadable: (\computername\D$\My Documents\Visual Studio 2013\Projects\project\css\foo.scss

If I copy/paste the path in file browser then it opens flawlessly. AFAICT there's no problem with this file (read only, lock...)

VS 2013 update 4

[am11]

Under the hood libsass does not support reading the file from the network path (via HTTP[S] or FTP), unless we employee a custom importer: sass/libsass#1000. With node-sass wrapper around libsass (which WE2013 consumes), it is possible to implement custom importer as a JavaScript function: https://github.com/sass/node-sass/tree/47d6386/test/fixtures/extras, which can be then fed to node-sass options used by WE's Sass web-service.

If anyone wants to take a stab, I can help. But I have moved on to VS2015 and using raw node modules.

[umkasanki]

try https://www.npmjs.com/package/gulp-wait