[p4] Problem with Microsoft DevStudio project files under Perforce control
timb at qualcomm.com
Fri Nov 24 10:23:55 PST 2000
P4Win allows you to set client file read status with a ClientSpec
option. Change "noallwrite" to "allwrite" and DevStudio should be happy.
At 09:24 AM 11/22/2000 +0100, Joel Conraud wrote:
>Im new to Perforce (in fact, Im currently evaluating it). I began to work
>with it and I appreciate it. I have just one worry for now: the source code
>I want to put under Perforce control includes C++ source files, C++ header
>files AND associated Microsoft DevStudio project files (*.dsp) and workspace
>files (*.dsw). When populating my perforce client workspace, all files are
>marked as read-only, including *.dsp ones. The problem is that devstudio
>doesnt like to open *.dsp files marked as such. A warning dialog box opens
>for each of them (I have more than 30 projects files
), warning me that
>DevStudio will not be able to save changes made in project settings.
>Furthermore, even if do not plan to change project settings during a
>DevStudio session, Perforce itself does it!, adding specific lines to SCC
>This behavior is annoying. The work arounds I envision for now are:
>After populating a client workspace with some *.dsp, ensuring that those
>files have read/write permissions (thus breaking one of the Perfore rules).
>Using c4 layer on top of perforce for ensuring every checkouted files,
>either being DSP or not, have read/write permissions.
>I would prefer if possible to stay near of Perforce natural way of working
>(read-only files by default).
>Any idea someone? I guess my problem should be common for people using
>Perforce on Windows, with DevStudio integration.
>PS: as Im currently evaluating Perforce, my main concern is how to explain
>this problem to the other developers in my company
when they are used to
>CVS checkout modules without any special operations to do after.
>Joel CONRAUD email: conraud at t-surf.com
>TSURF tel: (+33)(0)220.127.116.11.27
>The gOcad Company fax: (+33)(0)18.104.22.168.34
>perforce-user mailing list - perforce-user at perforce.com
More information about the perforce-user