Offline Work Issues

[ChristianH]

There seems to be some issues with offline changes.

1st issue: After doing offline changes at more than one projedct, the detection of offline changes after going online works only at the first opened project. On any other project, the offline changes are not detected. Each changed file is marked as renegate and must be checked out and checked in.

2nd issue: Offline added files are not automatically added to fortress after going online. Each file must be marked and added to fortress manually. Its very hard to find each not added file at large projects.

3rt issue (new in Fortress Client 2.0.1): While working offline on a project, every file is "readonly". In order to modify it, the read only flag must be removed first.

All this issues appear in Fortress 1.4.1, Fortress 2.0.1 Enhanced Client and Visual Studio 2005. The classic client at Visual Studio 2003 works fine. Are the plans to remove this issues at future versions?

Christian H

[lbauer]

1st issue: After doing offline changes at more than one project, the detection of offline changes after going online works only at the first opened project. On any other project, the offline changes are not detected. Each changed file is marked as renegate and must be checked out and checked in.

We would like to try to reproduce this behavior.

First of all, please confirm whether you are using the Fortress 2.0.1 server. The Fortress 2.0.1 client should not be able to connect to a Fortress 1.1.4 server.

Also, is this a new issue? Was it working properly in a previous version of Fortress?

When you are off-line, a are you working with one solution with more than one project? Or are you working off-line with one solution/project, then closing that an opening a different solution/project?

When you make an offline change the file is not checked out, so it would not be unexpected that the file would be renegade. Are you thinking that the modified file should be checked out automatically when you go back online?

[ChristianH]

Linda,

thanks for your reply.

we notice the 1st and 2nd issues at Fortress Client/Server 1.1.4 and Fortress Client/Server 2.0.1. But may be the problems appeared in an earlier version and we skipped version 2.0.0. And they only seem to appear at the Enhanced Client.

Follow this steps to reproduce the behavior:

• Create two or more solutions with at least one project in each solution and some files at Visual Studio 2005 on one Windows XP machine.
  Check in the solutions into Fortress using the Enhanced Client.
  Close the Visual Studio.
  Open a solution and "Work offline".
  Do some changes in some files in each solution and safe them.
  Add some files to the projects.
  Close the Visual Studio.
  Open the first offline changed Solution and "Go Online".
  The Fortess client will prompt you that offline changes are detected and checked out now.
  Open the next offline changed Solution, now you are already online.
  The offline changed files are now market as renegate and you have to check them out und check them in manually. Offline added files will not be added to Fortress. You have to add them manually.

The 3rd issue seems only to appear, if you have no connection to the Fortress server when you open a solution.

Christian

[lbauer]

Here's a workaround that you can try:

Go offline again after you commit the changes from the first solution, but before loading the second solution.

Offline is not a per-solution setting. It applies to every solution from that server.

[ChristianH]

This workaround works for me.

Thanks.

ChristianH

[lbauer]

Thanks for the update. That's good news.