Hi,
I am failing to make a cw 9.2 WorkSpace/Projects work correctly against
multiple Perforce client specs on the same and also across different
machines.
Perforce's latest scc plug-in, version 2003.2/56329, automatically added a
very usefull feature to msvc 7.1 solutions.
It allows one to bind clientspecs to projects.
(Just for the record, in .NET devstudio, a "workspace" is now called a
"solution" and a "solution" can contain many "projects". Thus a "solution"
is comparable to a CodeWarrior .cww "Workspace". Comparable, but certainly
not the same. I share a "solution" with my collegues but my findings seem
to
indicate that a .cww workspace is more of a personal entity. Also a
devstudio "project" is comparable to a codewarrior "project", but not
exactly the same - ehm, that just added to the confusion didn't it?)
This means that I can now have several clientspecs for the same source
branch on the same workstation without first having to trick devstudio by
switching defaults from the Perforce Windows client (updating the
notorious
Registry) before opening a different solution, or the same solution but
against a different clientspec.
After an initial configuration, I can simply open up the solution and
devstudio will automatically work against the correct Perforce clientspec.
This is a enormous improvement and was automatic with devstudio (.NET
20003
vc7.1 version). This last bit of information may be im****tant as it seems
to
indicate that the scc plug-in is itself resposible for making devstudio
much
more user friendly. In other words, it is unclear to me who is doing what.
Unfortunately, this does not work with CodeWarrior 9.2. As soon as I open
up
identical .mcp project files from another location (thus a different
Perforce client spec), on the same or on a different machine, I not only
loose *all* Version Control Settings but also get lots of out of date and
bogus file entries. This is an enormous nuisance. Currently, I am alone at
maintaining close to 80% of our msvc 7.1 code under mwcw 9.2, but I am
hoping this may change. However, unless I can have one of my peers
automatically inherit my latest .cww and .mcp changes, the chances are
very
slim.
What am I doing wrong?
How does cw 9.2 collaborate with the Perforce scc plug-in?
Who is doing what, and where are im****tant pieces of information stored
that
should be stored?
Apart from the actual source files, the .mcp project files and (under a
lot
of doubt) the .cww workspace file, are there any other files I should
submit
under source control?
Any clues much appreciated.
Sincerely,
Conrad Weyns.
|
