Is this what project templates are for?
I have not used them, but I thought this was there purpose.
Tim S
Well, I would prefer to use a wizard because the scripting (once I get my head round it) should give me the opportunity to make the whole process a lot more student proof (note that we're not talking about computer scientists here, just ordinary students doing Music Technology), but, for now, I have worked up a template which does pretty well all the basics of what I want, except change the name of the .def file I have to pass to the linker (this is required because of the way VST audio plugs are structured). If I make a new VST plug project, setting the name as, say, "New_VST_Plugin" all the file names, such as the .dll output name, etc., get changed appropriately, but not the .def file which, because it is include in the template file thus;
<Linker>
<Add option="-def AmbVSTGui.def" />
</Linker>
whereas any other AmbVSTGui reference is changed to New_VST_Plugin in the .cbp project file generated from the template. Is there some magic I can do to change this behaviour, or is this a C::B "feature"?
Dave