[p4] Passwords and Visual Studio .Net

Rainey, Mark (Cleveland) Mark_Rainey at intuit.com
Wed Oct 5 06:07:50 PDT 2005

Make sure the solution and all projects are bound to Perforce.  The
developer will have to clean up any source control files in the solution
directory structure and then "Open from Source Control" the solution to
recreate the scc files in that users workspace.  This has worked for me in
the past.  


-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Brough, Nicolas
Sent: Wednesday, October 05, 2005 5:53 AM
To: perforce-user at perforce.com
Subject: [p4] Passwords and Visual Studio .Net


I've got a couple of users who are complaining that VS.Net is prompting them
for their Perforce password several times when they open a project, despite
having the "save password" box checked.  Once they're in, they can work
without being prompted again.

We've a load of users with no password who don't have this issue, but this
is a bad idea which we're trying to get away from (I know that if I blank
out the password, it all works fine)

Anyone have any ideas on why this is happening or how to make it stop?

Thanks, Nic Brough

perforce-user mailing list  -  perforce-user at perforce.com

More information about the perforce-user mailing list