Using the vs.net integration, when the session has been invalidated for any reason and I try to check in some items, the first transaction fails, stating that the session was invalid. That's fine with me.
BUT: VS.NET still thinks that the file has been checked in and will therefore not let me check it in again; if I do a "get latest", it will quite often overwrite the changes that I had tried to check-in (need to be VERY careful in the merge process not to lose your changes)
Expected behaviour: Check in fails, file is still in "modified" state.
Regards,
Leo
VS.NET Integration: Check-In with lost session may lose data
Moderator: SourceGear