We have a DOT NET solution consisting of 11 development projects.
I am the developer in charge of building the install.
Since no one else has InstallShield Developer, I've decided to start with a new solution (my own, local solution) and add the InstallShield project (along with the rest of the projects) to it.
For some reason, when I add certain projects I get a red checkmark next to the project and all of its files. I get this checkmark even though I don't have the project checked out. (see attached image)
What would cause this
Referencing projects in a local solution causing problems
Moderator: SourceGear
Referencing projects in a local solution causing problems
- Attachments
-
- SourceGear_CheckMarks2.JPG (58.07 KiB) Viewed 8275 times
Additional info
Ignore the fact that Installshield is involved. I can simplify the solution to just two projects and the same result occurs. See attachment.
The properties on the project files match. They are both marked as read-only.
Does this help clarify?
The properties on the project files match. They are both marked as read-only.
Does this help clarify?
- Attachments
-
- SourceGear.JPG (23.93 KiB) Viewed 8263 times
Well this is interesting:
When I open the vault client after I open the "non-working solution", the status of each file in the project shows up as "missing".
When I open the vault client after I open the "good solution", the status is blank (in other words, Vault sees the files.)
I played around with some of the variables in the solution file (SccLocalPath and SccProjectUniqueName) but could not seem to *trick* Vault into looking into the valid working folder.
DOT NET is fine as far as seeing the files. I can click on them within the IDE and the file will open.
Is there something I can edit within the solution file to fix this?
When I open the vault client after I open the "non-working solution", the status of each file in the project shows up as "missing".
When I open the vault client after I open the "good solution", the status is blank (in other words, Vault sees the files.)
I played around with some of the variables in the solution file (SccLocalPath and SccProjectUniqueName) but could not seem to *trick* Vault into looking into the valid working folder.
DOT NET is fine as far as seeing the files. I can click on them within the IDE and the file will open.
Is there something I can edit within the solution file to fix this?
- Attachments
-
- Workingfolders.JPG (67.3 KiB) Viewed 8256 times
What version of which IDE are you using, and how did these files get added to Vault?
It looks like the problem is that the IDE didn't set the working folder correctly in the Vault. If you know where the working folder is, then you can set it in the Vault GUI client (do this while the IDE isn't running).
Do you have a project that contains files in two different workings, but are in the same folder in Vault? That would cause problems like this. Web projects will sometimes do this if they were added that way from the IDE.
It looks like the problem is that the IDE didn't set the working folder correctly in the Vault. If you know where the working folder is, then you can set it in the Vault GUI client (do this while the IDE isn't running).
Do you have a project that contains files in two different workings, but are in the same folder in Vault? That would cause problems like this. Web projects will sometimes do this if they were added that way from the IDE.
Hi.
Just wanted to post that we did get this fixed yesterday (would've tried to fix it sooner but had some deadlines to meet )
I say "we", but what I really mean is another developer in our department. He went through a lot of steps trying to fix so he can't remember everything. However, he does know he did the following:
1. Disconnected the solution from Vault
2. Cleared the Solution out of vault
3. Gave each project its own individual solution (e.g. Created Project1.sln for Project1.vbproj, Created Project2.sln for Project2.vbproj, etc.)
Did this by creating a blank solution in the project directory and then used the "Add Existing Project" option to add the project in that directory to the solution.
Once all that was done he's not sure if he added them all to the parent solution first and then checked it in to Vault or if he did them one at a time. Well, he knows he did both but that was because whichever method he did first did not work. Therefore, he had to remove it yet again and try the other method.
Hope that makes sense and helps anyone else who may have this problem.
Just wanted to post that we did get this fixed yesterday (would've tried to fix it sooner but had some deadlines to meet )
I say "we", but what I really mean is another developer in our department. He went through a lot of steps trying to fix so he can't remember everything. However, he does know he did the following:
1. Disconnected the solution from Vault
2. Cleared the Solution out of vault
3. Gave each project its own individual solution (e.g. Created Project1.sln for Project1.vbproj, Created Project2.sln for Project2.vbproj, etc.)
Did this by creating a blank solution in the project directory and then used the "Add Existing Project" option to add the project in that directory to the solution.
Once all that was done he's not sure if he added them all to the parent solution first and then checked it in to Vault or if he did them one at a time. Well, he knows he did both but that was because whichever method he did first did not work. Therefore, he had to remove it yet again and try the other method.
Hope that makes sense and helps anyone else who may have this problem.