[p4] Problem with Microsoft DevStudio project files under Perforce control
jdarnold at buddydog.org
Fri Nov 24 17:49:03 PST 2000
> 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
To begin with, Microsoft says to *not* put .dsw files under source code control.
They are machine and user specific files that should not be shared between programmers.
It can be a pain, as there are some settings in there you wish were shared and
some that you don't want, but that's the way to go.
> 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.
But why do you open a .dsp file? You only do this when you are doing a change
of settings, and in that case you certainly do need to check out the file. Other
than that, when you open the .dsw file, it gets the .dsp file and you can work
just fine with it as a read-only file.
> Furthermore, even if do not plan to change project settings during a
> DevStudio session, Perforce itself does it!, adding specific lines to SCC
Hmm, I don't see that, but maybe once you make the change once, you don't have
to worry about it.
| Jonathan Arnold (mailto:jdarnold at buddydog.org) |
| Havas Interactive HyperStudio Engineer |
| http://www.buddydog.org http://www.hyperstudio.com |
The optimist proclaims we live in the best of all possible
worlds, the pessimist fears this is true. - James Branch Cabell
More information about the perforce-user