Hey, Scripting Guy! Tell Me About PowerShell Community Extensions

re: Hey, Scripting Guy! Tell Me About PowerShell Community Extensions

TheHelpSeeker — Tue, 29 Jan 2013 23:02:46 GMT

This didn't work for me:

C:\> import-module PSCX

I had to get to the .psm1 file. Also, I had to create my Modules directory first: "C:\Documents and Settings\MyUsername\My Documents\WindowsPowerShell\Modules"

C:\> Import-Module Pscx-2.1.1\Pscx.psm1

re: Hey, Scripting Guy! Tell Me About PowerShell Community Extensions

Keith Hill — Tue, 21 Dec 2010 21:05:20 GMT

@Hak, generally quoting the argument containing the ';' will do the trick. However you also want PowerShell to expand the variable $stringwithsemi for you so you need to use double-quotes to do this (or in this case, no quotes at all) e.g.

.\foo.bat $stringwithsemi

Note that single-quotes in PowerShell does not expand variables. This is handy when you need to provide a literal string and you don't want to worry about PowerShell accidentally substituting something it shouldn't.

re: Hey, Scripting Guy! Tell Me About PowerShell Community Extensions

Hak — Fri, 13 Aug 2010 19:05:01 GMT

When a variable contains a semicolon, it looks like wrapping it up with a single quote won't work.

For example, $stringwithsemi = "1234;456"

.\somethingsomething.bat '$stringwithsemi'

in this case, the value passed in will be "$stringwithsemi" not "1234;456". In side of the batch file, use echo to print out the argument value.

any suggestions on how to pass in ";" to a batch file?