VS.NET 2003 don't recognize Source Safe controled files

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Martin Horst - 04 May 2004 07:19 GMT

Hi,

I've little Problem with VS.NET 2003 and VSS 6.0.
In a VC projekt all files are added to the Source Safe database and this
database is assigned to the VC projekt. If I now try to edit a file in most
cases
nothing happens. I've to check out these files using the Source Safe
explorer.
In some rare cases the VS check out dialogs appears so I can directly check
out
the file from inside Visual Studio. I can't find any reasons for this
behavior.
I've read that there are problems using VSS from inside the IDE when the
projekt files lie
inside another directory than the source files.

My projekt paths look something like this:

lib
+-- win32 <- Visual Studio projekt files
+-- src <- The source files.

Is there any way I can solve this problem because I'm getting bored always
to use
the VSS explorer for check out / check in operations.

Thanks in advance
Martin Horst

Reply to this Message

[MSFT] - 04 May 2004 09:30 GMT

Hi Martin.

Thank you for the post.

Regarding the issue, we are finding proper resource to assist you, and will
update you as soon as possible.

Regards,

Luke
Microsoft Online Support

Signature

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)

Reply to this Message

Kevin Yu [MSFT] - 06 May 2004 13:31 GMT

Hi Martin,

First of all, I would like to confirm my understanding of your issue. From
your description, I understand that the checkout dialog box appears
occasionally in VS.NET when you're trying to edit a file under source
control. If there is any misunderstanding, please feel free to let me know.

Based on the sympton, I think the possible cause of this is: some of the
files in the project are outside the project's folder bound to source
control. Those files cannot be controlled unless moved, or the project is
rebound correctly (the bound folder is logically "moved" to include those
files). Here are the steps for solution:

1) Use File/Source Control/Change source control dialog.
2) Unbind the project from source control.
3) Rebind it back, but this time pick the folder in VSS that matches the
project's unified root on the local disk (the folder that contains all
project files)

e.g. I suspect you have the win32 folder bound to something like
$/project/win32
The local unified root seems to be the "lib" folder
After rebind, you have to pick the folder above $/project/win32 that
matches "lib", in that case probably "$/project"

HTH.

Kevin Yu

Signature

=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

Reply to this Message

Martin Horst - 07 May 2004 06:11 GMT

Hi Kevin,

> Hi Martin,
>
> First of all, I would like to confirm my understanding of your issue. From
> your description, I understand that the checkout dialog box appears
> occasionally in VS.NET when you're trying to edit a file under source
> control. If there is any misunderstanding, please feel free to let me know.

yes, that's exactly the problem.

> Based on the sympton, I think the possible cause of this is: some of the
> files in the project are outside the project's folder bound to source
> control. Those files cannot be controlled unless moved, or the project is

Yes that's right. The funny thing is, that all files are outside the projekt
folder!

> rebound correctly (the bound folder is logically "moved" to include those
> files). Here are the steps for solution:
[quoted text clipped - 10 lines]
> After rebind, you have to pick the folder above $/project/win32 that
> matches "lib", in that case probably "$/project"

Thanks for you anwser Kevin. I will try it and then post what happends.

Best regards
Martin Horst

> HTH.
>
> Kevin Yu
> =======
> "This posting is provided "AS IS" with no warranties, and confers no
> rights."

Reply to this Message

VS.NET 2003 don't recognize Source Safe controled files

Free Magazines