Sharing VS.NET projects (use FTP?)

[cpnet]

I couldn't find the 'right' group to post this, so I thought I'd try it
here. If you can suggest a better newsgroup to post this in, please let me
know.

I trying to figure out if there's an easy way to share VS.NET code (for an
ASP.NET app) between 2 remote developers. In general only one developer
will be changing the code, but I'd like both developers to be able to
compile and run the code on their machines. The code shouldn't run on the
remote server, only on the developer machines.

We are a small company, and don't have a lot of infrastructure. We have a
hosted account on an NT 4 server (no ASP.NET support), and I was hoping that
I could share the code with FTP to this server, but I can't figure out how
to get this to work. (Since this is a hosted account I can't add ASP.NET or
VSS). With "Copy Project" or "Save As" in Visual Studio, I can connect to
my FTP site, but can't seem to upload any files (though I am able to create
folders, so I should have any necessary permissions).

From what I've read, it's going to be a bit tedious to e-mail projects back
and forth (unless I misunderstand the process) so I'm looking for an easier
way to share the projects' code.

Thanks

[Kevin Yu [MSFT]]

Hi cpnet,

First of all, I would like to confirm my understanding of your issue. From
your description, I understand that you need to share code between two
developers so that they can modify code and build them. If there is any
misunderstanding, please feel free to let me know.

In this case, I think we can use Visual Sourcesafe to manage code in team
development. When the project is put on the Sourcesafe server, we can check
out and check in them to modify code and submit changes. Visual Sourcesafe
can integrate with Visual Studio.NET.

When the client computers and the server are in the same LAN, it will be
easy to access the server. If the developers are out of office, they can
use VPN or RAS to connect to office and access Sourcesafe as if they are in
office. If no VPN or RAS service is available, they can also use some
third-party tool to access Sourcesafe server via Internet.

For more information about sourcesafe, please check the following link:

http://msdn.microsoft.com/vstudio/previous/ssafe/

For information about Team Development with Visual Studio .NET and Visual
SourceSafe, please check:

http://msdn.microsoft.com/library/de...us/dnbda/html/
tdlg_rm.asp

Here is a third-party add-in for accessing VSS through Internet.

http://www.sourcegear.com/sos/

HTH. If anything is unclear, please feel free to reply to the post.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

[cpnet]

Hi Kevin,

I've seen the Visual SourceSafe stuff, but as I mentioned in my post, the
only server I have that is accessible to both developers is hosted by a 3rd
party. I have http and ftp access to this server, but that's it. The
server does not have ASP.NET support, and I can't install Visual Source Safe
(or any other software) on it - other than ASP 2.0 scripts.

I do use SourceSafe locally, but I'm not able to provide a VPN/RAS
connection to my own LAN at this point.

I'm looking for a way to share the source code (other than e-mailing it back
and forth, reconfiguring it each time), that doesn't require anything but
FTP or HTTP access to the common server.

Chris

[Kevin Yu [MSFT]]

Hi Chris,

Since you have to share it on a server on which only FTP and HTTP is
provided. I think you can only copy the files needed for the project and
share them on the FTP server by uploading.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."

[cpnet]

Ok.

Thanks.

"Kevin Yu [MSFT]" <v-****@online.microsoft.com> wrote in message
news:4a**************@cpmsftngxa10.phx.gbl...

Hi Chris,

Since you have to share it on a server on which only FTP and HTTP is
provided. I think you can only copy the files needed for the project and
share them on the FTP server by uploading.

Kevin Yu
=======
"This posting is provided "AS IS" with no warranties, and confers no
rights."