PowerShell 2 In Windows 7 Comes With A Windows Shell

by Jon Davis 1. September 2009 01:48

Here’s something I overlooked about Windows 7 RTM. Not only does it comes with PowerShell v2 (I didn’t overlook that) but it also comes with an “ISE”—an Integrated Shell Environment. The “ISE” gives you three “panes” or sub-windows to work with PowerShell from within a single containing window: an input console, an output console, and a syntax highlighting text editor for script editing and debugging.

image

It does let you specify a layout. However, firing this thing up I immediately felt like I was stuck in Windows Live applications’ CandyLand. It has a notably consumer feel, and I’m afraid that system administrators and developers will tend to shy away from it simply because of that. Why Microsoft didn’t just reuse their Visual Studio Integrated Shell is beyond me.

Nonetheless, this is a nice addition to the Windows 7 and PowerShell combination/suite and will no doubt prove to be very handy for those who want to casually tinker with PS scripting without several different windows open or dishing out dough for the basic functionality of a PS script debugger.

image
Another much wanted feature finally arrives: Remote PS Shells

 

I’m still eyeing PowerShell Plus, albeit just a tiny fraction of a hair less now because of this.

Paying Attention To DinnerNow.net - Microsoft Killer App Best Practices Tutorial for Everything .NET 3.0

by Jon Davis 31. July 2007 18:01

I've been noticing my RSS feeds to Channel9 plugging some "DinnerNow" thing that sounded like some third party company who was just sharing some architectural trick up their sleeve, so I kinda shrugged it off. After all, how many software tricks are up people's sleeves at sourceforge.net or elsewhere?

But being a big new fan of ARCast.TV podcasts, I came across the Architecture Overview and Workflow piece which I didn't realize until I started listening that it was Part 1 of the DinnerNow bits. Listening to it now, I am realizing that this is something rather special.

DinnerNow, which I've only just downloaded and haven't actually seen yet but I'm hearing these guys talk about it in the podcast, is apparently NOT a Starter Kit style mini-solution like IBuySpy was (which was a dorky little shopping cart web site starter kit that Microsoft hacked together in ASP.NET back in the v1.1 days as a proof of concept).

Rather, DinnerNow is a full-blown software sample of an online restaurant food ordering web service application, one that I had wanted to build commercially for years (along with a hundred other ideas I had), that is top-to-bottom, soup-to-nuts, thorough and complete implementation of the entire solution from the servers, the restaurants, the buyer, demonstrating all of the awesome components of the latest long-released .NET Framework technologies, including:

  • Windows Communication Foundation (WCF) on the restaurant and web server
  • Windows Workflow Foundation (WF) on the restaurant and web server
  • Windows Presentation Foundation (WPF) for the restaurant (kiosk @ kitchen)
  • ASP.NET AJAX 1.0 and JSON-based synchronization
  • CardSpace for user security
  • PowerShell for things like administrative querying
  • Microsoft Management Console (MMC) for administrative querying, graphically
  • Windows Mobile / .NET Compact Framework
  • Windows Management Instrumentation (WMI)

Ron Jacobs (the ARCast host) made a good introduction for this with a statement I agree with, something along the lines of, "As architects, what we often try to do is look at someone else's software that was written successfully," and learn and discover new and/or best practices for software from it. In fact, that's probably the most important task in the learning process. If learning how to learn is an essential thing to learn in software architecture, then learn this essential point, that both understanding new technology and discovering best practices is learned by seeing it for yourself.

Update: Ugh. With many technologies being features comes many prerequisites. I had all of the above, but the setup requires everything to be exact. In other words, start with a fresh Virtual Machine with Vista 32-bit, and add the prerequisites. XP? Screwed. Win2003? Screwed. 64-bit? Screwed. Orcas Beta 2 installed? Screwed. And so on the screwing goes. An optional Virtual PC download from MSDN premium downloads with everything installed would have been nice. And I'm not hearing anything from the CodePlex forum / Issue Tracker, not a peep from its "maintainers". I think this project was abandoned. What bad timing, to put it on ARCast.tv now...

Another update: Microsoft did post a refresh build for Visual Studio 2008 Beta 2. I noticed it on CodePlex and they also started replying (for a change) to the multiple discussion threads and Issue Tracker posts on CodePlex. Among those replies were comments about 64-bit support--not supported, by design [which I knew] but they said with workarounds [which I posted multiple reports about] a 64-bit OS target build should be possible. I saw all this a few days ago; should have posted this follow-up update earlier, seems a Microsoft employee posted a comment here first. (Sorry.)

With passion comes passionate resentment when things go wrong. It's a fair give and take; on the other hand, whatever.

PowerShell Community Extensions on x64

by Jon Davis 24. July 2007 21:39

I ran into this error after installing PowerShell Community Extensions on Windows Server 2003 R2 (64-bit):

    Cannot load Windows PowerShell snap-in [..] because of the following error:
    No Windows PowerShell Snap-ins are available for version 1. 			

This is one of the lamest error messages in recent history. The solution was found here: http://www.eggheadcafe.com/software/aspnet/30117657/powershell-on-64bit-serv.aspx

.. where I just swapped out the referenced DLL with C:\Program Files (x86)\PowerShell Community Extensions\Pscx.dll and C:\Program Files (x86)\PowerShell Community Extensions\Pscx.Core.dll.

    C:\> C:\Windows\Microsoft.NET\Framework64\v2.0.50727\installutil.exe 
         "C:\Program Files (x86)\PowerShell Community Extensions\Pscx.dll" 

In that directory I found the post-install .bat file that attempted to do this. Apparently, it failed.

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Tags:

Computers and Internet | Cool Tools


 

Powered by BlogEngine.NET 1.4.5.0
Theme by Mads Kristensen

About the author

Jon Davis (aka "stimpy77") has been a programmer, developer, and consultant for web and Windows software solutions professionally since 1997, with experience ranging from OS and hardware support to DHTML programming to IIS/ASP web apps to Java network programming to Visual Basic applications to C# desktop apps.
 
Software in all forms is also his sole hobby, whether playing PC games or tinkering with programming them. "I was playing Defender on the Commodore 64," he reminisces, "when I decided at the age of 12 or so that I want to be a computer programmer when I grow up."

Jon was previously employed as a senior .NET developer at a very well-known Internet services company whom you're more likely than not to have directly done business with. However, this blog and all of jondavis.net have no affiliation with, and are not representative of, his former employer in any way.

Contact Me 


Tag cloud

Calendar

<<  May 2018  >>
MoTuWeThFrSaSu
30123456
78910111213
14151617181920
21222324252627
28293031123
45678910

View posts in large calendar