[Setacl-devel] ATL COM

[Howard W W. <hwo...@ms...>]

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