Bug report (upgrading projects from VS2003 to VS2005 biding)

[gmagana]

I don't know if I should put this here or in the fortress forum... Since this most probably applies to Vault too, here it is:

I have been upgrading my solutions to the 2005 binding, and it seems that there are some .vssscc files being left checked out after the process is finished. I have to undo checkout manually (since the files are not changed). For some reason they are not being checked in when I check in as the last part of the 2003 to 2005 style binding upgrade process.

I have not been able to figure out a pattern as to which .vssscc files are being checked out and then not checked in as part of the upgrade process, but I have a strong suspicion that it involves projects that I am also upgrading from VS2003 to VS2005 at the same time I am switching them over to Fortress 1.0 (Vault 4.0). It would make sense, I suppose if the .vssscc files are only used by VS2003 (and are being left stranded by VS as part of the VS2003 to VS2005 upgrade process), but I am not familiar enough with VS to know that for sure.

Anyway, this is a relatively minor problem, but a problem nonetheless.

[jeremy_sg]

If you're checking in from the VS 2005 client, these vssscc files are not considered to be "in" the project or solution, so they are being left out. With VS 2005, the vssscc files are no longer used.