update url on a network storage / unc path

[hybridherbst]

This had been mentioned before but the issue seems to have been closed without resolution.
Local file system works well, but a properly configured UNC path (if I paste that path into explorer it works) never finds updates. Pretty annoying for local deployment.

The original issue is #730.

[Logikgate]

The last issue was resolved with resolution. The UNC path that was being used was incorrect, it needed two slashes at the beginning in order to be valid. Do you have two slashes and are they properly escaped?

[anaisbetts]

Are you ending the path with a slash? Explorer likes to do that but Squirrel probably doesn't

[LunNova]

This is still a problem.

A path like \\SERVER-NAME\share-name\folder\Releases should be fine.

[anaisbetts]

@nallar Yep. Are you passing a path to a Folder, or to a RELEASES file - it should be a path to a Folder

[LunNova]

It is a folder called Releases, which contains a file called RELEASES. This matches the structure in https://github.com/Squirrel/Squirrel.Windows/blob/master/docs/getting-started/2-packaging.md

[anaisbetts]

@nallar Sounds like you're doing things right, I'd debug through Squirrel.exe with the --update parameter set to see what's going on

[Slion]

Looks like I'm facing that same issue. Mine is looking like:

file://server/projects/My%20Project/

Tried both with and without trailing slash, none worked.
It throws a system exception saying the directory does not exist.

[Slion]

Interestingly while the file URL above does not work the corresponding Windows UNC path works just file:

\\server\projects\My Project

[Thieum]

@soraryu are you still experiencing this issue with the latest version of Squirrel?

[hybridherbst]

Haven't been able to test this and had to move on to other topics, sorry. Would be great if someone else could test.

[ussha109]

I am also facing the same issue. My UNC path looks like
\cubert\TestProject\Releases\
and it seems automatic update is not working.

[Thieum]

See also #488 #671 #1331 #1406
@ussha109 as a workaround try to robocopy/sync the remote folder to something local, make the releasify, then resync back to remote.

Considering some third parties dependencies don't play well with the network, it solved this issue for some of us.

[anaisbetts]

@ussha109 That is not a UNC path, you're missing a slash. File URLs aren't supported. Use a regular, correctly formatted UNC path