Local path is incorrect and cannot be edited

( CVSSCC , VS .NET, Latest, WIN 2000/XP, UNIX )

Type: Public Status:Closed Created: 17 Aug 04 08:00 Updated: 17 Aug 04 08:00

--> Carl (user) at 17 Aug 04 08:00 writes

Thanks - that fixed the LOCAL PATH problem, although it still won't bind.
The project contained references to the header files in ..\H. I have to
wonder: if VS.NET can't handle files from more than one folder in a
project, why does it allow them? Or is this a limitation with PushOK
and/or CVS?

In any case, I still cannot bind the project to source control. Now all
the fields in the dialog look OK, clicking Check shows no problems, and I
get the correct LOCAL PATH, but when I click OK, it shows "Unknown" for
status, does a PushOK status check, and then shows "Invalid" for status.
There is no more explanation and no error message until I hit OK to the
"Change Source Control" dialog, at which point it says the bindings are not
correct and gives me the choice of fixing them or continuing. There is no
explanation as to *why* the bindings are not correct, or what I can do to
fix it. Thanks for your help.

--> Igor Pushkov (admin) at 17 Aug 04 08:00 writes

As I say before LOCAL PATH is supplied by IDE. VS .NET calculates is
as common parent dire for all files. Lets imagine that we have work
folder tree as shown below:
C:\
\WORK
\Mysolution
\MyProject1
\MyProject2
Mysolution.sln
\Mysolution2
\MyProject3
\MyProject4
Mysolution.sln
\Shared
\MySharedProject1
CASE 1
We add Mysolution to source control and it includes only files and
projects that lies in it folder itself and subfolders. The LOCALPATH
that calculates the IDE will be "C:\Work\MySolution"
CASE 2
We again add Mysolution, but now it contain also some projects (files)
from MySolution2. In that case LOCALPATH will be "C:\WORK"
CASE 3
The same as CASE 2 but now our solution contain also some files from
"C:\Shared". In that case LOCALPATH will be "C:\"
So, hope now it is clear for you that your project includes some files
that located not under the C:\RUN. The solution for problem is
_exclude_ such files from project.
Let me know if this will solve your problem.

--> Carl (user) at 17 Aug 04 08:00 writes

The problem is quite simply that I cannot bind one of the projects. There
are 9 projects plus the solution file (SLN). 8 of the projects bind
without problems - local path is correct in each case. One project will
not bind no matter what I do.

In the "Select CVSROOT, module and local path" dialog box, I only have two
fields that I can edit. The first is the CVSROOT, which is correct (and
pressing Check confirms that). The second is the CVS MODULE, which is
incorrect, but I can edit it to make it correct, and pressing Check
confirms that it is then OK. However it is obvious that the LOCAL PATH is
incorrect, and I cannot edit it. The local path is set to S:\ and it
should be S:\RUN. When I hit OK, I get the following message box:

Source Control
The folder you chose is not a valid binding root for the projects you have
selected. You attempted to retarget a solution to a source control folder
that is not within the solution's root. In the change source control dialog
box, specify the root for the solution. Select the folder 1 levels higher
in the tree to change the source control bindings correctly.

If I just hit OK again, then I get back to the "Change Source Control"
dialog box, but the status for the RUN project says "Invalid".

--> Igor Pushkov (admin) at 17 Aug 04 08:00 writes

You cannot edit them since IDE pass specific flag through SCC API which
instruct us to prevent this.
I.e. you cannot modify local path in that case.
If you explain me your problem with binding I will help to resolve it.

--> Carl (user) at 17 Aug 04 08:00 writes

I have spent all day trying to fix the bindings for a project, which are
not working. The problem is that when I go into the VS.NET "Change Source
Control" dialog box and click on "browse". Then I get a PushOK dialog
which contains a field called "LOCAL PATH". The contents of the field are
wrong, but the field is grayed out so I cannot fix the problem. Why can't
I edit the field?

Rate this ticket:

Not useful at all

Partially useful

Useful

Very useful

Ticket

Local path is incorrect and cannot be edited