PowerShell: differenze tra le versioni

Versione delle 00:20, 6 apr 2007

Versione delle 10:38, 6 apr 2007

Riga 25:

Microsoft ha pubblicato la seconda [[Versione_beta|beta]] pubblica di "Monad" l'[[11 Settembre]] [[2005]], mentre la terza è stata rilasciata il [[10 Gennaio]] [[2006]].

Microsoft ha annunciato il [[25 Aprile]] [[2006]] che WSH avrebbe cambiato nome in Windows PowerShell, e sarebbe divenuta una parte significativa della loro offerta tecnologicadi strumenti di gestione del sistema

<ref name="powershell">{{cita web

|url=http://blogs.msdn.com/powershell/archive/2006/04/25/583344.aspx

|titletitolo=Windows PowerShell (Monad) Has Arrived

|yearanno=[[April 25]] [[2006]]

|accesso=26-04-2006

|lastcognome=Snover

|firstnome=Jeffrey

|workopera=Windows PowerShell team blog

|editore=MSDN

|lingua=Inglese

}}</ref>.

La prima release candidate di PowerShell è stata rilasciata contestualmente all'annuncio.

<!--

La seconda release candidate è stata rilasciata il [[26 Settembre]] [[2006]].

==Storia==

La versione 1.0 è stata rilasciata il [[14 Novembre]] [[2006]].

==Principi==

Microsoft announced on [[April 25]] [[2006]] that MSH was renamed to Windows PowerShell, positioning it as a significant part of their management technology offerings<ref name="powershell">{{cite web

|url=http://blogs.msdn.com/powershell/archive/2006/04/25/583344.aspx

|title=Windows PowerShell (Monad) Has Arrived

|year=[[April 25]] [[2006]]

|accessdate=2006-04-26

|last=Snover

|first=Jeffrey

|work=Windows PowerShell team blog

|publisher=MSDN

}}</ref>. Release Candidate 1 of PowerShell was released at the same time.

Il nome in codice di PowerShell, ''Monad'', proviene dalla [[monadologia]] di [[Gottfried Leibniz]], una filosofia in cui l'universo è composto da elementi fondamentali, le ''[[monadi]]'', disposti in una "[[armonia prestabilita]]". In maniera simile, PowerShell è la combinazione di compiti complessi e di una serie di componenti, le ''cmdlets'' (''command lets'',

Release Candidate 2 of PowerShell was released [[September 26]] [[2006]].

<!--

Windows PowerShell v1.0 was released to web (RTW) [[November 14]] [[2006]].

PowerShell's codename, ''Monad'', comes from [[Gottfried Leibniz]]'s [[monadology]], a philosophy in which the universe is a composite of fundamental elements called ''[[Monads]]'' that are integrated in a "[[pre-established harmony]]". Similarly, PowerShell is a composite of the complex tasks of a series of components. The components are special programs called ''cmdlets'' (pronounced ''command lets''), which are .NET classes designed to use the features of the environment. The key difference between the usual Unix approach and the PowerShell one is that rather than creating a "pipeline" based on ''textual'' input and output, PowerShell passes data between the various cmdlets as ''objects'' (structured data).

==Principi==

PowerShell's codename, ''Monad'', comes from [[Gottfried Leibniz]]'s [[monadology]], a philosophy in which the universe is a composite of fundamental elements called ''[[Monads]]'' that are integrated in a "[[pre-established harmony]]". Similarly, PowerShell is a composite of the complex tasks of a series of components. The components are special programs called ''cmdlets'' (pronounced ''command lets''), which are .NET classes designed to use the features of the environment. The key difference between the usual Unix approach and the PowerShell one is that rather than creating a "pipeline" based on ''textual'' input and output, PowerShell passes data between the various cmdlets as ''objects'' (structured data).

If accessed individually from the command line, a cmdlet's output will automatically be converted into text, but if its output is to be used by another cmdlet, it will be converted into whatever form of object is most appropriate for that cmdlet's input. This has the advantage of eliminating the need for the many text-processing utilities which are common in Unix pipelines, such as [[grep]] and [[awk]], as well as allowing things to be combined interactively, or in a scripting environment, which would otherwise require a more complex [[programming language]]. For instance, a listing of processes will consist not of text describing them, but objects representing them, so that methods can be called on those objects without explicit reference to any outside structure or [[library (computer science)|library]].