Vista - which direction to go

Hello,

quick scenario: I have experience with batch files, vbscript/wsh, bash shell
scripting, and vb.net/c#.net programming. None of which do I do everyday.
Over the years I have used these things to accomplish tasks or solve
problems as needed. I am about to move into a position where automation in
general will be key. Server deployment will be the primary area utilizing
Windows Automated Deployment Services and later System Center Configuration
Manager. So its time for me to update myself on the options out there now
for scripting for deployment and ongoing administration purposes.

1) what to focus on first? stick with vbscript/WSH, pull in WMI when needed
or do I not bother refreshing and updating myself on that and go right to
powershell/WMI?

2) I've used Visual Studio 2005 for some app development and noticed it has
support for WSH projects which I assume means all the great features of that
IDE will be available for WSH projects such as autocompletion and
documentation with examples at your fingertips. I'm also assuming getting VS
2005 only for scripting may be overkill. What options are out there now as
far as code editors that may have similar features to VS 2005 only just for
scripting?

any information/recommendations would be appreciated. thanks.

Hi David,

Around a year ago I found myself in a similar situation as you
describe.

My advice would be to go 100% Powershell.

Every day I amaze myself with what can be done in Powershell. Stuff
that might have taken hundreds of lines to accomplish in VBScript can
be produced in moments -at the command line or as a script. Being
built on .NET it'll be around for a long time to come so represents a
good investment of your time and effort. The short term yield to your
learning investment is awesome.

There are now some super books available to help you get up to speed
as well as formal training offerings from the likes of Sapien
Technologies ( I'm REALLY looking forward to starting my 'Intermediate
Powershell' course in July!).

Check out "Powershell in Action" by Bruce Payette, "Powershell
Cookbook" by Lee Holmes as well as "Pro Windows Powershell" by Hristo
Deshev and not forgetting the "Powershell TFM" by Sapien. They're all
great.

There's absolutely brilliant support available here and no matter how
often I ask stupid questions or ask for clarification the experts,
often MVP's, never exhibit any sign of losing patience!! Well not yet
anyway.

As far as editors go, that seems to be quite a personal question and
never fails to get peoples blood pressure rising from what I can
tell!! But I'll give you my $00.02 worth.

PowerGUI is free and is a bloody brilliant code editor with a
fantastic debugger. It's a staple "use-it-every-day" tool for me now.
I really liked the trial of PrimalScript 2007 - it's a wonderful
environment and I can see why some ppl regard it as the best editor
out there. I believe that Sapien are working on an even better IDE
with yet more Powershell support. I'm really keen to see that when
it's ready!

Personally, I went for the Admin Script Editor and I simply could not
be happier. Writing Powershell scripts is an absolute JOY in this
product. It also allows me to incorporate Windows Forms and database
functionality without breaking sweat and the integrated Powershell
debugger is simply outstanding. Way too many amazing features to get
into here without sounding like I work for the company that makes it!!

I consider myself to be a very mediocre Powersheller, especially
compared to other ppl who post here. So if I can get good results then
ANYONE can. But beware, Powershell is highly addictive. Spend three
months getting into it then see if you can stop..

Best wishes,

Stuart

I would recommend a program called "PowerShell Plus".. its both an IDE
and an enhanced shell, giving you many of the features you are used to
on the unix platform, but extending it futher giving IDE like
"intellisense" at the command prompt, while also providing you with a
full IDE editor and the most extensive powershell debugger to date.
Additionally you could grab PowerShell Analyzer, which has a more IDE
feel - it hasn't really been worked on lately, but will soon be made
100% free, while PS+ has a trial for commercial use, but is free for non
commercial uses.


David wrote:

David wrote:It would seem to be important to understand what needs to be automated
in the longer run.

You can do lots of things with PowerShell.

For example, PowerShell has built-in support for XML files. This may
help you when working with the Server 2008 Server Manager from the
command-line.

I think with whatever amount of .NET development you have done (with C#
more than VB.NET), the transition to PowerShell will be that much easier.

Marco

--
Microsoft MVP - Windows PowerShell
http://www.microsoft.com/mvp

PowerGadgets MVP
http://www.powergadgets.com/mvp

Blog:
http://marcoshaw.blogspot.com

Editors - I use PowerGUI, Powershell+ and the graphical interface in
PowerShell v2 CTP

Beware that the PowerShell syntax is like C# - sort of. You will find
yourself stumbling over the differences

Where ever possible I would use PowerShell - it is Microsoft's automation
engine and it will be built into all major MS products plus a lot of third
party vendors are adopting it - Quest, Citrix, VMware & IBM etc

I would second the list of books that Kryten posted

There is a tremendous PowerShell community not just on this forum.

Go with PowerShell - it is the future
--
Richard Siddaway
All scripts are supplied "as is" and with no warranty
PowerShell MVP
Blog: http://richardsiddaway.spaces.live.com/
PowerShell User Group: http://www.get-psuguk.org.uk


"Marco Shaw [MVP]" wrote:

thank you all for the great information.
-David

"David" <nospam@xxxxxx> wrote in message
news:%23B2c5FAzIHA.2208@xxxxxx