[p4] Can't checkin from Visual Studio 2003
Silgi, Nir
nsilgi at shopping.com
Tue Aug 22 07:06:32 PDT 2006
The problem was indeed that the drive in Root folder in the Client
workspace was with capital D. changed to lowercase and everything is
perfect.
You really did save me lot of troubles with this piece of info, since
the SCC log shows nothing.
THANKS MUCH,
NirS
-----Original Message-----
From: Weintraub, David [mailto:david.weintraub at bofasecurities.com]
Sent: Monday, August 21, 2006 9:18 PM
To: Silgi, Nir; perforce-user at perforce.com
Subject: RE: [p4] Can't checkin from Visual Studio 2003
Go to "Files->Source Control->Change Source Control" and check the
bindings. See if all projects are bound. Also make sure that drive
letters in your Client's Root: field are lowercase. Sometimes, uppercase
letters cause problems.
-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Silgi, Nir
Sent: Sunday, August 20, 2006 12:06 PM
To: perforce-user at perforce.com
Subject: [p4] Can't checkin from Visual Studio 2003
Hi,
I have a severe problem of checking in projects I just added to source
control from Visual Studio 2003.
The scenario is:
I create a new VS project -> Add to source control-> Perforce login->
After some time I get the message: "Failed to check in one or more
files. Some files remain checked out or not added.
When I go to P4V I see all the files marked for add in a pending
changelist. For some reason the VS can't check the files in.
One more check I made is the Change the source control dialog. The
status of the provider is Invalid (second attachment)
Needless to say this causes big frustration to people I'm just teaching
Perforce.
On my personal PC everything works fine.
Please help,
Thanks.
_______________________________________________
perforce-user mailing list - perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user
More information about the perforce-user
mailing list