[p4] Tips for migrating Visual Studio.NET Web projects from VSS toPerforce?

[Douglas, Paul]

Thanks for the info.  I am new to Perforce.  A couple of follow-up
questions: 
Are you doing the unbind after you have installed the perforce client?
When I installed the perforce client on my machine, I said "Yes" to the
prompt asking if perforce should be the source control system.  After
doing this can I still open a solution and get latest from VSS?

When you say add code to perforce, how are you doing it?  
Setting up the workspace mappings seems to be the trick -- I am trying
to set them up similar to a perforce note at:
http://www.perforce.com/perforce/technotes/note064.html

Thanks again for your help.

-----Original Message-----
From: Matthew Janulewicz [mailto:MJanulewicz at greendotcorp.com] 
Sent: Thursday, May 25, 2006 5:14 PM
To: Douglas, Paul; perforce-user at perforce.com
Subject: RE: [p4] Tips for migrating Visual Studio.NET Web projects from
VSS toPerforce?

We're on the verge of doing this and I've been playing with it a lot the
past couple of months. The easiest (maybe not the best) way I found was
to:

Open a solution from VSS with the VSS bindings still active. Use the
'change source control' menu item to un-bind the whole thing from VSS.
This makes all those straggler .sccss etc. files 'neutral'. For me this
was easier than going through the whole code tree and trying to figure
out what files to delete, as when you bind back to Perforce some of them
are re-created anyway. But others are expected to already be there.

Add code to Perforce. Open the solution locally and re-bind to Perforce.

Perhaps the hardest thing for my developers to get a handle on has been
the concept of the workspace, and how it differs from 'working folders'
in VSS. I try to explain that the 'working folder' is now *not* bound to
the project is VSS, but to the workspace.

Making a sane looking workspace to use as a template for projects that
were originally in VSS may take a while because of this. You have to
have your workspaces lay down the files where the solution expects them
to be. A vast amount of re-arranging solutions and projects is in my
future. It's probably in yours, too. 

One more obstacle that I have not yet figured out an elegant solution to
is the 'shared file problem'. If you have them in VSS, be ready for a
headache. The main problem is that in a non-Web project in visual
studio, you can refer to files outside the directory the project is in,
so it's easy enough to consolidate all these shared files and point
non-web projects back to them. However, in a web project each file has
to be contained in the physical folder that the project file is in. No
external references. We have a set of files in VSS that are each shared
a zillion times, and wrangling this for web projects is going to be a
problem. The only thing I can think of is to make a workspace that has a
bunch of rather ugly lines in it for single files. Some big solutions
have several web projects, each of which have 5 or 6 references to these
shared files. Ugly.

Without re-architecting the whole lot to make the shared things truly
shared (in an assembly) you may be in for a struggle, like I think I
might be.


-Matt


-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Douglas, Paul
Sent: Thursday, May 25, 2006 2:34 PM
To: perforce-user at perforce.com
Subject: [p4] Tips for migrating Visual Studio.NET Web projects from VSS
toPerforce?

We have a complex Visual Studio Web project that is currently in VSS.
We migrated the files from VSS to a Perforce test server.  Now I am
trying to set it up so I can open the solution, check out, check in,
build etc. from Visual Studio.

Thanks

 

Paul Douglas

 

_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user