[p4] Passwords and Visual Studio .Net

Brough, Nicolas (Contractor) BroughN2 at bp.com
Wed Oct 12 14:26:49 PDT 2005

Mark, that's great.

We stumbled upon it in the end, purely by luck! The user had ignored me
telling them to "open solution from source control" when first opening
the project (which I always do because I rarely have any trouble if they
do).  Then not told me that he'd ignored me.  Once I'd established this,
we went back over it all from basics, and on the second try, another
user spotted that the .sou file was changing, so we moved it and tried
again.  This fixed it, exactly as you suggested!

However, the stuff you've posted on has just sorted out another user
(inherited machine this time, changing client specs and users is a bit
messy here).  This time it was the .ncb file and the overwrite flag
fixed it on the first pass!

So, thank you - both for confirming what we'd stumbled through, and for
helping fix a similar problem.  

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Mark Allender
Sent: 12 October 2005 18:57
To: Brough, Nicolas (Contractor); perforce-user at perforce.com
Subject: RE: [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,

I'm a little late on the subject having been out on vacation.  I've
that the following steps work every time in solving the pesky .NET
integration problems.  It's a pain, but after it's done for a solution,
shouldn't have trouble.  I can't tell you if it will work for your
particular case,  but please feel free to give it a go and let me know
it goes.  From our internal WIKI:

There is a known problem with the Perforce integration with the .NET
This problem could manifest itself in a number of ways including getting
errors that say "unspecified error" when opening the solution, or always
being asked to check out the solution and project files when opening the
project. You should be able to get completely set up right the first
time by
using the following steps: 

- go to explorer to the location where your solution file is 
- delete your .ncb and your .suo file. The .suo is hidden so you have to
show hidden files to see it if you aren't already doing that. Delete the
and suo files for any projects that you are having trouble with 
- go to file/open from source control 
- you may have to type in your perforce password. Make sure that client
your client name in the box. 
- use the tree view to browse to the solution file. Ask your lead if you
unsure where it is located in the depot 
- click ok and wait a long time 
- click on "overwrite" on the next dialog - this gets the solution from
Perforce and ignores any settings that you currently have 
- a windows explorer box comes up - choose the local solition file
(depending on what you opened a few steps ago). 
- At this point you are done. To make sure after the solution is all
quit .NET and then open the project as you normally would. Everything
be good to go. You should no longer have problems opening a solution
that is
under Perforce control. 
perforce-user mailing list  -  perforce-user at perforce.com

More information about the perforce-user mailing list