2 messages in com.perforce.perforce-userPerforce & MS Visual Interdev| From | Sent On | Attachments |
|---|---|---|
| Sears | 07 Jan 1999 12:14 | |
| Mich...@perigis.com | 07 Jan 1999 13:00 |
| Subject: | Perforce & MS Visual Interdev |
|---|---|
| From: | Mich...@perigis.com (Mich...@perigis.com) |
| Date: | 01/07/1999 01:00:45 PM |
| List: | com.perforce.perforce-user |
Our "solution" to this was to bypass the interdev project entirely. We installed a web server on every engineers machine. We then took the web project and put all the files under the depot. A simple project was created on each users machine in the directory that the depot files would map to. (For reasons of naming semantics, the files were always under a directory structure "ProjectName/ProjectName_Local/..." ) We would then create a virtual root on the web server to those local files. The project is set to be in local mode, as well as working offline. In fact, I encourage people not to use the Interdev project explorer at all. It is much less confusing to use the P4Win app to checkout and submit, as well as to double-click and edit the files. The only thing that we use Interdev for now is for database browsing, and editing asp & html files, because of essential things like syntax coloring and IntelliSense.
When I talked to Microsoft about there lack of integration with Interdev and 3rd party tools, they were aware of it and were not aware of any plans to correct it.
------Original Message----- From: Sears, William D [mailto:William.Sears at navistar.com] Sent: Thursday, January 07, 1999 12:15 PM To: 'Long Doan'; Michael Bass; perforce-user at perforce.com Subject: RE: Perforce & MS Visual Interdev
We have tried this, and we could not get it to work. I think that you are answering a different problem than was asked. MS DevStudio will indeed work with Perforce doing what Long suggests - we use it for J++. However, MS Visual Interdev goes through the front page extensions on the web server (IIS 4 in our case). So IIS needs to be told to use Perforce instead of MS VSS. We were testing on a machine with IIS installed on the same machine as we were using Visual Interdev from and no source code control options appear at all if only Perforce is installed. If both VSS and Perforce are on the machine, nothing we could think of (moving all references in the registry or even copying the Perforce dll to the VSS ssccc.dll and ssapi.dll) would get it to work. IIS seems to be using ssapi.dll, but the Perforce dll was obviously not a replacement for that.
Has anyone managed to get this to work? Is there any progress being made? Is there any known workarounds other than having a version checked out locally AND on the server?
Thanks for your help.
William Sears William.Sears at navistar.com
------Original Message----- From: Long Doan [mailto:ldoan at mindq.com] Sent: Friday, October 30, 1998 2:14 PM To: Michael Bass; perforce-user at perforce.com Subject: Re: Perforce & MS Visual Interdev
(Windows only ...:) Look at the registry entry: HKLM\SOFTWARE\SourceCodeControlProvider\ProviderRegKey
If it points to "Software\Microsoft\SourceSafe", MS DevStudio will use source safe. If it points to "SOFTWARE\Perforce\p4", MS DevStudio will use perforce (assuming that you have already installed the p4scc dll).
Hope that helps, Long.
------Original Message----- From: Michael Bass <michael_bass at perigis.com> To: 'perforce-user at perforce.com' <perforce-user at perforce.com> Date: Friday, October 30, 1998 1:44 PM Subject: Perforce & MS Visual Interdev
I am trying to use Perforce and a Microsoft Visual Interdev development environment. Without getting into too much detail, Interdev does some strange file manipulation that is somewhat different than a traditional file based work environment. Worse, it seems locked into using Visual Source Safe. Does anyone have any experience or advice with this issue?
_____
Michael Bass
mailto:michael_bass at perigis.com