We have a developer at the DOE that has a package where she added a new file to the project, checked the file in, promoted the package to TEST, and then PRODUCTION in Harvest but Visual Studio/Harvest is still identifying the file as a new file not associated with a package.
The details of Visual Studio and the versions of the Visual Studio Add Ons are listed below as well as screenshots indicating that all the files are the latest versions and that the files are being seen as “new” files.
Please advise on potential additional steps that can be taken to resolve this issue.
Root cause was not found.
Upgraded to SCM Client and VSIP plugin v13.0.3 and this resolved the prolblem.