Hi,
At the June Best Practices Workshop, one of the =
Google
Summer of Code participants gave a short talk on a project involving a =
tool to
work with the Windows client. Something to do with MMC and the registry =
and C#
I think…
If someone could point me to some more detailed =
information
on the project, I would appreciate it.
Thanks,
Mickey Lane.
SNA
------=_NextPart_000_0002_01C9F663.F40C93F0--
From jaltman@secure-endpoints.com Fri Jun 26 19:13:11 2009
From: jaltman@secure-endpoints.com (Jeffrey Altman)
Date: Fri, 26 Jun 2009 14:13:11 -0400
Subject: [OpenAFS-win32-devel] Work on Windows MMC?
In-Reply-To: <000101c9f685$7b1e33f0$715a9bd0$@com>
References: <000101c9f685$7b1e33f0$715a9bd0$@com>
Message-ID: <4A450FB7.3090108@secure-endpoints.com>
Mickey:
GSOC projects are described at http://www.openafs.org/gsoc.html.
The project is implementing the mockups provided at
http://www.secure-endpoints.com/openafs-windows-roadmap.html#client%20service%20mmc
Jeffrey Altman
Mickey Lane wrote:
> Hi,
>
>
>
> At the June Best Practices Workshop, one of the Google Summer of Code
> participants gave a short talk on a project involving a tool to work
> with the Windows client. Something to do with MMC and the registry and
> C# I think…
>
>
>
> If someone could point me to some more detailed information on the
> project, I would appreciate it.
>
>
>
> Thanks,
>
> Mickey Lane.
>
> SNA
>
>
>
From mickeylane33540@gmail.com Fri Jun 26 19:22:57 2009
From: mickeylane33540@gmail.com (Mickey Lane)
Date: Fri, 26 Jun 2009 14:22:57 -0400
Subject: [OpenAFS-win32-devel] Work on Windows MMC?
In-Reply-To: <4A450FB7.3090108@secure-endpoints.com>
References: <000101c9f685$7b1e33f0$715a9bd0$@com> <4A450FB7.3090108@secure-endpoints.com>
Message-ID: <001301c9f68b$22888870$67999950$@com>
Thanks Jeffrey
I got a note from Brant on this.
That's exactly the information I needed. It looks very promising. If =
there's anything I can do to help (testing, etc) please let me know.
Mickey.
> -----Original Message-----
> From: Jeffrey Altman [mailto:jaltman@secure-endpoints.com]
> Sent: Friday, June 26, 2009 2:13 PM
> To: Mickey Lane
> Cc: openafs-win32-devel@openafs.org
> Subject: Re: [OpenAFS-win32-devel] Work on Windows MMC?
>=20
> Mickey:
>=20
> GSOC projects are described at http://www.openafs.org/gsoc.html.
>=20
> The project is implementing the mockups provided at
>=20
> http://www.secure-endpoints.com/openafs-windows-
> roadmap.html#client%20service%20mmc
>=20
> Jeffrey Altman
>=20
> Mickey Lane wrote:
> > Hi,
> >
> >
> >
> > At the June Best Practices Workshop, one of the Google Summer of =
Code
> > participants gave a short talk on a project involving a tool to work
> > with the Windows client. Something to do with MMC and the registry
> and
> > C# I think=E2=80=A6
> >
> >
> >
> > If someone could point me to some more detailed information on the
> > project, I would appreciate it.
> >
> >
> >
> > Thanks,
> >
> > Mickey Lane.
> >
> > SNA
> >
> >
> >
From brant@gurganus.name Sat Jun 27 02:04:08 2009
From: brant@gurganus.name (Brant Gurganus)
Date: Fri, 26 Jun 2009 21:04:08 -0400
Subject: [OpenAFS-win32-devel] MMC project update
Message-ID: <7085f1180906261804k748aa82ake17796cd4ba76215@mail.gmail.com>
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
From cclausen@acm.org Sat Jun 27 19:58:12 2009
From: cclausen@acm.org (Christopher D. Clausen)
Date: Sat, 27 Jun 2009 13:58:12 -0500
Subject: [OpenAFS-win32-devel] MMC project update
References: <7085f1180906261804k748aa82ake17796cd4ba76215@mail.gmail.com>
Message-ID: