Here's how to list, start and stop Windows services on a remote computer using PowerShell:
# List all services on the remote computer
[System.ServiceProcess.ServiceController]::GetServices('10.123.123.125')
# Stop the service and wait for it to change status
$service = (new-object System.ServiceProcess.ServiceController('Service name','10.123.123.125'))
$service.WaitForStatus('Stopped',(new-timespan -seconds 5))
$service.Stop()
# Start the service again
$service.Start()
This can come in really handy in deployment scripts, etc.
(Parts of this post came from The PowerShell Guy).
/Emil
Update: In the earlier version of this post I used new-object every time I needed a reference to the service. That's not necessary, it's much prettier to use a variable for the reference, so I have now updated the code.
It's quite easy to load and use .Net assemblies in Windows PowerShell, which of course is one of the main selling points of the script language. In this post I'll show a few examples.
Listing all loaded assemblies:
GAC Version Location
--- ------- --------
True v2.0.50727 C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\mscorlib.dll
True v2.0.50727 C:\WINDOWS\assembly\GAC_MSIL\Microsoft.PowerShell.Conso...
True v2.0.50727 C:\WINDOWS\assembly\GAC_MSIL\System\2.0.0.0__b77a5c5619...
True v2.0.50727 C:\WINDOWS\assembly\GAC_MSIL\System.Management.Automati...
True v2.0.50727 C:\WINDOWS\assembly\GAC_MSIL\System.Configuration.Insta...
True v2.0.50727 C:\WINDOWS\assembly\GAC_MSIL\Microsoft.PowerShell.Comma...
True v2.0.50727 C:\WINDOWS\assembly\GAC_MSIL\Microsoft.PowerShell.Secur...
True v2.0.50727 C:\WINDOWS\assembly\GAC_MSIL\Microsoft.PowerShell.Comma...
True v2.0.50727 C:\WINDOWS\assembly\GAC_MSIL\System.Management\2.0.0.0_...
True v2.0.50727 C:\WINDOWS\assembly\GAC_MSIL\System.DirectoryServices\2...
True v2.0.50727 C:\WINDOWS\assembly\GAC_32\System.Data\2.0.0.0__b77a5c5...
True v2.0.50727 C:\WINDOWS\assembly\GAC_MSIL\System.Xml\2.0.0.0__b77a5c...
To load a new assembly, do the following:
When an assembly has been loaded, types and code in it can be used with the new-object Cmdlet, for example:
Kundnummer :
Kundnamn : Acme
Organisationsnummer :
KontaktpersonKund :
Referens :
Affärsnummer : 2323232
Fas :
Betalningsvillkor :
Status : None
Fakturaaddress :
Fakturor : {}
Id : 0
PS> $obj.Validate()
Exception calling "Validate" with "0" argument(s): "Affärsnummer: Felaktig data: Affärsnummer skall alltid vara 9 siffror"
At line:1 char:14
+ $obj.Validate( <<<<)
Pretty cool, huh? (BTW, Validate() is a method on the "Affär" class.)
Also note that some command completion works with imported types. For example, if I type "$obj." and then press TAB, then the console will cycle through the available members of the type in question.
There's more to write about this interesting subject, so more posts will come...
/Emil
I recently decided to start learning the (fairly) new Windows PowerShell script language and thought it would be useful to write down some of its pecularities. The list below is by no means complete, it's just my own notes when learning the language.
BTW, I'm quite impressed of the power of this script language and will be using it from now on instead of the good old CMD.EXE and BAT files. However, there is a learning curve involved and it's steeper than it could have been. The creators' idea of "elastic syntax" (you can write the same logic in many ways) doesn't exactly help... Thus there is a need for a reference like this one.
Here we go:
Setup
To allow script execution, do this:
Virtual drives
More things than files can be accessed using a file system-like method using the virtual drives mechanism.
Example:
Error handling
PowerShell has a quite powerful error handling arsenal.
Errors can be trapped:
trap { "Something bad happened: " + $_.Exception; break } 1/$null
The first example uses the $_ variable to access the ErrorRecord object of the current error, and the second example displays the underlying .Net exception (including call stack, etc).
The previous errors are stored in the $errors array.
Using the console
Display text in the console (and don't send it down the pipeline):
Send text to stderr:
Change the console prompt:
The prompt function should return a single string.
Special operators
# array with values 1 through 10
1..10
# read file (or variable) content. NB, no whitespace after "{"!
${c:\boot.ini}
# encapsulate in array if needed
@( "foobar" )
# initialize an empty array
$a = @()
# initialize an array with 1 element
$a = ,1
# initialize an array
$a = 1,2,3
# (assigns elements from the array to variables $b == 1, $c == 2,3)
$b,$c = $a
# retrieves values for index 0 and 2 from an array
$a[0,2]
# retrieves values for index 0 through 2 from an array
$a[0..2]
# expression sequence (all results is merged into an array)
"foo"; "bar"
# & - execute script block
$a = { Get-Process | Select -First 2 }
& $a
# . - same as &, but execute in current scope
$x = 2
. { $x = 3 }
$x # $x is now 3, if we used & instead it would still be 2
# % can be use as a shortcut for the Foreach-Object Cmdlet
1..5 | % { $_ * 3 }
# ? can be used as a syntax shortcut for the Where-Object Cmdlet
1..17 | ? { $_ % 2 -eq 0 }
Hash tables (object imitations)
# object property syntax
$user.FirstName = "Mary"
# array syntax
$user["FirstName"] = "Mary"
# all values from the hash table
$user.Values
# all keys from the hash table
$user.Keys
# all values from the hash table using an array as input
$user[$user.keys]
Constants
These are fairly self-explanatory:
Built-in variables
Pattern matching
Wildcard matching (true/false):
Regular expressions (true/false + matching results in $matches):
Output:
True
Name Value
---- -----
2 bar
1 foo
0 foo bar
Discarding output of a command
Any of the following will do the trick:
Conditional and looping statements
The switch statement is mighty cool:
That's it for now. I will probably extend this posting later as i discover more things that are difficult to remember...
/Emil
In later versions of NHibernate it's possible to separate NHibernate configuration from normal application configuration (which is normally done in App.config/Web.config) by using a separate file called hibernate.cfg.xml.
Works great, but there is one thing to keep in mind in ASP.Net applications, namely that it should be placed in the bin/ folder, not in the root folder fo the application! Took me quite some time to figure out! So if you have the same problem as me, just move it to that folder
/Emil
[powered by WordPress.]
jour·nal n. A personal record of occurrences, experiences, and reflections kept on a regular basis; a diary.
36 queries. 1.253 seconds