Any more news on monad?

Have not heard anything for a while about monad.

Any idea of release?  Just longhorn or is it going to be part of Win2003 & XP?

littleguru wrote:

I haven't heard also nothing for a while. Today I was on beta place, there is still the old version. I hope they port it also to winxp and win2k.

What do you mean, port? It already works on XP (I'm not too sure about 2k though).

I've read that they were aiming to release the first official version as a part of the next version of Exchange (could just be rumours though).

Since it's a .Net 2.0 app, I hope they'll release a new beta when Whidbey beta 2 is released.

Sven Groot wrote:

littleguru wrote: I haven't heard also nothing for a while. Today I was on beta place, there is still the old version. I hope they port it also to winxp and win2k.

What do you mean, port? It already works on XP (I'm not too sure about 2k though).

I've read that they were aiming to release the first official version as a part of the next version of Exchange (could just be rumours though).

Since it's a .Net 2.0 app, I hope they'll release a new beta when Whidbey beta 2 is released.

I have gotten it to work on Win2k just fine.  It works extremely well.  If I can get an answer as to whether I can leagally offer a downloadable compilation for Win2k depends on Microsoft and how soon they get back to me.  I have heard it will be part of .NET Framework 2.0 and I have also heard it will be a Longhorn only technology, so its a wait and see type of situation.  I havent heard the Exchange rumor though although to me it would make no sense to release it with Exchange, they could probably put some cmdlet or Exchange management scripts with Exhange.

Part of Exchange?  Eh?  Isn't this the Longhorn command shell.  Or have I gone mental?

EDIT:  Weird.  A bit of Googling and...

"MSFT James Truher (Expert):
Q: Will MSH V1.0 be done before Longhorn?
A: Monad will ship as a feature of Exchange 12 in 2H06 (target).Monad will ship in Windows after that. Release vehicle is undefined. Monad will support WS03 SP1, XP SP2, Longhorn"


Now, that makes no sense whatsoever

Cider wrote:

Part of Exchange?  Eh?  Isn't this the Longhorn command shell.  Or have I gone mental?

EDIT:  Weird.  A bit of Googling and...

"MSFT James Truher (Expert):
Q: Will MSH V1.0 be done before Longhorn?
A: Monad will ship as a feature of Exchange 12 in 2H06 (target).Monad will ship in Windows after that. Release vehicle is undefined. Monad will support WS03 SP1, XP SP2, Longhorn"


Now, that makes no sense whatsoever

Now that I have heard the rumor, you are correct it really makes no sense whatsoever.  Hopefully they will offer us Betaplace members a full version before they ship commercially.

Scobleizer mentioned in another thread recently that he has some more stuff coming on monad in the near future.

We will have an update on betaplace in a month or so.  I think you'll really enjoy this update.  The majority of the language is now complete and you can do some amazing things with it.  I'm giving an INTRO and ADVANCED Monad Scripting class at MMS next week so please drop by if you are attending.

We are working with on the of the server teams and that partnership is going extremely well.  (They don't want us announcing their features so you'll have to have some fun guessing for a little bit.)  They are driving a great set of requirements and validating a lot of our work.  In particular, all of their admins GUIs are written in MMC2.1 and layered on top of MONAD.  There is nothing that you can do in the GUI that you can't also do from the Command Line!  Working with a large scale server product helps ensure that those scenarios work really well.

We are still planning to ship downlevel support and in the OS but the specifics are not available at this time.  You shouldn't read too much into that.  We are just getting hard-core about remaining silent about vehicles and timing until all the details are nailed down.

Jeffrey P. Snover
MONAD Architect

I never really understood what Monad is about, is it the next version of the commandline?

I think it's for automating windows.