An Overview of Windows PowerShell 1.0 and .NET - Revision history

Neil: Text replacement - "" to "
"
2016-10-27T19:58:44Z
Text replacement - "<table border="0" cellspacing="0">" to "<table border="0" cellspacing="0" width="100%">"

← Older revision Revision as of 19:58, 27 October 2016
Line 1: Line 1:

−
<table border="0" cellspacing="0">
+
<table border="0" cellspacing="0" width="100%">

<tr>

<tr>

<td width="20%">[[Windows PowerShell 1.0 File Handling|Previous]]<td align="center">[[Windows PowerShell 1.0 Essentials|Table of Contents]]<td width="20%" align="right">[[Creating GUIs in Windows PowerShell 1.0 with WinForms|Next]]</td>

<td width="20%">[[Windows PowerShell 1.0 File Handling|Previous]]<td align="center">[[Windows PowerShell 1.0 Essentials|Table of Contents]]<td width="20%" align="right">[[Creating GUIs in Windows PowerShell 1.0 with WinForms|Next]]</td>

Neil: Text replacement - "" to "
"
2016-05-05T14:28:34Z
Text replacement - "<table border="0" cellspacing="0" width="100%">" to "<table border="0" cellspacing="0">"

← Older revision Revision as of 14:28, 5 May 2016
Line 1: Line 1:

−
<table border="0" cellspacing="0" width="100%">
+
<table border="0" cellspacing="0">

<tr>

<tr>

<td width="20%">[[Windows PowerShell 1.0 File Handling|Previous]]<td align="center">[[Windows PowerShell 1.0 Essentials|Table of Contents]]<td width="20%" align="right">[[Creating GUIs in Windows PowerShell 1.0 with WinForms|Next]]</td>

<td width="20%">[[Windows PowerShell 1.0 File Handling|Previous]]<td align="center">[[Windows PowerShell 1.0 Essentials|Table of Contents]]<td width="20%" align="right">[[Creating GUIs in Windows PowerShell 1.0 with WinForms|Next]]</td>

Neil: Text replacement - "BUY_WPS" to "powershell"

2016-02-01T21:12:12Z

Text replacement - "<google>BUY_WPS</google>" to "<htmlet>powershell</htmlet>"

Neil: Text replacement - "ADSDAQBOX_FLOW" to "adsdaqbox_flow"

2016-02-01T18:01:12Z

Text replacement - "<google>ADSDAQBOX_FLOW</google>" to "<htmlet>adsdaqbox_flow</htmlet>"

Neil at 17:25, 15 May 2009

2009-05-15T17:25:19Z

Neil at 13:51, 14 May 2009

2009-05-14T13:51:49Z

Neil: /* The Basics of .NET */

2009-03-18T18:52:06Z

‎The Basics of .NET

Neil at 19:44, 9 December 2008

2008-12-09T19:44:53Z

Neil: /* Instance Members and Properties */

2008-12-09T19:40:38Z

‎Instance Members and Properties

Neil: /* Instance Members and Properties */

2008-12-09T19:40:02Z

‎Instance Members and Properties

← Older revision		Revision as of 21:12, 1 February 2016
Line 8:		Line 8:


−	<~~google~~>~~BUY_WPS~~</~~google~~>	+	<htmlet>powershell</htmlet>

@@ Line 16: / Line 16: @@
 == The Basics of .NET ==
-<google>ADSDAQBOX_FLOW</google>
+<htmlet>adsdaqbox_flow</htmlet>
 .NET is a vast framework of libraries (also referred to as ''assemblies'') which provide application programming interfaces (APIs) designed to perform a wide range of application functions. For example, assemblies are provided specifically for graphical user interface creation, web application development, business process handling and database access (to name just a few). Microsoft has invested significant research and development into developing .NET to the extent that it is now one of the most comprehensive development frameworks available today.

@@ Line 144: / Line 144: @@
 == Listing the Methods and Properties of a .NET Class ==
-The .NET Framework is a vast collection of classes, methods and properties. As such there many resources both in print and on-line providing detailed .NET reference information. If all that is required, however, is a listing of the methods and properties available in a .NET class, this can be obtained from within the Windows PowerShell environment using the ''get-members'' cmdlet.
+The .NET Framework is a vast collection of classes, methods and properties. As such there are many resources both in print and on-line providing detailed .NET reference information. If all that is required, however, is a listing of the methods and properties available in a .NET class, this can be obtained from within the Windows PowerShell environment using the ''get-members'' cmdlet.
 To obtain a list of all instance methods and properties of a particular class, simply pipe it through to the ''get-members'' cmdlet as illustrated below:
