[p4] Perforce integration with VS .NET 2003

[Mark Allender]

I've found that the following set of instructions will always properly bind
a solution/projects to Perforce.  Of course, YMMV, but I've been using them
internally for a while with no problems.  It's a bit of a pain, but it
works, and once the instructions are followed, you can then open solutions
through a normal manner and have them properly bind to Perforce:

- 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 ncb
and suo files for any projects that you are having trouble with 
- start .NET - DON'T OPEN THE SOLUTION 
- go to file/source control/open from source control 
- you may have to type in your perforce password. Make sure that client has
your client name in the box. 
- use the tree view to browse to the solution file.
- 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 loaded,
quit .NET and then open the project as you normally would. Everything should
be good to go. You should no longer have problems opening a solution that is
under Perforce control.