File names in extension can no longer contain spaces?

[jessehouwing]

It didn't use to be a problem when packaging extensions, but since 0.3.40 I'm getting the error below:

error: Part Name 'vsts-snyk/node_modules/snyk/Contributor Agreement.md' is invalid. Please check the following: 
error: 1. No whitespace or any of these characters: #^[]<>?
error: 2. Cannot end with a period.
error: 3. No percent-encoded / or \ characters. Additionally, % must be followed by two hex characters.
tfx failed with error: Error: C:\TFS\_W\3\s\node_modules\.bin\tfx.cmd failed with return code: 4294967295

Since I cannot enforce this kind of restriction on developers of 3rd party dependencies, it's a very inconvenient change.

[tomap]

Hi,

Could you please tell us if this check is here because of a limitation of VSIX or it's something that could be changed ?

Thank you

[rfennell]

Seeing the same issue, anyone ever get a fix or workaround for this issue?

[jessehouwing]

I worked around it by replacing all spaces in file names with and `_`, which was possible in my case.

…

On Jun 29, 2017 19:12, "Richard Fennell" ***@***.***> wrote: Seeing the same issue, anyone ever get a fix or workaround for this issue? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#174 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AD-uSxs1yDKuAuVMjT1d-ecEGDEF6bK_ks5sI9rmgaJpZM4K3iIc> .

[rfennell]

ouch, loads of .md documention files that come with the 3rd party packages, but i guess i can try that

[rfennell]

To get around this problem we have been running an in-line Powershell script prior to running the VSIX packaging step.

The code is as follows

dir -recurse | where {-Not $_.PsIscontainer -AND $_.name -match " "} | foreach { 
    $New=$_.name.Replace(" ","_")
    Rename-Item -path $_.Fullname -newname $New -passthru
}   

[TerrenceHuang]

same issue too

[simchev]

Issue still open?