|
| Here's my problem:
I manage a web based (vb) VS development environment with 6 +
developers & separate environments (and servers) for a single project:
#1. Local (Each developer has their own)
#2. Master Development Web Server
#3. Stage
#4. Production
I've already successfully copied applications from #1 to server #2,
using vs's copy project functionality (after building the entire
project). Moving this to #3 and #4 is simple if im moving the entire
project.. but in our situation this will not be practical.
My problem is a classic development issue when large projects are
shared amongst multiple developers. We have many cases where we need
to copy single files, and/or blocks of code from one environment to
another.
With classic ASP, this was not a big problem. When we wanted to post
specific changes from server #1 to server #2, we would simply check
the file in. Rarely did we have code that was not ready on #1 in the
same file... when we did we'd comment out the code that wasn't ready,
check it in, then uncomment the code to finish it.
Now on server #2, there are situation where we have changes which
aren't ready but share the same file as changes that are ready to be
moved onto server #3.
With Classic ASP, we would use Araxis Merge (a file compare/merge
program) to compare the different environments, and move "ready"
blocks of code -- or whole files throughout the stage and production
environments.
I'd like to do this now with our new .NET environments as well. But
heres the kicker:
1. I dont want to have to install vs on each server.
2. When the projects make it to production (server #4) I don't want
source code in production.
I thought of using vbc.exe to compile ready source on server #3.. but
im thinking there might be better ways of getting this done. If this
is the right way to go, suggestions for compiling vs projects manually
would be helpful.
Any help/suggestions/criticisms/slaps would be greatly appreciated.
TIA
-JD
|
|