/\\/\\o\\/\\/
Mon Feb 27 12:36:04 CST 2006
I'm a MVP op Monad (Windows Admin Frameworks)
I'm mostly in microsoft.public.windows.server.scripting , but I came
across the, I think interesting discussion , on this thread.
I would like to note for who is interested in Monad, that in that
newsgroup you can find the Monad team, and others answering questions on
Monad (MSH), and you can find great support there.
I also did put some Comments inline
mayayana wrote:
>> I do not know what microsoft's support plan is , I do know that they have
>> stopped developing vbscript years ago. I think that vbscript, wmi, and wsh
>> regardless if they are "supported" or not will be useless
>> comparatively against msh and ironpython and other .net framework
>> technologies. Wmi will still be around, and developed as far as I have
>> heard, but I could be wrong on that. wsh/vbscript are supposed to be still
>> supported but microsft has said they are have stopped development on them.
>>
you must see Monad more as a "tool" to get to those technologies quick.
Monad e.g. has WMI / COM / ADSI and .NET support
for example :
get-WMIObject win32_operatingsystem
will get back that WMI class.
> Thanks. I've been doing some research since
> this discussion got going, having downloaded the
> Monad docs and some articles. I can't seem to find
> a totally definitive declaration about VBS and WSH,
> but the MS position does appear to be, as you say,
> that there will be no further development but that the
> older options will still be left in the system for whoever
> wants to use them.
>
>> I think once you get used to msh you will really like it. The
>> opportunities for automatation with msh are awesome if microsoft goes
>> ahead with what it says it is planning. And it actually works as stated.
>>
I'm using Monad now since october and as said got realy addicted ;-)
> I haven't had much chance to look it over, but there
> are two thoughts I have:
>
> 1) Something designed
> optimally for admin is not necessarily optimally designed
> for other uses. Hopefully Monad is good for both. Personally
> I don't need to adjust something or check installations
> on 100 machines. I'm more apt to want to alter 100 files on
> 1 machine....or vwrite a small program to automate something.
I think it is its great to figure some things out on the commandline and
then put them together as a script.
> 2) Personally I don't like command line. To my mind, if I'll
> need to write a command with options more than a couple of
> times then I may as well write a script or program to automate the
> whole thing, rather than having to memorize all the
> command options and type it out by hand every time.
I think you will like monad for this reason, you have a lot of power on
one-liners and its easy to combine them in a script.
> Of course, command line is great as one option, but
> that doesn't appear to be the plan with Monad. I may be
> missing something with Monad (I've just started reading the
> docs), but it appears to me that it doesn't provide a host for
> actual text files. In other words, it's great if MS wants to add
> a new system for scripting, but if they cut out the intermediate
> level - between command line and compiled software - of hosted
> script files, leaving only command line hosting, then interactive
> script applets would be impossible. That's mostly
> what I use script for. For instance, something as simple as
> removing read-only attributes: I have a script on my Desktop
> for that. When I copy a folder from a CD I can remove all read-only
> attributes in the folder by dropping it onto the script. That's far
> easier than opening a console window, doing a cd to Desktop,
> then carefully typing in an attrib command.
Monad has full support for script files, and interactive use.
> On the other hand, maybe, as Michael Harris suggested,
> I'm just an old fuddydud attached to technicolor GUI
> functionality while the world is moving on, "back to the
> future", to the advanced world of console text input. Perhaps
> I should just be glad that the new cutting edge doesn't
> involve punch cards. :)
>
LOL, did not see punch cards yet (but did see Logo;-))
I think some good points are made in this post(and rest of thread), but
I think Monad will "fulfill" most of them,
I really like it to have a powerful shell again, after all those "GUI
years"
gr /\/\o\/\/
PS I also have a blog about Monad, and you can find links to some more
there :
http://mow001.blogspot.com