PowerShelled

This blog has moved to http://ThePowerShellGuy.com Greetings /\/\o\/\/ $AtomFeed = ("Atom.xml")
$PreviousItems = (" Windows "Monad" Shell (MSH) Beta 3.1 "," scripting games Last Day MSH answers for event 7 a... "," Scripting Games almost over "," The Scripting Games Event 6 in MSH "," Scripting Games week 2 "," Monad Links "," MSH Concentration (scripting games part 4) "," scripting games part 3 "," 2006 Winter Scripting Games (part 2) "," Monad hosting "," ")

Monday, February 27, 2006

Windows "Monad" Shell (MSH) Beta 3.1

There is a new Monad beta,

Windows "Monad" Shell Beta 3.1 (for .NET Framework 2.0 RTM) x86 http://www.microsoft.com/downloads/details.aspx?FamilyID=239a1116-c0f5-4320-84fc-2ad625ebb910&DisplayLang=en4

Windows "Monad" Shell Beta 3.1 (for .NET Framework 2.0 RTM) AMD64 http://www.microsoft.com/downloads/details.aspx?FamilyID=24bace7a-253a-4794-bb4f-d92715cb0a68&DisplayLang=en4

I don't know what is new yet, the release notes are the same, I could not find the proposed namechanges e.g.:

· Combine-Path will be renamed to Join-Path
· Parse-Path will be renamed to Split-Path
· Match-String will be renamed to Select-String
· Time-Expression will be renamed to Measure-Command
· Write-Object will be renamed to Write-Output

but If I find out more I will let you know,

thanks to Jean for posting the links in the NG

gr /\/\o\/\/

posted by /\/\o\/\/

Comments:

Sung Meister

Difference was not so obvious.
1) Added
div.Section1 {page:Section1;}

2) - We improved the “type finding” by looking in the loaded assemblies instead of using the overload of Activator.CreateInstance that takes an assembly name. With this fix SimpleGenericsTypeConverter was created so that conversions like String to Microsoft.Exchange.Data.Unlimited`1[Microsoft.Exchange.Data.ByteQuantifiedSize] should work. Before this fix we failed to find Microsoft.Exchange.Data.SimpleGenericsTypeConverter (which was in a loaded assembly) and got an exception that was unhandled.

- Pipeline input fails to bind to pipeline enabled parameter:

Create a cmdlet that has 2 parameter sets with 3 parameters.
One parameter must take pipeline input
One parameter should take provider input: MshPath
One parameter must be shared or used in a parameter set with each of the first two parameters.
Run the cmdlet with the shared parameter and pipeline input.

RESULT:
The pipeline input parameter fails to bind

# posted by

Sung Meister : 11:16 PM

Archives

October 2005 November 2005 December 2005 January 2006 February 2006 March 2006 April 2006 May 2006 June 2006 July 2006 August 2006 September 2006 October 2006 November 2006 December 2006