-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Get-InstallCommand - spaces in filename #11
Comments
It depends on how you defined the variable, did you surround it with single quotes? e.g. |
I don't define it, it's in the source code in the Get-InstallCommand function. And it takes the value from the SCCM application install command. |
Interesting :)
Maybe I’m not handling escapes chars very well. I’ll take a look, thank you
Sent from Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: Boss-man ***@***.***>
Sent: Monday, November 13, 2023 11:46:57 AM
To: byteben/Win32App-Migration-Tool ***@***.***>
Cc: Subscribed ***@***.***>
Subject: [byteben/Win32App-Migration-Tool] Get-InstallCommand - spaces in filename (Issue #11)
I have a $SetupFile variable as this: msiexec /i "Print Settings 1.0.1.msi" /q
The resulting $command is "1.0.1.msi", which is not right.
Don't know if spaces in the filename can be handled somehow.
—
Reply to this email directly, view it on GitHub<#11>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKSAHIEIVEOGYE7WPUQ3643YEICDDAVCNFSM6AAAAAA7JAQ35OVHI2DSMVQWIX3LMV43ASLTON2WKOZRHE4TANBYHEZTMNQ>.
You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Ben, you're splitting the $SetupFile line first by $InstallTech (.msi in this case) and then by a " " (space), that's why you end up with just "1.0.1.msi". |
Semi-confident this is now fixed in 2.0.19 branch @Boss-man |
I have a $SetupFile variable as this: msiexec /i "Print Settings 1.0.1.msi" /q
The resulting $command is "1.0.1.msi", which is not right.
Don't know if spaces in the filename can be handled somehow.
The text was updated successfully, but these errors were encountered: