Never Created a ATL project from scratch on VC2003 - Manging COM ATL output files
-
Hi, I have worked on ATL projects in VC2003 and above, but I have never created them from scratch. They have all originally been projects that evolved from VC6 code. How do people handle deployment and dependencies of the projects? Under VC6 the .idl file is shown as being part of the project, and therefore you could modify where the .tlb and .h and .c files where generated. At my current company we have a .\TLB directory off the branch root. How can I make the .tlb file end up there? I cannot see either the idl file, or its project settings. Peter
-
Hi, I have worked on ATL projects in VC2003 and above, but I have never created them from scratch. They have all originally been projects that evolved from VC6 code. How do people handle deployment and dependencies of the projects? Under VC6 the .idl file is shown as being part of the project, and therefore you could modify where the .tlb and .h and .c files where generated. At my current company we have a .\TLB directory off the branch root. How can I make the .tlb file end up there? I cannot see either the idl file, or its project settings. Peter
Hah Hah :-D I've figured it out. The ATL project had been supplied to be by a collegue, and he had left the defaulted "Attributed" item in the ATL Project wizard. If you create a project and clear this the .idl files appear just as they did with VC6.
-
Hah Hah :-D I've figured it out. The ATL project had been supplied to be by a collegue, and he had left the defaulted "Attributed" item in the ATL Project wizard. If you create a project and clear this the .idl files appear just as they did with VC6.
How do people who create attributed atl projects manage the output files?