cmdlet

I have searched for something similar and I keep running across the FTP download answers. This is helpful information, but ultimately proving to be difficult to translate. I have found a powershell script and it works, but I am wondering if it can be tweaked for my needs. I don't have much experience with powershell scripting, but I'm trying to learn. The need is this. I need to download and install a series of files to a remote machine, unattended. The files are distributed via email via tinyurls. I currently throw those into a .txt file, then have a powershell script read the list and

Given my research, I don't believe the following is easily accomplished, if at all. As a last resort, however, I figured I'd check here. In Powershell 2.0, I'd like a way to reduce the (annoyingly) long names of parameters to various cmdlets. I would like absolute control over what the shorthand version looks like. (As opposed to being a slave to whatever parameter abbreviation scheme PS uses.) So, for example, I'd like to be able to do something like this: # Command goes on this first line to alias "-ForegroundColor" to "-fg" # Command goes on this second line to alias "-BackgroundColor" to "

I'm having a problem to execute powershell commands from the C# application. I've found many things related to this issue, but none of them helped me to figured it out what might is going on. So I have this little test function: private void Button_Click_1(object sender, RoutedEventArgs e) { Runspace runspace = RunspaceFactory.CreateRunspace(); runspace.Open(); Pipeline pipeline = runspace.CreatePipeline(); pipeline.Commands.AddScript("msg * test"); pipeline.Invoke(); runspace.Close(); } The problem is that in some computers it works just fine, but in others I receive the message that "the

When calling a cmdlet, is it possible to expand the value of a powershell variable somehow so it acts as a parameter (with associated values) for the cmdlet? Here's an example of what I'm trying: $CREDENTIALED_SECTION = "-Username $USER_NAME -Password $PASSWORD" . . . Invoke-Sqlcmd -ServerInstance "$SERVER_NAME" -Query "$SQL_STATEMENT" "$CREDENTIALED_SECTION" -Database "$DATABASE" The problem comes when Invoke-Sqlcmd runs. It tells me that a positional parameter cannot be found that accepts "-Username my username -Password my password " So it's expanding the variable but not properly sending