[OpenAFS-win32-devel] MMC project update

[Christopher D. Clausen]

On XP/Windows 2003 apparently one needs to run mmcperf.exe before trying 
to register new snap-ins.  Otherwise I get an exception running 
installutil.

Also, none of the various fields are filled in when I run this.  It is 
just empty boxes.  (Perhaps this is all that should be there at this 
point in time.)

To me, the Canel button makes no sense at all in the context of an MMC 
snap-in.  In fact having both "Ok" and "apply" are redundant.  Only one 
of them should be needed as the usual occurance of "Ok" is to do the 
same as the "apply" button and then close the dialog as well.  I would 
think that the snap-in isn't closed unless the user exits it, so having 
only an "apply" button makes the most sense to me.  One can simply click 
on another snap-in without clicking apply to undo changes without 
applying them.

I'd say to not have the tabs across the right pane and instead have a 
drop-down sub menu under the left pane for each of the current tabs. 
This would be more inline with other snap-ins from Microsoft and should 
in theory allow an agency using AFS to setup specific consoles that only 
allow specific features to specific admins / help desk users.  E.g. one 
could setup an MMC view to only display the ability to start and stop 
the service.

I'd also suggest using an AFS directory name without spaces in it so 
that is easier for the rest of us to get to the code.

<<CDC

Brant Gurganus <brant@gurganus.name> wrote:
> I made a new snapshot of my project available at
> \\afs\rose-hulman.edu%user.class07.gurganbl\Public\"OpenAFS Client
> Manager"
>
> It should be rather complete as far as the user interface, though
> what's there is based on what was in the prototypes. If there's any
> feedback on what is is missing or should be changed, let me know now
> before too much gets hooked to actually doing something.
>
> To build: Use Visual Studio and build either x64 or x86
> configurations.
>
> To install, run the x86 or x64 installutil on the built assembly.
>
> To uninstall, run the x86 or x64 installutil with the /u switch on the
> built assembly.
>
> To use, launch MMC and add the OpenAFS snapin.
>
> Here's what should work:
> All the UI should be visible if you expand the MMC enough.
> Starting and stopping the AFS Client service should work.
>
> Here's what I need help with:
> I haven't figured out how to get the Windows Forms control to fill the
> space it has in the console.
> Starting and stopping the service outside of the MMC will result in an
> exception since you are starting an already running service or
> stopping and already stopped service. If there are thoughts on how to
> best handle such exceptional states, I'm welcome to them.
>
> What I've written is known to work in 32-bit and 64-bit environments
> on Windows 7 RC.
>
> It should work on Windows XP and up. You will need .Net 2.0 or higher
> installed as well as MMC 3.0 if on Windows XP or 2003. You can get it
> at http://support.microsoft.com/kb/907265
>
> Please let me know if you have any feedback both as a user or as a
> developer.
>
> One other note, the project is set up to strongly name the assemblies
> built using my key. You don't have my password so you can create your
> own key with the sn tool or just not give your assembly a strong name.
> An alternative is to delay sign the assembly, but you'll have to tell
> .Net to ignore verifying the assembly's signature.
>
> Brant Gurganus
> http://gurganus.name/brant