Copying an existing ATL DLL

NTDEV
1

We’ve got a COM DLL based on ATL, and it’s time to update it with new
interfaces, etc. Is there a convenient way to create a new project and copy
the source files, etc. over so that the existing interface definitions
transfer intact? I really don’t want to have to retype all those interface
definitions just because it’s a new project (and we need to keep the old
version intact for historical purposes). If I just copy all of VC’s
configuration files, everything bears the name of the old project and
there’s plenty of opportunity for confusion if the two projects are
manipulated on the same machine.

Thanks for any guidance, RTFM, etc.

RLH

2

> We’ve got a COM DLL based on ATL, and it’s time to update it with new

interfaces, etc. Is there a convenient way to create a new project and
copy
the source files, etc. over so that the existing interface definitions
transfer intact? I really don’t want to have to retype all those interface
definitions just because it’s a new project (and we need to keep the old
version intact for historical purposes). If I just copy all of VC’s

I was influenced in hardcore COM development in about 97-early 98.
Our way was to NOT use the ATL AppWizard, though use the ATL itself.
We wrote all our IDLs by hand - they were the interfaces (self-documenting
with lots of comments, for sure) between sub-teams.
The ATL headers derived from the interfaces were alse written by hand. It is
not so terrible as it seems :-)))

Max