- Concepts for Grokking
- Not Quite as Simple as 1-2-3
- Weighing the Pros and Cons
- Microsoft Silent on Exchange 12 Timetable
Like this article? We recommend
Like this article? We recommend
Like this article? We recommend
Weighing the Pros and Cons
Will Monad’s abandoned support for v2.0.50215 indeed turn out to be the best way to go? Maybe. But then again, maybe not.
Will other developers and administrators put off getting their feet wet with Monad, so they can bide their time in upgrading to new editions of the framework and VS? It’s too early to tell the answer to that question. But there are clear signs that Microsoft and early Monad adopters are doing their best to gear the emerging scripting shell to the needs of the great masses of .NET developers and administrators.
Microsoft officials frankly admit to a need for very clear Monad documentation. "We have not done a good job of documenting [Monad] concepts, but we need to [do so]. Clearly this is towards the top of the list," Snover wrote upon the release of Monad beta 2 in September 2005.
Meanwhile, prebuilt cmdlets are multiplying beyond the sample cmdlets included in Monad. Thomas Lee has posted dozens on his own web site; for example, scripts for modifying the color scheme of the normal console and for changing the names of other cmdlets.
Microsoft’s Exchange team has already written and demoed a number of other cmdlets, including scripts for creating storage groups and mailbox databases, and for getting lists of all running agents, their status and priorities.