Re: [Setacl-devel] ATL COM, Active Directory Support

[Helge K. <hel...@ne...>]

Active Directory support _could_ be included in SetACL in 
the future (when everything else works ;-). I do know that 
it is quite complex; also, there is a tool in the Reskit 
called DSAcls.exe that already does the job. I suggest we 
talk about this again later.

NT4-Support: until now I have only come across one function 
(regarding SDDL strings) that is not available in NT. We 
_could_ drop NT support which would open the path to 
exporting AND importing complete security descriptors with 
all DACL and SACL settings (as SDDL strings), and enable AD 
support. What do you think?

COM control: Howard, would you like to start with the 
control? When I started to work on the main class CSetACL I 
implemented the interface to the outside world first - it 
should be complete enough by now to be able to build a 
control (and a console EXE) around it. My plan was to expose 
the public funtions in the control which are all input 
functions to pass data to the class. There is, of course, 
the need to pass strings back to the calling 
class/function/EXE, like detailed error/success/status 
messages which might be needed by the caller. I used a 
callback function for that purpose to be able to send any 
message in realtime while the program is still working. 
Example: someone uses the OCX to build a GUI around SetACL. 
The user of this GUI wants to create a permission listing of 
a large partition which might take a while. Via the callback 
function the GUI can display in real time the permissions 
that currently processed by SetACL. Is a callback function a 
viable way to do it and does it work with COM?

CVS: I started a new dir/tree called baseclasses for the 
main classes. I think it would be wise to use a separate 
dir/tree for the OCX and another one for the console UI.

Helge

---- Original message ----
>Datum: Tue, 14 Jan 2003 20:18:48 +0100
>Von: "Howard W Wortley" <hwo...@ms...>  
>Betreff: [Setacl-devel] ATL COM  
>An: <set...@li...>
>Cc: <hel...@ne...>
>
>Hi
>
>I am familiar with building COM components (clients, 
servers, console apps) etc using Visual C++ and ATL/COM. It 
is essential for building ATL/COM that the developer has SP5 
installed. Pro edition is OK no need for Enterprise stuff. I 
thought I had posted before Christmas that I thought ATL/COM 
was by far the best way to go on this project as it enables 
all of H.K. design goals to be met within a single code 
source. FWIW I am also familiar with Active Directory but I 
am not sure if SetACL is meant to get into that area or not. 
There are differences between supporting NT4 and Win2000. 
NT4 is sorta fading I suggest Win2000 and up support only.
>
>It would be possible to build using VC++ an activex OCX for 
use by VB6 if anybody thought that a good idea.
>
>
>Howard
>
>From: Helge Klein <helge@ne...>
> Language for COM control
>2003-01-14 11:44
> As already discussed in the forum SetACL is and will be
> written in VC++. There are mainly three reasons for this:
>
> a) SetACL is to run without any additional runtime files.
> Just the EXE (or OCX) is to be needed to use the program.
> Especially larger organizations will never install runtime
> libraries or even the .NET framework on production servers
> just to use a tool.
>
> b) SetACL is to fully support NT4 SP4+, W2k, XP, Windows
> Server 2003.
>
> c) SetACL needs serveral rather complex API functions which
> require pointers (to functions, too) and unicode.
>
> Those three points refer to the main program. I do not
> think, though, that it would make _any_ sense to implement
> other parts in another language. It would be very 
difficult,
> too, since the main program consists of several C++ classes
> which are _not_ wrapped in a DLL.
>
> Who has experience in building COM controls in VC++ using
> ATL or MFC?
>
> Helge