DosTips.com

I'm having weird issue with "current directory" when the following hybrid batch is executed from directory containing opening square bracket in its name. When run e.g. from "te[]st" directory, the result of Get-Location is "C:\Windows\SysWOW64\WindowsPowerShell\v1.0" (I...

Ah, looks like I can answer myself - the brianddk 's method described in http://www.dostips.com/forum/viewtopic.php?p=45502#p45502 is the way. The problem I was having with this was that I did not get the idea properly - the whole point is that the PS code should be actually written as a function......

Okay, so this is simulating the param()... but how about actually having the param() fully functional... e.g. including parameter attribute and its arguments (like Mandatory, HelpMessage, ParameterSetName, etc.) or ability to define "switch" type parameters? I would really like to be able ...

<# : ------------ start batch part ------------ @echo off set PSModulePath=D:\Documents\WindowsPowerShell\Modules;%PSModulePath% :: PowerShell location set POWERSHELL=%windir%\system32\WindowsPowerShell\v1.0\powershell.exe :: 32-bit version needs to be used on 64-bit systems! if exist "%windir...

I tried various hybrid PS/BAT techniques described here, but I can't get the embedded PowerShell script to work properly with named parameters. I.e. that I could call my hybrid batch like e.g. foo.cmd -computerName MYHOMEPC -action MyAction If the PS code in foo.cmd declares parameters like param($c...