@@ Line 213: / Line 213: @@
 UtcNow                Property   System.DateTime UtcNow {get;}
 </pre>

@@ Line 4: / Line 4: @@
 == The Basics of .NET ==
+<google>ADSDAQBOX_FLOW</google>
 .NET is a vast framework of libraries (also referred to as ''assemblies'') which provide application programming interfaces (APIs) designed to perform a wide range of application functions. For example, assemblies are provided specifically for graphical user interface creation, web application development, business process handling and database access (to name just a few). Microsoft has invested significant research and development into developing .NET to the extent that it is now one of the most comprehensive development frameworks available today.

@@ Line 1: / Line 1: @@
 The power of Windows PowerShell is enhanced significantly by the ability to access and utilize the .NET framework from within both the shell environment and PowerShell scripts. This means that if there is a requirement for which a Windows PowerShell cmdlet or construct is not available, there is a very good chance the behavior is available via .NET. For example, Windows PowerShell is a text based environment with no built in support for creating and displaying graphical user interfaces (GUIs). Through the use of .NET WinForms support, however, even the most complex of GUIs can be created quickly and easily from with Windows PowerShell.
-In this chapter of [[Windows PowerShell 1.0 Essentials]] the basics of using .NET within Windows PowerShell will be covered. In the next chapter, [[Designing GUIs in Windows PowerShell 1.0 with WinForms]], will cover creation of graphical user interfaces.
+In this chapter of [[Windows PowerShell 1.0 Essentials]] the basics of using .NET within Windows PowerShell will be covered. In the next chapter, [[Creating GUIs in Windows PowerShell 1.0 with WinForms]], will cover creation of graphical user interfaces.
 == The Basics of .NET ==

@@ Line 1: / Line 1: @@
-<table border="0" cellspacing="0">
+<table border="0" cellspacing="0" width="100%">
 <tr>
 <td width="20%">[[Windows PowerShell 1.0 File Handling|Previous]]<td align="center">[[Windows PowerShell 1.0 Essentials|Table of Contents]]<td width="20%" align="right">[[Creating GUIs in Windows PowerShell 1.0 with WinForms|Next]]</td>

← Older revision		Revision as of 13:51, 14 May 2009
Line 1:		Line 1:
		+	<table border="0" cellspacing="0" width="100%">
		+	<tr>
		+	<td width="20%">[[Windows PowerShell 1.0 File Handling\|Previous]]<td align="center">[[Windows PowerShell 1.0 Essentials\|Table of Contents]]<td width="20%" align="right">[[Creating GUIs in Windows PowerShell 1.0 with WinForms\|Next]]</td>
		+	<tr>
		+	<td width="20%">Windows PowerShell 1.0 File Handling<td align="center"><td width="20%" align="right">Creating GUIs in Windows PowerShell 1.0 with WinForms</td>
		+	</table>
		+	<hr>
		+
		+
		+	<google>BUY_WPS</google>
		+
		+
	The power of Windows PowerShell is enhanced significantly by the ability to access and utilize the .NET framework from within both the shell environment and PowerShell scripts. This means that if there is a requirement for which a Windows PowerShell cmdlet or construct is not available, there is a very good chance the behavior is available via .NET. For example, Windows PowerShell is a text based environment with no built in support for creating and displaying graphical user interfaces (GUIs). Through the use of .NET WinForms support, however, even the most complex of GUIs can be created quickly and easily from with Windows PowerShell.		The power of Windows PowerShell is enhanced significantly by the ability to access and utilize the .NET framework from within both the shell environment and PowerShell scripts. This means that if there is a requirement for which a Windows PowerShell cmdlet or construct is not available, there is a very good chance the behavior is available via .NET. For example, Windows PowerShell is a text based environment with no built in support for creating and displaying graphical user interfaces (GUIs). Through the use of .NET WinForms support, however, even the most complex of GUIs can be created quickly and easily from with Windows PowerShell.

@@ Line 121: / Line 121: @@
 $object.PropertyName
-$object.NropertyName = new_value
+$object.PropertyName = new_value
 For example, to create an instance of the ''[System.Net.WebClient]'' class, and then call an instance method on that object:

@@ Line 109: / Line 109: @@
 == Instance Members and Properties ==
-In the case of instance members, an instance of the class must first be created before the methods and properties of that class may be used from within PowerShell. The syntax for creating an instance of a class (also referred to as an ''object'') requires the use of the ''new-object'' cmdlet and is as follows:
+In the case of instance members, an instance of the class must first be created before the methods and properties of that class may be used from within PowerShell. The syntax for creating an instance of a class (also referred to as an ''object'') requires the use of the ''new-object'' cmdlet as illustrated below:
 ''$object'' = new-object ''classname''(''parameters'')