TestDriven.NET by Jamie Cansdale

NetFrameworkv1 WMI Provider?

From: Andy Cheung [MSFT] (hangc@online.microsoft.com)
Subject: Re: new namespace for v1.1?

View this article only

Newsgroups: microsoft.public.win32.programmer.wmi
Date: 2003-07-16 14:17:54 PST

This namespace and the WMI Configuration Provider are removed starting from
.NET Framework v1.1 Redist as part of our effort to phase out this provider
for various reasons. If you have .NET Framework v1.0 installed side-by-side,
you can still connect to root\NetFramework namespace using System.Management
in .NET Framework v1.1. However, you can only use the root\NETFrameworkv1
namespace to access configuration information specific to .NET Framework
v1.0.

-- 
Andy Cheung
Microsoft WMI Test Engineer
This posting is provided "As Is" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

psexec \\computer -u Administrator cmd

The above command launches an interactive command prompt on \\computer running as Administrator. Mark Russinovich and Bryce Cogswell over at Sysinternals never fail to amaze me. If you haven't already, go grab Pstools now!

Jason Posted @ 10/8/2003 2:18 PM
Wow...that's pretty wild..It's actually a local window executing a remote command prompt (or whatever). Very cool stuff!

I didn't describe what it does very well - but yes, it is pretty wild!  It will even copy the command you want to run onto the remote machine if nessesary (it doesn't have to be cmd).  All without using telnet.  Bonkers!

Command Line Client for GDN Workspaces

Apologies for the rather cryptic announcement yesterday.  It was late, it worked and I wanted to go to sleep! ;)  As the more curious of you will have found out, I’ve set up a couple of new GDN Workspaces.  One for NAntAddIn and another for a Workspaces command line client. You will find a pre-built version of 'wks'.  I will try and get a release of NAntAddIn up tomorrow.

I started working on the Workspaces client after getting frustrated trying to keep the NAntAddIn Workspace in sync with my local Subversion repository.  My ultimate aim is to create a two way bridge between them.  For the moment I’ve added a command (load) that lets me do a vendor drop into the Workspace (adding, deleting, checking out and checking in to sync up with my local version).  There’s also a command to save the Workspace along with last modified and version information.  This lets me store the Workspace in my Subversion repository and hopefully absorb changes made there.

I’ve loosely modelled the command line client on 'cvs' and 'svn'.  To get a list of possible sub-commands type “wks help”.  At the moment you will get the following list…

Available sub-commands:
    save - Save files from a Workspace with version information
    help - Help on wks sub-commands
    mywks - List MyWorkspaces

    size - List Workspace size information
    list - List all files in a workspace
    add - Add file(s) to a Workspace
    delete - Delete file(s) from a Workspace
    export - Export files from a workspace
    checkout - Checkout Workspace
    checkin - Checkin Workspace
    load - Load files, adding and deleting as necessary 

The functionality is skewed towards what I’ve needed so far.  It should be very strait forward to add new commands.  If you would like to run the unit tests, you will need write assess to the ‘wks-testing’ workspace.  Just ask and I will happily give you access.

..