Integration in VS NET 2003

( CVSSCC , VS .NET, Latest, WIN 2000/XP, CVS NT 2.0.x )

Type: Public Status:Closed Created: 21 Oct 04 10:00 Updated: 21 Oct 04 10:00

--> Igor Pushkov (admin) at 21 Oct 04 10:00 writes

Well, it is clear now.
1. It may work if you will add it from IDE. More other, one of
advantages of our plug-in that it correctly support adding and pulling
files from IDE (in contrast to Igloo), and what is more important for
you Igloo does not create specific information in project/solution
files about SCC bindings. This partially explain why it works on VS
6.0.
2. You should seriously think do you really need such organization or
not. Best way (right from IDE point of view) is to have all files
under the same file tree, and the root of this tree should be folder
with solution file.
The another good way is to "simulate" situation of single tree
using unix "symlinks" if your repository is on server. This way you
can "map" files from any location on server to the appropriate module
as though they are located in that module.
3. There are lot of similar public tickets, you can search through
them to find other solution to that problem.

--> Roland Douyau (user) at 21 Oct 04 10:00 writes

Yes, it's a kind of organization we can have and in this example if the
files : my_very_usefull_file.c, my_very_usefull_file.c are included
in a project (for example project1) they don't appear as controlled by CVS.
C:\
\Work
\Solution1
solution1.sln
\Project1
project1.vcproj
\Project2
\Project3
\Shared
dummy.c
dummy2.c
\Stuff
my_very_usefull_file.c
my_very_usefull_file.c
excellent_library.lib
It seems that the problem appears with VS NET 2003 : one of my colleagues
who tried earlier VS NET 2002 (with the same projects) said that he don't
remember such a problem with this version !
Note also that I didn't try to create a new workspace/project with such an
organization and then put it under source control : maybe the problem
appears only with projects that are already under source control.
Thx.
Best regards.
-----Message d'origine-----
mailto:support@pushok.com]
Envoyé : jeudi 21 octobre 2004 10:02
À : Roland Douyau
Objet : Re: [pst330] Integration in VS NET 2003
http://www.pushok.com/tickets_addmodify.php?id=330
Please confirm that I understand you correctly. Is I am right that you
talking about
solution/project organization like this:
C:\
\Work
\Solution1
\Project1
\Project2
\Project3
\Shared
dummy.c
dummy2.c
\Stuff
my_very_usefull_file.c
my_very_usefull_file.c
excellent_library.lib
And your projects (solution) include files from "Shared" and "Stuff".
Is it correct? If not, please provide your file location scheme, and
we will know about what we talking.

--> Igor Pushkov (admin) at 21 Oct 04 10:00 writes

Please confirm that I understand you correctly. Is I am right that you
talking about
solution/project organization like this:
C:\
\Work
\Solution1
\Project1
\Project2
\Project3
\Shared
dummy.c
dummy2.c
\Stuff
my_very_usefull_file.c
my_very_usefull_file.c
excellent_library.lib
And your projects (solution) include files from "Shared" and "Stuff".
Is it correct? If not, please provide your file location scheme, and
we will know about what we talking.

--> Roland Douyau (user) at 21 Oct 04 10:00 writes

(First sorry for my english).
We are currently Visual Studio 6 and Jalindi plugin. We plan to migrate
our
projects under VS NET 2003. With Jalindi in VS NET 2003, I notice a problem
that doesn't appears under VS6 : the files that are not in a
(sub-)directory of the workspace or a project belonging to the workspace
are not marked as controlled by CVS (it's a problem for us because our
projects includes source files from many other locations).
I've downloaded the PushOK plugin to see if the problem is the same :
PushOK
plugin works fine in VS6 (like Jalindi) but the same problem appears under

VS NET 2003 (I suppose that the problem comes from VS NET IDE).
So is there a solution to solve this problem without move our source files
?

Rate this ticket:

Not useful at all

Partially useful

Useful

Very useful

Ticket

Integration in VS NET 2003