A friend and I are working on re-creating the site that the book: ASP.NET 
Website Programming

We were wondering what is the best way  for us to work on the project 
together.

He has the project loaded on his server but how do we work on it together 
sharing access to the same project?

i.e. some feature in Visual Studio to access the code remotely.

Since this is a requirement of the project.

 
Appreciate any answer?

Check for a .NET web hosting company that allows the 
proper configuration of Frontpage settings to allow 
you to place your web project on a remote server and 
edit locally using VS .NET.

The only problem is most hosting companies don't have 
integrated Visual SourceSafe so you wouldn't be able 
to guarantee that your friend won't be editing the 
same page you're editing.

--- Original Message ---
From: dstruve@m...
To: "Website Programming with ASP.NET" 
<aspdotnet_website_programming@p...>
Subject: [aspdotnet_website_programming] How to 
Develop Remotely

>A friend and I are working on re-creating the site 
that the book: ASP.NET 
>Website Programming
>
>We were wondering what is the best way  for us to 
work on the project 
>together.
>
>He has the project loaded on his server but how do we 
work on it together 
>sharing access to the same project?
>
>i.e. some feature in Visual Studio to access the code 
remotely.
>
>Since this is a requirement of the project.
>
> 
>Appreciate any answer?
>
>to unsubscribe send a blank email to leave-
aspdotnet_website_programming-1076044R@p...

dstruve@m... wrote:
> We were wondering what is the best way  for us to work on the project
> together.
> 
> He has the project loaded on his server but how do we work on it
> together sharing access to the same project?
> 
> i.e. some feature in Visual Studio to access the code remotely.
> 
> Appreciate any answer?

I can think of four approaches.  I haven't used any with .NET so this is
NOT first hand.
1)  If your VS license includes Source Safe (SS) you could use that.  I
believe there are issues if a connection goes down while things are
updating and remerging after a project "fork" may have issues.  (Other
products license SS for example some Office developer editions have it
so there may be a license lying around!) 
2)  I know some people swear by CVS even for .NET projects.  I guess you
can get it at SourceForge.  My very limited experience is that I found
the command line version easy to use but a "GUI front end" that I tested
went unused when I couldn't figure it out within a few minutes.
3)  Use the "ZIP net" approach.  Mr A. codes then zips the whole
project.  Miss B. unzips codes the unzipped project, rezips and sends it
back.  Each person responsible for code testing, so Unit tests within
the project are a great idea.
4)  Create a web site with the directory structure.  You each grab bits
(say by ftp) and manage updates manually on your own systems.  (Email
contact etc.)

Comments.
1)  Learning how to use Source Safe or CVS has some learning curve.
2)  For a small project human co-ordination may be a good idea.
3)  In a situation where I wasn't sure of people's capabilities I'd
choose 3 first followed by 4.

Hope that helps.

Mike Gale, Decision Engineering (NZ) Ltd.