- edited description
Error: Space and period in profile name
When loading up the Pro Tools PowerShell forms designer, it errors out because my profile has a space in it as well as a middle initial with a period contained in it. This should be an easy fix to just enclose the profile directory in quotes.
Visual Studio Code Version Info: Version: 1.31.1 (user setup) Commit: 1b8e8302e405050205e69b59abb3559592bb9e60 Date: 2019-02-12T02:20:54.427Z Electron: 3.1.2 Chrome: 66.0.3359.181 Node.js: 10.2.0 V8: 6.6.346.32 OS: Windows_NT x64 10.0.17763
When starting up Visual Studio code:
Import-Module C:\Users\Victor D. Villa.vscode\extensions\ironmansoftware.powershellprotools-4.1.8\out\PowerShellProTools.VSCode.psd1
Import-Module : A positional parameter cannot be found that accepts argument 'D.'.
At line:1 char:1
+ Import-Module C:\Users\Victor D. Villa.vscode\extensions\ironmansoft ...
+ ~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (:) [Import-Module], ParameterBindingException
+ FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.PowerShell.Commands.ImportModuleCommand
When loading up the form designer:
Import-Module c:\Users\Victor D. Villa.vscode\extensions\ironmansoftware.powershellprotools-4.1.8\out\PowerShellProTools.VSCode.psd1
Import-Module : A positional parameter cannot be found that accepts argument 'D.'.At line:1 char:1
+ Import-Module c:\Users\Victor D. Villa.vscode\extensions\ironmansoft ...+ ~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (:) [Import-Module], ParameterBindingException
+ FullyQualifiedErrorId : PositionalParameterNotFound,Microsoft.PowerShell.Commands.ImportModuleCommand
Comments (2)
-
reporter -
- changed status to resolved
Fixes
#81→ <<cset 25a393277148>>
- Log in to comment