Grrr 1.1 and Big Invaders

Home  >>  Announce  >>  Grrr 1.1 and Big Invaders

Grrr 1.1 and Big Invaders

On February 26, 2007, Posted by , In Announce,Cmdlets,Cool,Grrr,Invaders,PowerShell, With 11 Comments

So I’ve been spending a bit of time getting to grips with Cmdlets and resurrecting interest in PSInvaders using Grrr and now have something to post.

Grrr 1.1 is now Cmdlet based and comes as a Snap-In. The most obvious benefit from this is performance, as I can now present a playable version of PowerShell Big Invaders.

BigInvaders 1.1 in play

BigInvaders is one of the demo PowerShell scripts that makes use of the Grrr.

Download this prerelease version 1.1 of the Grrr snap-in.

Update: this should now install on Vista – thanks to Chris Warwick for pointing out some issues

There’s no installer (yet) so to get going, follow this instructions:

Unzip the archive where you want to use it and CD to the top level director where the README file is.

Type: ./installgrrr.ps1 -r

The -r switch forces it to re-register the snap-in if a (possibly) older version exists. It then adds the snap-in to the current shell.

From here you can CD into the demos directory and run any of the scripts. Each one shows a feature of Grrr, but perhaps the most interesting is in the biginvaders directory.

To run BigInvaders, you need to have a very large console. To achieve this you probably need to set the font size of your console window to 6×8.

If you want sound, you need to install DirectX DirectSound. More on why later.

It should work without, silently, but this hasn’t had much testing as all my XP boxes have it installed 🙂 If there are exceptions, start it with the -nosound switch.

Assuming all is well, type ./biginvaders.ps1 and you should see this title screen:

BigInvaders 1.1 intro screen

Hit ESC to quit or Space to play. In play, Space fires a missile and arrow keys move left and right. Hit F to toggle FPS display in the top-righthand corner.

The target FPS is 33. I achieve this easily on my MacPro, and my wife’s Dell (a core 1 duo, 1.66ghz) also just manages.

There are still a few snags to iron out here and I want to add proper PowerShell help and an installer, but it is functional.

I’ve learned a lot about C#, PowerShell SDK and .NET these last weeks and will write about my findings over the next days. It’s not all been rosy.

I’ll also be writing about the features of Grrr, and where I want to go with it.

That’s it for now.

11 Comments so far:

  1. Chris Warwick says:

    Cool!! Couple of issue tho’

    – The installer has a hardcoded path pointing to your C:\ drive. Fixed easily enough….

    – …but, the InstallUtil command fails on Vista with the following:

    System.InvalidOperationException: Unable to create an instance of the Soapyfrog.Grrr.Meta.GrrrSnapin installer type.
    The inner exception System.Reflection.TargetInvocationException was thrown with the following error message: Exception has been thrown by th
    e target of an invocation..
    The inner exception System.Security.SecurityException was thrown with the following error message: That assembly does not allow partially trusted callers..

    So, I can’t run it 🙁

  2. adrian says:

    Oh yea, sorry on h/c path 🙂

    Vista: I don’t have it, so can’t say why it behaves differently… anyone?

  3. adrian says:

    Had a thought… does the download need to be blessed, or otherwise approved, as Vista probably thinks it came from an untrusted source… XP had something along those lines for scripts.. an option on the file properties dialog box.

  4. Chris Warwick says:

    Good thinking, but just modified the dll and tried again – exactly the same result. A quick Google found this that looks like it might fix the problem?

    To solve this security exception I mark my assembly by using the AllowPartiallyTrustedCallersAttribute (APTCA)

    I used the AllowPartiallyTrustedCallersAttribute (APTCA) in the Assemblyinfo.vb file since my project was developed in VB.NET. You can add the attribute AllowPartiallyTrustedCallersAttribute in Assemblyinfo.cs for C# applications.

    Use the below code line in

    [assembly: AllowPartiallyTrustedCallers]

    Prior adding the AllowPartiallyTrustedCallers attribute you should check that you have imported the System.Security namespace

    Imports System.Security


    using System.Security


  5. […] And if you are into monad/powershell give a shot at Adrian’s implementation. […]

  6. zproxy says:

    Just to let you know I just implemented the same game in javascript.


  7. adrian says:

    Very nice. Always good to see Space Invaders alive and well in the world 🙂

  8. Marco Shaw says:

    Will you make the source available? Will you share more on your cmdlet development experience?

  9. adrian says:

    >Will you make the source available?

    Probably. I wanted to get the cmdlet help docs sorted out before releasing it.

    > Will you share more on your cmdlet development experience?

    Yes. I’ve been on holiday recently so PS1 has been rather low on my list of priorities 🙂

  10. says:

    Still planning on releasing the cmdlet source? Just taking a break for the Summer or is your “interest” in PowerShell completely gone?

  11. adrian says:

    I’d sort of forgotten about it. Sorry. I don’t need/use PS1 in my day to day work and have other priorities outside of work.

    I’ll package it up though and post shortly.