[p4] VS.Net Perforce - Partial Check in

Smith, Jeff jsmith at medplus.com
Tue Mar 22 05:51:36 PST 2005

Not to state the obvious, but if you are paying for Perforce support, I
would definately drop them a line.
-----Original Message-----
From: G, Deepa (Institutional Securities Management)
[mailto:Deepa.G at morganstanley.com] 
Sent: Tuesday, March 22, 2005 5:39 AM
To: perforce-user at perforce.com
Subject: [p4] VS.Net Perforce - Partial Check in

Hi All, 

I had posted this question sometime back to this forum, but did not get
a reply. Any one has any idea how I can solve this?

I have seen this peculiar behavior of VS.NET integrated with Perforce.

Lets say I have a list of files in my change-list and I try to check-in
all of them at the same time from the VS.NET IDE. 

After I click on the perforce check-in pop-up box, I get messages like
"files have been changed, do you want to reload them". Irrespective of
whether I say "yes" or "no" on this box, only few files gets checked in
(the symbol changes from a tick-mark to a lock on VS.NET IDE) and the
other files still have the tick-mark !

When I check in the Perforce P4Win UI, the changelist doesnt have any
files! Does this mean all files have been checked-in successfully? Then
why does the VS.NET IDE show the other files still with the tick mark. I
have to manually right-click on each file then and say check-in for the
tick marck to be replaced with the lock. This is confusing.

Any one else faced this problem?



Deepa G 
Morgan Stanley | Institutional Securities Mgmt
Bldg. 5, Sector 30, Mindspace, Goregaon (West) | Floor 02
Mumbai, 400 090
Phone: +91 22 5641-1138
Deepa.G at morganstanley.com <blocked::mailto:Deepa.G at morganstanley.com> 

NOTICE: If received in error, please destroy and notify sender. Sender
does not waive confidentiality or privilege, and use is prohibited.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://maillist.perforce.com/pipermail/perforce-user/attachments/20050322/66141848/attachment-0007.html>

More information about the perforce-user mailing list