[p4] Perforce VS.NET integration - Thierry TM. Michalowski - com.perforce.perforce-user

5 messages in com.perforce.perforce-user[p4] Perforce VS.NET integration

From	Sent On	Attachments
Vivek Hebbar	08 Aug 2003 09:55
Robert Cowham	08 Aug 2003 16:06
Vivek Hebbar	08 Aug 2003 16:58
Robert Cowham	09 Aug 2003 01:09
Thierry TM. Michalowski	11 Aug 2003 00:59

Subject:	[p4] Perforce VS.NET integration
From:	Thierry TM. Michalowski (Thie...@echotech.ch)
Date:	08/11/2003 12:59:59 AM
List:	com.perforce.perforce-user

It looks like VSS does not understand the notion of a "root" , and allows you to map any part of a "project" to any location on your hard
drive. Perforce does not allow that directly (all of its files must reside under the
same root) BUT allows you to do it from within your client view, should you wish to do so.

I am not sure whether I'd like to be able to change a client view from within
the VS settings, though. It could look like a nice "integrated" idea, but I would fear some unexpected
effects if you're not completely aware of what you're doing (like, suddenly
moving your project from outside your root).

My 0.02? anyway... Cheers, Thierry Michalowski

-----Original Message----- From: Vivek Hebbar [mailto:hebbar at adobe.com] Sent: Saturday, August 09, 2003 1:59 AM To: perforce-user at perforce.com Subject: Re: [p4] Perforce VS.NET integration

I am able to set the root path for a client spec but that is not my problem. A client spec may have multiple projects. VS.NET needs a root path for each project within a solution in order to have the menu "Open project from Source Control" to work correctly. It mentions that this should be possible using the "Server Bindings" in the "Change Source Control" dialog. This is not possible as Perforce brings up the "Client Spec" dialog everytime I try to edit the bindings. I assume it must be something VSS implements and Perforce does not.

----- Original Message ----- From: "Robert Cowham" <robert at vaccaperna.co.uk> To: "'Vivek Hebbar'" <hebbar at adobe.com>; <perforce-user at perforce.com> Sent: Friday, August 08, 2003 4:06 PM Subject: RE: [p4] Perforce VS.NET integration

In Perforce you select the client workspace from the Plugin Connection Settings.

The client workspace has an associated root directory. However, setting up that root directory is something you must do using standard Perforce (p4win or command line) - in p4win see ClientSpec menu. Command line see "p4 help client"

Does that help?

Robert

-----Original Message----- From: perforce-user-admin at perforce.com [mailto:perforce-user-admin at perforce.com] On Behalf Of Vivek Hebbar Sent: 08 August 2003 17:56 To: perforce-user at perforce.com Subject: [p4] Perforce VS.NET integration

Microsoft Document the following for changing the root folder associated with a project.

1.. On the VS.NET IDE's File menu, point to Source Control, and then click Change Source Control. 2.. In the Change Source Control dialog box, click the Server Bindings column entry. When you click the Server Path column, an Ellipses (...) button appears. Clicking this button displays the Choose project from SourceSafe dialog box.

3.. In the Choose project from SourceSafe dialog box, select the project folder that you want to be associated with the unified root for the currently loaded solution, and then click OK But when I click on the Ellipses(...) button with Perforce as the Source Control for VS.NET I get a "Perforce Plugin Connection Settings" dialog with no option to change the root folder associated with a project. There is a local project path edit box but that seems to be disabled. I have project files in a Build folder under the root path. "Open from Source Control" retrieves all files under the root path when the project is opened. This makes the "Open from Source Control" fail as it takes the Build path as the root path. Any suggestions,

--------------------------------------------------------------

---------- Vivek Hebbar

Adobe Systems