Newbie advice appreciated

[Kryten]

Hi,
I was just beginning to dip my toes into the world of developing
Windows applications and scripts with
VBScript and Visual Basic 2005 Express when PowerShell came along and
completely blew me away with
it's object based functionality.

Been playing around and learning as much as I can about PoweShell
since then but two things still bug me:-

a) I still don't come close to understanding things like assembles,
classes, namespaces, voids and other .NET stuff.
I "get" properties, methods and enough of the object orientation to
get by but to get better and more creative with PowerShell I need to
plug up those holes.

b) PowerShell lacks an easy to use implementation of Windows.Forms and
it so happens that most of the applications that I think I could get
value out of writing would need a graphical front end.

Enter C# and MS Visual C# Express 2008

I've bought "Head First C#" by O'Reilly and working my way through it
but could anyone recommend a learning source for the items I mention
in a) that I don't understand?

Many thanks,

Stuart

 

[Nicholas Paldino [.NET/C# MVP]]

Kryten,

You can do a google search for ".NET tutorial" and you will probably
come up with a number of links that will help you understand the basics such
as classes, namespaces, void, etc, etc. Look for "C# tutorial" as well.

As for powershell lacking an easy to use implementation of Windows
Forms, it's not ^meant^ to use Windows Forms. As the name implies it is a
power "shell" which implies the command-line.

 

[Kryten]

You can do a google search for ".NET tutorial" and you will probably
come up with a number of links that will help you understand the basics such
as classes, namespaces, void, etc, etc. Look for "C# tutorial" as well.

Thanks Nicholas, I'll do that but wonder if there are any particularly
good books
on the subject too?

As for powershell lacking an easy to use implementation of Windows
Forms, it's not ^meant^ to use Windows Forms. As the name implies it is a
power "shell" which implies the command-line.

Yes, I understand this, perhaps I wrongly used the word "lacking" but
the fact is
when deploying large administrative scripts with numerous options and
possibilities for
user input a graphical interface is nice to have. I guess thats why
I'm now looking at trying
to get some C# skills,

Thanks again,
Stuart