P4DTI issue job000179

TitleTeamtrack.dll can get lost
Statusclosed
Prioritynice
Assigned userGareth Rees
OrganizationRavenbrook
DescriptionAn inexperienced Windows user who copies the P4DTI files from the unpack directory to another one might end up without teamtrack.dll (since DLLs are hidden by Windows tools like Windows Explorer by default).
AnalysisWe could rename teamtrack.dll as teamtrack.pyd and avoid this problem.
How foundcustomer
Evidence<http://info.ravenbrook.com/mail/2001/01/17/15-48-45/0.txt>
<http://info.ravenbrook.com/mail/2001/01/18/12-04-05/0.txt>
<http://info.ravenbrook.com/mail/2001/01/18/11-26-31/0.txt>
<http://info.ravenbrook.com/mail/2001/01/18/11-47-31/0.txt>
Observed in0.4.2
Created byGareth Rees
Created on2001-01-18 12:05:01
Last modified byGareth Rees
Last modified on2001-12-10 19:19:23
History2001-01-18 GDR Created.

Fixes

Change Effect Date User Description
13767 closed 2001-07-03 12:36:09 Gareth Rees Added support for TeamTrack 5.0:
Split code/tsapi/... into code/tsapi-4.5/... and code/tsapi-5.0/... and split the Developer Studio project teamtrack.dsp into teamtrack-4.5.dsp and teamtrack-5.0.dspso that I can build two copies of the Python interface to TeamTrack, one for TeamTrack 4.5 and one for TeamTrack 5.0.
Updated teamtrack-module.cpp so that it has two entry points (one for each module).
Added teamtrack_version configuration parameter.
Updated design, Administrator Guide and release notes.