Bug Report: VS2005 IDE, Open From Fortress

gmagana · Post by **gmagana** » Mon Jun 11, 2007 10:46 am

It seems Fortress (or VS2005 when using Fortress) is even more picky about solutions and the directories that hold the projects of a solution.

I have a solution with the following directory structure (Sorry about the dashes, this forum software removes whitespace):

Devel
----- Gobae
--------- MO
------------- Gobae-MO [*]
--------------------- Client
------------------------- Gobae-MO-Client [+]
------------------------- Gobae-MO-DataFileImporter [+]
------------------------- Gobae-MO-RemotngClientLib [+]
------------------------- Gobae-MO-WebClient [+]
--------------------- Server
------------------------- Gobae-MO-ServerApp [+]
------------------------- Gobae-MO-ServerClassLib [+]
------------------------- Gobae-MO-ServerConfig [+]
------------------------- Gobae-MO-ServerConfigStore [+]
------------------------- Gobae-MO-ServerDBAccessLayer [+]
------------------------- Gobae-MO-ServerService [+]
------------------------- Gobae-MO-ServerShared [+]
--------------------- Setup
------------------------- Gobae-MO-DataFileImporter-Setup [+]
------------------------- Gobae-MO-ServerApp-Setup [+]
------------------------- Gobae-MO-WinClient-Setup [+]
--------------------- Shared
------------------------- Gobae-MO-Shared [+]
--------- Utils
------------- GobaeSecTester [+]
----- SharedComponents
--------- GobaeSec [+]
--------- xUtils [+]

[*] is where the solution file is found
[+] are the proejct files within the solution

When I load the solution from Fortress, I get all projects marked as "loading" and they never leave that status (see Error1.gif).

NOTE: This behavior appears to be related to solutions containing solution folders...

At this point only some of the project files are in their place in the working folder. Only project files are present, no other files are there (ie, source code, etc...). the project files that are there are the ones that are under the directory in which the solution file resides.

This point nothing works and I have to restart VS2005 and reopen the solution. I get an error about the projects not under the solution directory not existing, I press OK.

After the solution is re-opened, more details are visible about the projects under the solution directory, but the files are not there. I can now right-click on the solution and the Get Latest element is there now, so I press it.

Even though I got latest and the files are now in my working directory (only for the projects under the solution file's directory), they retain the "warning" icon as if I had not done a get latest.

At this point my solutions almost looks good. The projects in the different path are missing. (See Error2.gif)

I could not find a way to retrieve these within VS2005, so I gave up and closed the solution and did a get latest from the Fortress client.

When I reopen the solution within VS2005, all is well, and everythign works as expected from then on.

gmagana · Post by **gmagana** » Mon Jun 11, 2007 11:11 am

Here are the images for the above post:

Error 1

Error 2

gmagana · Post by **gmagana** » Mon Jun 11, 2007 11:21 am

On a related note, subsecuently opening other solutions from Fortress that use the shared libraries results in the library outside of the solution's directory being marked as loading, but it stays forever in that state:

This status does not go away until VS2005 is restarted. Closing/reopening the solution does not work.

gmagana · Post by **gmagana** » Mon Jun 11, 2007 11:41 am

For what it's worth, this appears to be partially related to the "Node mismatch count" problem ( http://support.sourcegear.com/viewtopic.php?t=7920 ).

The node mismatch count happens when you open a solution that has solution folders and you are converting from 2003 to 2005 style binding. The issue posted in this thread happens when you are trying to open a solution with solution folders that is already in Fortress with 2005-style bindings.