Comments for Huddled Masses

Comment on Adventures getting MSBuild, TFS and SQL Server Data Tools to work together by Dew Drop – April 27, 2012 (#1,315) | Alvin Ashcraft's Morning Dew

Dew Drop – April 27, 2012 (#1,315) | Alvin Ashcraft's Morning Dew — Fri, 27 Apr 2012 12:40:09 +0000

[...] Adventures getting MSBuild, TFS and SQL Server Data Tools to work together (Joel ‘Jaykul’ Bennett) [...]

Comment on Scriptable SSH from PowerShell by Joel 'Jaykul' Bennett

Joel 'Jaykul' Bennett — Fri, 20 Apr 2012 04:56:26 +0000

Update: There’s now another SSH Library on CodePlex (SSH.NET), and Joakim Svendsen over at PowerShellAdmin.com has a PowerShell module using SSH.Net — you should check his out too, it even has an Enter-SshSession and the ability to Invoke-SshCommand across multiple Ssh Sessions!

Comment on PowerShell 3 – Finally on the DLR! by Joel 'Jaykul' Bennett

Joel 'Jaykul' Bennett — Fri, 03 Feb 2012 03:27:25 +0000

So, yeah … PowerShell still starts like a .Net app starts, so it’s slower to start than most scripting languages. And of course, since you can’t store the script pre-compiled, it has to be compiled on first run — which is kind-of a pain for startup scripts. My impression is that in some cases they’ll automatically cache scripts’ pre-compiled versions, but I’m not sure that’s true.

I’m really not sure how CAS applies. I do know that .Net 4 had better defaults for UNC paths, which is a relief, but I’m not a CAS expert.

Comment on PowerShell 3 – Finally on the DLR! by Joel 'Jaykul' Bennett

Joel 'Jaykul' Bennett — Fri, 03 Feb 2012 03:23:09 +0000

I should really stick in a toolbar … it’s textile, but to trigger syntax highlighting I use geshi, which means you have to tell it what language it is with a tag: <code lang="posh">

Comment on PowerShell 3 – Finally on the DLR! by Josh Einstein

Josh Einstein — Thu, 02 Feb 2012 15:59:40 +0000

Okay I have no idea what I am doing with this comment system. I meant to reply, and I tried both HTML and Markdown and can’t seem to format my code like you have.

Comment on PowerShell 3 – Finally on the DLR! by Josh Einstein

Josh Einstein — Thu, 02 Feb 2012 15:58:50 +0000

Ahh thanks, yeah seems like they might want to build in some special case logic for anything imeplementing IDynamicMetaObjectProvider so that it calls the GetDynamicMemberNames method.

In the meantime I used this as a workaround.

    function ConvertFrom-DictionaryObject {

        process {

            $Obj = New-Object PSObject 

            foreach ($Key in $_.Keys) {

                Add-Member -InputObject $Obj NoteProperty $Key $_[$Key]

            }

            $Obj

        }

    }

But then again doing this is basically the same situation we had in v2.

Comment on PowerShell 3 – Finally on the DLR! by Peter Kriegel

Peter Kriegel — Thu, 02 Feb 2012 08:12:08 +0000

Yeah! I have seen the presentation Video from Jeffrey Snover and Refaat Issa at the Build conference.
The say execution of code is up to 6* faster.

As a .NET Developer and Admin, I was crying all the time, about the One-way affair, between PowerShell and the .Net Framework. Because PowerShell takes all advantages of the Framework, but there is no backflow from PowerShell to the Framework (PS-Modules/Snapins as Classes into the Framework, to use it in C# or VB natively).
I am Happy to go a step forward in this relationship.

My credo is: PowerShell everywhere! (As a replacement for Kixtart, DOS, VBscript..)
If you want to use PowerShell for Logon scripts there is a Gap. One of the Arguments against PowerShell for this purpose is that PowerShell starts up to slow. How fast is that with V3 and a script?

So I see a need for precompiled scripts, to add more speed! What’s with that?

My next question which comes into mind is; which role plays the .NET Code Access Security in that game?
(I did not take knowledge of the new .NET 4 CAS)

Comment on PowerShell 3 – Finally on the DLR! by Joel 'Jaykul' Bennett

Joel 'Jaykul' Bennett — Wed, 01 Feb 2012 23:47:06 +0000

Ok, yeah, I came up with my own example, and … I guess this deserves it’s own blog post, but … it does work, mostly. It needs some help for Get-Member and maybe a format file though.

Add-Type -ReferencedAssemblies System.Core, Microsoft.CSharp @"

namespace Expando {

    using System;

    using System.Dynamic;

    using System.Management.Automation;

    [Cmdlet("Get", "Expando")]

    public class Test : Cmdlet {
        public static dynamic GetThing() { 

            dynamic expando = new ExpandoObject();

            // Adding New Members

            // properties, methods (and events?) can be added to instances of the ExpandoObject class.

            expando.FirstName = "Joel";

            expando.LastName = "Bennett";

            expando.GetFullName = (Func)(() => { 

                return String.Format("{0}, {1}",  expando.LastName, expando.FirstName); 

            });
            return expando;

        }
        protected override void ProcessRecord() {

            WriteObject( GetThing() );

        }

    }

}

"@

$thing = [Expando.Test]::GetThing() 
# Thinks that $thing is a KeyValuePair

$thing | Get-Member
# Shows that $thing is really an ExpandoObject:

Get-Member -InputObject $thing

But even though it’s an ExpandoObject, you can’t figure out what properties are on it without looking at the key/value stuff. Once you know, you can access them, although the methods need .Invoke()ing:

<#C:\PS #>⁠⁠⁠ $thing["FirstName"]

Joel
<#C:\PS #>⁠⁠⁠ $thing.FirstName

Joel
<#C:\PS #>⁠⁠⁠ ⁠⁠$thing.FirstName = "Katrina"
<#C:\PS #>⁠⁠⁠ $thing.GetFullName.Invoke()

Bennett, Katrina

Comment on PowerShell 3 – Finally on the DLR! by Josh Einstein

Josh Einstein — Wed, 01 Feb 2012 21:43:56 +0000

Sure:

Add-Type-TypeDefinition @"

using System;

using System.Collections.Generic;

using System.Dynamic;

public static class DynamicMaker {

    public static dynamic MakeDynamic(string propertyName, object value) {

        IDictionary obj = new ExpandoObject();

        obj[propertyName] = value;

        return obj;

    }

}

"@
$Obj = [DynamicMaker]::MakeDynamic("Color", [ConsoleColor]::Blue)
@($Obj) | Format-List

I would expect the result to be:

Color: Blue

Instead it is:

Key: Color
Value: Blue

Treating ExpandoObject as a dictionary and not a dynamic object with a single Color property.

Comment on PowerShell 3 – Finally on the DLR! by Joel 'Jaykul' Bennett

Joel 'Jaykul' Bennett — Wed, 01 Feb 2012 21:29:02 +0000

Do you have a quick example?