Cart(0 items)
Professional Windows PowerShell by Andrew Watt
BUY IT NEW
- $39.99 Online price
- $35.99 Member price Join Now
- Add to Wish List
FIND IT IN OUR STORES
Enter a zip code
(Paperback)
Write a Review- Publisher: Wiley, John & Sons, Incorporated
- Pub. Date: April 2007
- ISBN-13: 9780471946939
- Sales Rank: 169,037
- 552pp
- Series: Programmer to Programmer Ser.
Synopsis
• MSH is a new command-line shell for Microsoft server products, including the long-awaited Longhorn server, and will eventually ship with all major Microsoft products, making it the must-know technology
• MSH will replace current command lines in new Microsoft products and can be used to write shell scripts similar to those used with Unix and Linux
• Discusses how MSH enables all of the .NET Framework objects to become accessible via scripting, making it a very powerful addition to any developer's or administrator's toolbox
• Readers are guided through all the ins and outs of MSH and learn how to create powerful solutions; run scripts, programs, and commands; customize the MSH environment; handle data; manage files and disks; and script solutions and .NET objects
Biography
Andrew Watt (Aberdeen, Scotland, UK) was on the Windows PowerShell beta program for almost two years before product release. He is a Microsoft Most Valuable Professional, MVP, for SQL Server and is an independent consultant and experienced computer book author. He wrote his first programs in BASIC and 6502 Assembler in 1984 while researching his doctoral thesis.
He is a regular contributor to the Windows PowerShell newsgroup, microsoft.public.windows.powershell, and can be contacted by email at SVGDeveloper@aol.com.
From the Publisher
• MSH is a new command-line shell for Microsoft server products, including the long-awaited Longhorn server, and will eventually ship with all major Microsoft products, making it the must-know technology
• MSH will replace current command lines in new Microsoft products and can be used to write shell scripts similar to those used with Unix and Linux
• Discusses how MSH enables all of the .NET Framework objects to become accessible via scripting, making it a very powerful addition to any developer's or administrator's toolbox
• Readers are guided through all the ins and outs of MSH and learn how to create powerful solutions; run scripts, programs, and commands; customize the MSH environment; handle data; manage files and disks; and script solutions and .NET objects
Product Details
- ISBN:
0471946931
- ISBN-13: 9780471946939
- Format: Paperback, 552pp
- Publisher: Wiley, John & Sons, Incorporated
- Pub. Date: April 2007
- Sales Rank: 169,037
- Series: Programmer to Programmer Ser.
Table of Contents
Introduction xv
Acknowledgments xx
Finding Your Way Around Windows PowerShell 1
Getting Started with Windows PowerShell 3
Installing Windows PowerShell 3
Installing .NET Framework 2.0 4
Installing Windows PowerShell 7
Starting and Stopping PowerShell 8
Starting PowerShell 8
Exiting PowerShell 10
Startup Options 10
Finding Available Commands 11
Getting Help 14
Basic Housekeeping 17
Case Insensitivity 18
What You Get in PowerShell 19
Interactive Command Shell 19
Cmdlets 20
Scripting Language 21
Summary 23
The Need for Windows PowerShell 25
Limitations of CMD.exe 27
Batch Files 28
Inconsistency of Implementation 28
Inability to Answer Questions 29
Lack of Integration with GUI Tools 29
The GUI Emphasis in Windows 29
Previous Attempted Solutions 29
Windows Script Host 30
WindowsManagement Instrumentation 30
Summary 31
The Windows PowerShell Approach 33
A New Architecture 33
.NET Framework-Based Architecture 34
Object-Based Architecture 35
A New Cross-Tool Approach 38
GUI Shell (MMC Layered over PowerShell) 39
Command Line 39
Command Scripting 41
COM Scripting 43
Namespaces as Drives 45
File System Provider 47
Registry 47
Aliases 48
Variables 49
Active Directory 50
Certificates 51
Extensibility and Backward Compatibility 51
Aliases 51
Use Existing Utilities 53
Use Familiar Commands 55
Long Term Roadmap: Complete Coverage in 3 to 5 Years 55
COM Access 56
WMI Access 56
.NET Class Access 56
Object-Based Approach in PowerShell 56
Object-Based Pipelines 56
A Consistent Verb-Noun Naming Scheme 57
Coping with a Diverse World 58
Upgrade Path to C# 58
Working with Errors 58
Debugging in PowerShell 59
Additional PowerShell Features 59
Extended Wildcards 59
Automatic Variables 60
Summary 62
Using the Interactive Shell 63
Windows PowerShell's Two Command Line Parsing Approaches 63
Expression Mode Examples 65
Command Mode Examples 66
Mixing Expressions and Commands 69
Exploring a Windows System with Windows PowerShell 69
Finding Running Processes 69
Filtering Processes Using where-object 71
Filtering Processes Using Wildcards 72
Finding Out about Services 73
Finding Running Services 74
Finding Other Windows PowerShell Commands 75
Using Abbreviated Commands 76
Command Completion 76
Aliases 77
Working with Object Pipelines 78
Sequences of Commands 78
Filtering Using where-object 79
Sorting 81
Grouping 83
Pros and Cons of Verbosity 85
Interactive 85
Stored Commands 87
Summary 87
Using Snapins, Startup Files, and Preferences 89
Startup 89
Snapins 90
Profiles 97
Profile.ps1 98
Aliases 100
The export-alias Cmdlet 105
The get-alias Cmdlet 107
The import-alias Cmdlet 108
The new-alias Cmdlet 108
The set-alias Cmdlet 109
The Help Alias 111
Command Completion 112
Prompts 113
Preference Variables 115
Summary 116
Parameters 117
Using Parameters 118
Finding Parameters for a Cmdlet 121
Named Parameters 124
Wildcards in Parameter Values 125
Positional Parameters 127
Common Parameters 132
Using Variables as Parameters 133
Summary 135
Filtering and Formatting Output 137
Using the where-object Cmdlet 137
Simple Filtering 138
Using Multiple Tests 140
Using Parameters to where-object 142
The where-object Operators 144
Using the select-object Cmdlet 144
Selecting Properties 145
Expanding Properties 146
Selecting Unique Values 147
First and Last 148
Default Formatting 151
Using the format-table Cmdlet 155
Using the property Parameter 156
Using the autosize Parameter 157
Hiding Table Headers 158
Grouping Output 158
Specifying Labels and Column Widths 159
Using the format-list Cmdlet 161
Using the update-formatdata and update-typedata Cmdlets 162
Summary 163
Using Trusting Operations 165
Look Before You Leap 166
Using the remove-item Cmdlet 166
Using the whatif Parameter 175
Using the stop-process Cmdlet 175
Using the stop-service Cmdlet 178
Using the confirm Parameter 180
Using the verbose Parameter 181
Summary 182
Retrieving and Working with Data 183
Windows PowerShell Providers 183
Using the get-psdrive Cmdlet 184
Using the set-location Cmdlet 188
Using the passthru Parameter 190
Using the get-childitem Cmdlet 191
Using the get-location Cmdlet 194
Using the get-content Cmdlet 196
Using the measure-object Cmdlet 201
The new-item Cmdlet 203
The new-psdrive Cmdlet 204
Summary 205
Scripting with Windows PowerShell 207
Enabling Scripts on Your Machine 207
Using the read-host Cmdlet 212
Using the write-host Cmdlet 214
The Arithmetic Operators 218
Operator Precedence 219
The Assignment Operators 220
The Comparison Operators 222
The Logical Operators 225
The Unary Operators 226
Using the set-variable and Related Cmdlets 227
The set-variable Cmdlet 228
The new-variable Cmdlet 229
The get-variable Cmdlet 230
The clear-variable Cmdlet 231
The remove-variable Cmdlet 232
Summary 234
Additional Windows PowerShell Language Constructs 235
Arrays 235
Creating Typed Arrays 239
Modifying the Structure of Arrays 241
Working from the End of Arrays 245
Concatenating Arrays 248
Associative Arrays 249
Conditional Expressions 250
The if Statement 251
The switch Statement 254
Looping Constructs 256
The for Loop 256
The while Loop 258
The do/while Loop 259
The foreach Statement 260
Summary 262
Processing Text 263
The .NET String Class 263
Working with String Methods 267
Casting Strings to Other Classes 287
URI 287
Datetime 288
XML 289
Regex 289
Summary 291
COM Automation 293
Using the new-object Cmdlet 293
Working with Specific Applications 294
Working with Internet Explorer 294
Working with Windows Script Host 299
Working with Word 301
Working with Excel 302
Accessing Data in an Access Database 303
Working with a Network Share 305
Using Synthetic Types 306
Summary 308
Working with .NET 309
Windows PowerShell and the .NET Framework 309
Creating .NET Objects 311
The new-object Cmdlet 311
Other Techniques to Create New Objects 317
Inspecting Properties and Methods 320
Using the get-member Cmdlet 320
Using .NET Reflection 324
Using the GetMembers() Method 324
Using the GetMember() Method 326
Using the GetMethods() Method 328
Using the GetMethod() Method 329
Using the GetProperties() Method 330
Using the GetProperty() Method 331
Using System.Type Members 333
Summary 334
Putting Windows PowerShell to Work 335
Using Windows PowerShell Tools for Discovery 337
Exploring System State 338
Using the get-location Cmdlet 338
Handling Errors 345
Namespaces 346
PowerShell Aliases 346
PowerShell Functions and Filters 349
PowerShell Variables 350
Exploring the Environment Variables 351
Exploring the Current Application Domain 353
Exploring Services 357
Using the get-service Cmdlet 358
Using the new-service Cmdlet 360
Using the restart-service Cmdlet 361
Using the set-service Cmdlet 362
Using the start-service Cmdlet 362
Using the stop-service Cmdlet 363
Using the suspend-service Cmdlet 364
Summary 365
Security 367
Minimizing the Default Risk 368
The Certificate Namespace 374
Signed Scripts 376
Creating a Certificate 376
The set-authenticodesignature Cmdlet 377
The get-authenticodesignature Cmdlet 379
Summary 379
Working with Errors and Exceptions 381
Errors in PowerShell 381
{dollar}Error 383
Using Error-Related variables 388
Using the {dollar}ErrorView variable 389
Using the {dollar}ErrorActionPreference variable 390
Trap Statement 392
Using Common Parameters 397
Using the ErrorAction Parameter 397
Using the ErrorVariable Parameter 399
The write-error Cmdlet 400
Summary 401
Debugging 403
Handling Syntax Errors 403
The set-PSDebug Cmdlet 408
The write-debug Cmdlet 413
Tracing 418
The trace-command Cmdlet 419
The set-tracesource Cmdlet 422
The get-tracesource Cmdlet 422
Summary 423
Working with the File System 425
Path Names in Windows PowerShell 426
Fully Qualified Path Names 427
Relative Path Names 430
Path Names and Running Commands 431
Simple Tasks with Folders and Files 434
Finding the drives on a system 434
Finding Folders and Files 434
Finding File Characteristics 436
Exploring Files Using the select-object Cmdlet 439
Finding Hidden Files 442
Tab Completion 443
Redirection 445
Creating Custom Drives 447
Cmdlets for File Actions 449
Using the out-file Cmdlet 449
Using Cmdlets to Work with Paths 450
Summary 453
Working with the Registry 455
Introduction to the Registry 455
Exploring the Registry Using Windows PowerShell 458
Selecting a Hive 458
Navigating to a Desired Key 459
Changing the Registry 461
Summary 464
Working with Environment Variables 465
Environment Variables Overview 465
The Environment Command Shell Provider 468
Exploring Environment Variables 470
Modifying Environment Variables 471
Summary 473
Language Reference 475
Working with Logs 477
Event Log Basics 477
The get-eventlog Cmdlet 480
Summary 494
Working with WMI 495
Introducing Windows Management Instrumentation 496
Managed Resources 496
WMI Infrastructure 497
CIM Object Manager 498
The CIM Repository 499
WMI Consumers 499
WMI Tools 499
Using the get-wmiobject Cmdlet 502
Finding WMI Classes and Members 506
Exploring a Windows System 509
Characterizing the CPU 509
Finding Memory 510
Exploring Services 512
Exploring Remote Machines 513
Summary 514
Index 515
Acknowledgments xx
Finding Your Way Around Windows PowerShell 1
Getting Started with Windows PowerShell 3
Installing Windows PowerShell 3
Installing .NET Framework 2.0 4
Installing Windows PowerShell 7
Starting and Stopping PowerShell 8
Starting PowerShell 8
Exiting PowerShell 10
Startup Options 10
Finding Available Commands 11
Getting Help 14
Basic Housekeeping 17
Case Insensitivity 18
What You Get in PowerShell 19
Interactive Command Shell 19
Cmdlets 20
Scripting Language 21
Summary 23
The Need for Windows PowerShell 25
Limitations of CMD.exe 27
Batch Files 28
Inconsistency of Implementation 28
Inability to Answer Questions 29
Lack of Integration with GUI Tools 29
The GUI Emphasis in Windows 29
Previous Attempted Solutions 29
Windows Script Host 30
WindowsManagement Instrumentation 30
Summary 31
The Windows PowerShell Approach 33
A New Architecture 33
.NET Framework-Based Architecture 34
Object-Based Architecture 35
A New Cross-Tool Approach 38
GUI Shell (MMC Layered over PowerShell) 39
Command Line 39
Command Scripting 41
COM Scripting 43
Namespaces as Drives 45
File System Provider 47
Registry 47
Aliases 48
Variables 49
Active Directory 50
Certificates 51
Extensibility and Backward Compatibility 51
Aliases 51
Use Existing Utilities 53
Use Familiar Commands 55
Long Term Roadmap: Complete Coverage in 3 to 5 Years 55
COM Access 56
WMI Access 56
.NET Class Access 56
Object-Based Approach in PowerShell 56
Object-Based Pipelines 56
A Consistent Verb-Noun Naming Scheme 57
Coping with a Diverse World 58
Upgrade Path to C# 58
Working with Errors 58
Debugging in PowerShell 59
Additional PowerShell Features 59
Extended Wildcards 59
Automatic Variables 60
Summary 62
Using the Interactive Shell 63
Windows PowerShell's Two Command Line Parsing Approaches 63
Expression Mode Examples 65
Command Mode Examples 66
Mixing Expressions and Commands 69
Exploring a Windows System with Windows PowerShell 69
Finding Running Processes 69
Filtering Processes Using where-object 71
Filtering Processes Using Wildcards 72
Finding Out about Services 73
Finding Running Services 74
Finding Other Windows PowerShell Commands 75
Using Abbreviated Commands 76
Command Completion 76
Aliases 77
Working with Object Pipelines 78
Sequences of Commands 78
Filtering Using where-object 79
Sorting 81
Grouping 83
Pros and Cons of Verbosity 85
Interactive 85
Stored Commands 87
Summary 87
Using Snapins, Startup Files, and Preferences 89
Startup 89
Snapins 90
Profiles 97
Profile.ps1 98
Aliases 100
The export-alias Cmdlet 105
The get-alias Cmdlet 107
The import-alias Cmdlet 108
The new-alias Cmdlet 108
The set-alias Cmdlet 109
The Help Alias 111
Command Completion 112
Prompts 113
Preference Variables 115
Summary 116
Parameters 117
Using Parameters 118
Finding Parameters for a Cmdlet 121
Named Parameters 124
Wildcards in Parameter Values 125
Positional Parameters 127
Common Parameters 132
Using Variables as Parameters 133
Summary 135
Filtering and Formatting Output 137
Using the where-object Cmdlet 137
Simple Filtering 138
Using Multiple Tests 140
Using Parameters to where-object 142
The where-object Operators 144
Using the select-object Cmdlet 144
Selecting Properties 145
Expanding Properties 146
Selecting Unique Values 147
First and Last 148
Default Formatting 151
Using the format-table Cmdlet 155
Using the property Parameter 156
Using the autosize Parameter 157
Hiding Table Headers 158
Grouping Output 158
Specifying Labels and Column Widths 159
Using the format-list Cmdlet 161
Using the update-formatdata and update-typedata Cmdlets 162
Summary 163
Using Trusting Operations 165
Look Before You Leap 166
Using the remove-item Cmdlet 166
Using the whatif Parameter 175
Using the stop-process Cmdlet 175
Using the stop-service Cmdlet 178
Using the confirm Parameter 180
Using the verbose Parameter 181
Summary 182
Retrieving and Working with Data 183
Windows PowerShell Providers 183
Using the get-psdrive Cmdlet 184
Using the set-location Cmdlet 188
Using the passthru Parameter 190
Using the get-childitem Cmdlet 191
Using the get-location Cmdlet 194
Using the get-content Cmdlet 196
Using the measure-object Cmdlet 201
The new-item Cmdlet 203
The new-psdrive Cmdlet 204
Summary 205
Scripting with Windows PowerShell 207
Enabling Scripts on Your Machine 207
Using the read-host Cmdlet 212
Using the write-host Cmdlet 214
The Arithmetic Operators 218
Operator Precedence 219
The Assignment Operators 220
The Comparison Operators 222
The Logical Operators 225
The Unary Operators 226
Using the set-variable and Related Cmdlets 227
The set-variable Cmdlet 228
The new-variable Cmdlet 229
The get-variable Cmdlet 230
The clear-variable Cmdlet 231
The remove-variable Cmdlet 232
Summary 234
Additional Windows PowerShell Language Constructs 235
Arrays 235
Creating Typed Arrays 239
Modifying the Structure of Arrays 241
Working from the End of Arrays 245
Concatenating Arrays 248
Associative Arrays 249
Conditional Expressions 250
The if Statement 251
The switch Statement 254
Looping Constructs 256
The for Loop 256
The while Loop 258
The do/while Loop 259
The foreach Statement 260
Summary 262
Processing Text 263
The .NET String Class 263
Working with String Methods 267
Casting Strings to Other Classes 287
URI 287
Datetime 288
XML 289
Regex 289
Summary 291
COM Automation 293
Using the new-object Cmdlet 293
Working with Specific Applications 294
Working with Internet Explorer 294
Working with Windows Script Host 299
Working with Word 301
Working with Excel 302
Accessing Data in an Access Database 303
Working with a Network Share 305
Using Synthetic Types 306
Summary 308
Working with .NET 309
Windows PowerShell and the .NET Framework 309
Creating .NET Objects 311
The new-object Cmdlet 311
Other Techniques to Create New Objects 317
Inspecting Properties and Methods 320
Using the get-member Cmdlet 320
Using .NET Reflection 324
Using the GetMembers() Method 324
Using the GetMember() Method 326
Using the GetMethods() Method 328
Using the GetMethod() Method 329
Using the GetProperties() Method 330
Using the GetProperty() Method 331
Using System.Type Members 333
Summary 334
Putting Windows PowerShell to Work 335
Using Windows PowerShell Tools for Discovery 337
Exploring System State 338
Using the get-location Cmdlet 338
Handling Errors 345
Namespaces 346
PowerShell Aliases 346
PowerShell Functions and Filters 349
PowerShell Variables 350
Exploring the Environment Variables 351
Exploring the Current Application Domain 353
Exploring Services 357
Using the get-service Cmdlet 358
Using the new-service Cmdlet 360
Using the restart-service Cmdlet 361
Using the set-service Cmdlet 362
Using the start-service Cmdlet 362
Using the stop-service Cmdlet 363
Using the suspend-service Cmdlet 364
Summary 365
Security 367
Minimizing the Default Risk 368
The Certificate Namespace 374
Signed Scripts 376
Creating a Certificate 376
The set-authenticodesignature Cmdlet 377
The get-authenticodesignature Cmdlet 379
Summary 379
Working with Errors and Exceptions 381
Errors in PowerShell 381
{dollar}Error 383
Using Error-Related variables 388
Using the {dollar}ErrorView variable 389
Using the {dollar}ErrorActionPreference variable 390
Trap Statement 392
Using Common Parameters 397
Using the ErrorAction Parameter 397
Using the ErrorVariable Parameter 399
The write-error Cmdlet 400
Summary 401
Debugging 403
Handling Syntax Errors 403
The set-PSDebug Cmdlet 408
The write-debug Cmdlet 413
Tracing 418
The trace-command Cmdlet 419
The set-tracesource Cmdlet 422
The get-tracesource Cmdlet 422
Summary 423
Working with the File System 425
Path Names in Windows PowerShell 426
Fully Qualified Path Names 427
Relative Path Names 430
Path Names and Running Commands 431
Simple Tasks with Folders and Files 434
Finding the drives on a system 434
Finding Folders and Files 434
Finding File Characteristics 436
Exploring Files Using the select-object Cmdlet 439
Finding Hidden Files 442
Tab Completion 443
Redirection 445
Creating Custom Drives 447
Cmdlets for File Actions 449
Using the out-file Cmdlet 449
Using Cmdlets to Work with Paths 450
Summary 453
Working with the Registry 455
Introduction to the Registry 455
Exploring the Registry Using Windows PowerShell 458
Selecting a Hive 458
Navigating to a Desired Key 459
Changing the Registry 461
Summary 464
Working with Environment Variables 465
Environment Variables Overview 465
The Environment Command Shell Provider 468
Exploring Environment Variables 470
Modifying Environment Variables 471
Summary 473
Language Reference 475
Working with Logs 477
Event Log Basics 477
The get-eventlog Cmdlet 480
Summary 494
Working with WMI 495
Introducing Windows Management Instrumentation 496
Managed Resources 496
WMI Infrastructure 497
CIM Object Manager 498
The CIM Repository 499
WMI Consumers 499
WMI Tools 499
Using the get-wmiobject Cmdlet 502
Finding WMI Classes and Members 506
Exploring a Windows System 509
Characterizing the CPU 509
Finding Memory 510
Exploring Services 512
Exploring Remote Machines 513
Summary 514
Index 515
Read a Sample Chapter
Professional Windows PowerShell
By Andrew Watt
John Wiley & Sons
Copyright © 2007 John Wiley & Sons, LtdAll right reserved.
ISBN: 978-0-471-94693-9
Chapter One
Getting Started with Windows PowerShell
If you are like me, then when you begin to look seriously at an interesting piece of software, you like to get your hands dirty and play with it from the beginning. In this chapter, I show you how to get started using Windows PowerShell, and I'll show you enough of the PowerShell commands to let you begin to find your way around effectively. In the rest of the book, I help you build on that initial knowledge so that you can use PowerShell for a wide range of useful tasks, depending on your requirements.
Windows PowerShell, as you probably already know, is Microsoft's new command shell and scripting language. It provides a command line environment for interactive exploration and administration of computers, and by storing and running Windows PowerShell commands in a script file, you can run scripts to carry out administrative tasks multiple times. Windows PowerShell differs in detail from existing command line environments on the Windows and Unix platforms, although it has similarities to past environments. In Chapter 3, in particular, Iexplain more about the PowerShell approach, although differences from existing command shells and scripting languages will emerge in every chapter.
Once you have had a brief taste of PowerShell, you will need to understand a little of the assumptions and approach that lie behind the design decisions that have made PowerShell the useful tool that it is. In Chapter 2, I step back from using the PowerShell command line and look at the strengths and deficiencies of some existing Microsoft approaches to system management and then, in Chapter 3, take a look at the philosophy and practical thought that lies behind the approach taken in Windows PowerShell.
Installing Windows PowerShell
Windows PowerShell depends on the presence of the .NET Framework 2.0. Before you install PowerShell, you need to be sure that you have the .NET Framework 2.0 installed.
Installing .NET Framework 2.0
At the time of writing, the 32-bit version of the .NET Framework 2.0 runtime is available for downloading from www.microsoft.com/downloads/details.aspx?FamilyID=0856eacb-4362-4b0d-8edd-aab15c5e04f5&displaylang=en.
If you are using 64-bit Itanium processors, download the .NET Framework 2.0 runtime from www.microsoft.com/downloads/details.aspx?familyid=53C2548B-BEC7-4AB4-8CBE-33E07CFC83A7&displaylang=en. Windows PowerShell is only available on Windows Server 2003 for Itanium processors.
If you are using AMD 64-bit processors, download the runtime from www.microsoft.com/downloads/ info.aspx?na=47&p=3&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=F4DD601B-1B88-47A3-BDC1-79AFA79F6FB0&u=details.aspx%3ffamilyid%3dB44A0000-ACF8-4FA1-AFFB-40E78D 0788B00%26displaylang%3den.
If you are unsure whether or not you have .NET Framework 2.0 installed, navigate to C:\Windows\ Microsoft.NET\Framework (if necessary substitute another drive letter if your system drive is not drive C:). In that folder you will find folders that contain the versions of the .NET Framework that are installed on your machine. If you see a folder named v2.0.50727, then you have the .NET Framework 2.0 installed. The .NET Framework 2.0 SDK, which you can download separately, is useful as a source of information on .NET 2.0 classes that you can use with PowerShell.
Figure 1-2 shows the appearance of the Framework folder on a clean install of Windows 2003 Service Pack 1 after the .NET Framework 2.0 runtime has been installed.
You don't need to delete the v1.0.3705 or v1.1.4322 folders. In fact, you are likely to cause problems for applications that need earlier versions of the .NET Framework if you delete those folders. The .NET Framework 2.0 is designed to run side by side with .NET Framework 1.0 and 1.1.
To install the .NET Framework 2.0, follow these steps.
1. Navigate in Windows Explorer to the folder where you downloaded the installer, dotnetfx.exe.
2. Double-click the installer. On the splash screen that opens, click Next.
3. On the EULA screen, accept the license agreement and click Install.
4. The installer then proceeds to install the .NET Framework 2.0, as shown in Figure 1-3.
5. When the installation has completed successfully, you should see a screen similar to Figure 1-4.
6. If you have Internet connectivity, click the Product Support Center link shown in Figure 1-4 to check for any updates.
Once you have installed the .NET Framework 2.0, you can then install Windows PowerShell.
Installing Windows PowerShell
To install Windows PowerShell on a 32-bit system, follow these steps. If you are installing it on a 64-bit system, the installer filename will differ.
1. Double-click the .exe installer file appropriate for the version of Windows PowerShell you want to install. The initial screen of the installation wizard, similar to the one shown in Figure 1-5, is displayed.
2. Click Next.
3. Accept the license agreement and click Next.
4. If you are installing on drive C: on a 32-bit system, the default install location is C:\Windows\System32\windowspowershell\v1.0.
5. When the installation has completed successfully you will see a screen similar to Figure 1-6.
6. Click Finish.
Starting and Stopping PowerShell
Once you have installed Windows PowerShell, you have several options for starting it.
Starting PowerShell
To start PowerShell without using any profile file to customize its behavior, open a command window (On Windows 2003, select Start -> All Programs -> Accessories -> Command Prompt), then type:
%SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe -NoProfile
After a short pause, the Windows PowerShell prompt should appear (see Figure 1-7).
If you are still using a Release Candidate and attempt to start PowerShell by simply typing PowerShell .exe at the command shell prompt, you may see the error message shown in Figure 1-8. To fix that, update to the final release version.
Alternatively, you can start PowerShell by selecting Start -> All Programs -> Windows PowerShell 1.0 -> Windows PowerShell (see Figure 1-9).
Because of security concerns about previous Microsoft scripting technologies, the default setting of Windows PowerShell is that scripting is locked down. Specifically, when Windows PowerShell starts, it does not attempt to run profile files (which are PowerShell scripts) that contain various settings controlling how PowerShell should run. Whichever way you start PowerShell initially, you will probably later want to enable scripts. To do that, you use the set-executionpolicy cmdlet. Type:
set-executionpolicy -ExecutionPolicy "RemoteSigned"
and you will be able to run locally created scripts without signing them. I cover execution policy in more detail in Chapter 10.
There are several additional options for starting PowerShell, and I will briefly describe all of those - after I show you how to stop PowerShell.
Exiting PowerShell
To stop PowerShell, simply type the following at the PowerShell command line:
Exit
and you are returned to the CMD.exe command prompt (assuming that you started PowerShell from the CMD.exe prompt). If you started PowerShell using Start -> All Programs -> Windows PowerShell 1.0 -> Windows PowerShell, the PowerShell window closes.
You can't use "quit" to exit PowerShell. It just causes an error message to be displayed.
Startup Options
You have several options for how you start PowerShell. These are listed and explained in the following table. On the command line, each parameter name is preceded by a minus sign.
To view information about all help options, type:
%SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe -Help
or:
%SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe -?
or:
%SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe /?
at the command line. Each of those commands will cause the information, part of which is shown in Figure 1-10, to be displayed.
Notice that there are sets of parameters that you can use with PowerShell.exe. You can combine parameters only in the ways shown in Figure 1-10.
The preceding commands give you help on how to start Windows PowerShell. Once you start PowerShell, you also need to know where to find help on individual PowerShell commands. As a first step, you need to be able to find out what commands are available to you.
Individual PowerShell commands are small and granular. As a result, they are called cmdlets (pronounced "commandlets").
Finding Available Commands
In this section, I will show you a few commonly used commands and show you how to explore the PowerShell cmdlets to see what PowerShell commands are available on your system. The get-command cmdlet allows you to explore the commands available to you in Windows PowerShell.
The simplest, but not the most useful, way to use the get-command cmdlet is simply to type:
get-command
at the PowerShell command line. Several screens of command names scroll past when you do this - there are a lot of cmdlets in PowerShell. It's more useful to view the information one screen at a time. You achieve that by typing:
get-command | More
at the PowerShell command line. The result is similar to that shown in Figure 1-11. If you run that command and carefully read the available commands, you will get some idea of the scope of functionality that PowerShell allows you to control and manage.
To view another screen of commands, press the spacebar once. Repeat this to view each additional screen of commands.
PowerShell commands are formed of a verb, followed by a hyphen (or minus sign), followed by a noun. The get-command cmdlet illustrates the structure. The verb "get" is followed by a hyphen, which is followed by a noun "command." PowerShell uses the singular form of the noun, even when, as is often the case, you want to find multiple items that satisfy your requirements. Thus, you might use get-process to get all the processes running on a system, as opposed to get-processes.
You can use wildcards to focus your search for the relevant command. For example, to find all commands that use the get verb, use the following command:
get-command get-*
or, the slightly tidier:
get-command get-* | More
The argument to the get-command cmdlet uses the * wildcard. The argument get-* finds any command whose name begins with get, a hyphen, and zero or more other characters. As you can see in Figure 1-12, there are many cmdlets that use the get verb.
Other verbs worth looking for include add, format, new, set, and write. To see a complete list of available verbs, type the following command:
get-command | group-object verb
Figure 1-13 shows the results. The preceding command uses a pipeline that consists of two steps. The first uses the get-command cmdlet to create objects representing all available commands. The second step uses the group-object cmdlet to group the results by the verb.
To find the nouns available in your installation of PowerShell, use the following command:
get-command | group-object noun
If you want to sort the nouns alphabetically use the following command:
get-command | group-object noun | sort-object name
You can also use the get-command cmdlet to explore in other ways. For example, suppose that you want to find all cmdlets that you can use to work with processes. The preceding command shows you that process is one of the nouns used in cmdlets. One way to display information about all cmdlets that operate on processes is to use the following command:
get-command *-process
Figure 1-14 shows you that there are only two cmdlets that you can use to work specifically with processes. As you construct pipelines with multiple steps, you have many other cmdlets available for use with process-related information.
You can adapt the preceding command to find cmdlets relevant to other nouns. For example, the command:
get-command *-service
will find all cmdlets that relate to services.
Getting Help
When you're using PowerShell, you need to be able to find out how to use commands that you are already aware of or that you find by using the techniques described in the previous section.
You use the get-help cmdlet to get help information about individual cmdlets. You can use the get- help cmdlet with or without parameters. Using the get-help cmdlet with no parameters displays abbreviated help information.
For example, to get help on the get-process cmdlet type either:
get-help get-process
or:
get-process -?
at the PowerShell command line.
The default behavior of the get-help cmdlet when providing help information about a specific command is to dump all the help text to the screen at once, causing anything that won't fit on one screen to scroll off the screen and out of sight. You may find it more useful to display the help information one screen at a time by using More:
get-help get-process | More
or:
get-process -? | More
You are likely to have the help function available to you. It behaves similarly to the get-help cmdlet, except that the help function displays the help information one screen at a time. To display the help information for the get-process cmdlet one screen at a time, you can type:
help get-process
Since that is a little shorter to type than the get-help syntax, you may find that it's more convenient.
PowerShell displays help information in a way similar to man in Unix. The help for each command or other piece of syntax is structured in the following sections:
Name - The name of the cmdlet Synopsis - A brief text description of the cmdlet Syntax - Demonstrates how the cmdlet can be used Detailed Description - A longer text description of the cmdlet Parameters - Provides detailed information about how to use each parameter Input Type - Specifies the type of the input object(s) Return Type - Specifies the type of the returned object Examples - Examples of how to use the cmdlet Related Links - Names of other cmdlets with related functionality Remarks - Information about using parameters with the cmdlet
For some commands, some sections may contain no help information.
When you use no parameter with the get-help cmdlet, you see the following sections of information:
Name Synopsis Syntax Detailed Description Related Links Remarks
If you use the -detailed parameter, for example:
get-help get-process -detailed
you see the following sections of help information:
Name Synopsis Syntax Detailed Description Parameters Examples Remarks
If you use the -full parameter, for example:
get-help get-process -full
you see the following sections of help information:
Name Synopsis Syntax Detailed Description Parameters Input Type Return Type Notes Examples Related Links
In addition to the built-in help about cmdlets, you can also access help about aspects of the PowerShell scripting language using the get-help cmdlet. If you don't know what help files on the language are available, use the command:
get-help about_* | more
to display them. Figure 1-15 shows one screen of results. This works, since each of these help files begins with about_.
An alternative way to explore the available help files for an install on 32-bit hardware is to open Windows Explorer, navigate to the folder C:\Windows\System32\WindowsPowerShell\v1.0, and look for text files whose name begins with about. If your system drive is not drive C: modify the path accordingly.
(Continues...)
Excerpted from Professional Windows PowerShell by Andrew Watt Copyright © 2007 by John Wiley & Sons, Ltd. Excerpted by permission.
All rights reserved. No part of this excerpt may be reproduced or reprinted without permission in writing from the publisher.
Excerpts are provided by Dial-A-Book Inc. solely for the personal use of visitors to this web site.
- Windows Powershell in ActionBruce Payette
- Linq in ActionSteve Eichert, Jim Wooley, Fabrice Marguerie
- Microsoft Mobile Development HandbookAndy Wigley, Peter Foot, Daniel Moth, Daniel Moth, Peter Foot
- Programming Collective Intelligence : Building Smart Web 2.0 ApplicationsToby Segaran
- Understanding IPv6Joseph Davies
loading...