Hello,

What would be the best design for setting up a develompment environment =
(I dont mean the IDE, but "a developer team").

Developer pc's have VS.Net installed locally
Projects are on a (file)-server

Should the solutions be created locally on every developer-pc or only =
once on the server?
If the latter: what happens if developer A is rebuilding a project and =
developer B is in the middle of editing that same project.

Up until now I have only used vs.Net locally (I've been working alone on =
my project) but I'm planning to expand and I'm (obviously) not shure how =
to setup a multi-developer environment.

TIA,

[quoted text, click to view]
Hello,

What would be the best design for setting up a develompment =
environment (I dont mean the IDE, but "a developer team").

Developer pc's have VS.Net installed locally
Projects are on a (file)-server

Should the solutions be created locally on every developer-pc or only =
once on the server?
If the latter: what happens if developer A is rebuilding a project and =
developer B is in the middle of editing that same project.

Up until now I have only used vs.Net locally (I've been working alone =
on my project) but I'm planning to expand and I'm (obviously) not shure =
how to setup a multi-developer environment.

TIA,

Michael

For starters, your going to need some sort of source code=20
control system for collaborative development. Look into Visual =
SourceSafe that comes with Visual Studio .NET Enterprise Architect =
Edition. It *may* come with Enterprise Developer as well, but I'm not =
sure either way.

--=20
Peter [MVP Visual Developer]

Hi Peter,

I think what you are looking for can be found in the doc located at the
link below. It discusses several different source code control scenarios
using VSS and VS .NET. This Patterns and Practices doc on MSDN is titled
"Team Development with Visual Studio .NET and Visual SourceSafe". Its
long, but well worth the read.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/
tdlg_rm.asp

Please let me know if you have any questions,

Brett Keown
Microsoft Support
brettke@online.microsoft.com

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

[quoted text, click to view]
Hello, Brett.
Did you mean this reply for Michael (the OP)?

Hi guys,

Thanks for your replies. I'm currently looking into SourceGears' Vault.
I do have an ent. arch. subscription, but I tend not to use vss because the
only comment I've read about it (until now) is negative (as in the latest
issue of 'code' or 'Visual Studio Mag' -> I'm not shure which-one).

I think I'll figure it out now.
I've also encoutered another url about this topic:
http://software.ericsink.com/scm/index.html

Regards,

Peter: Brett is OOF recently. I think his reply is for Michael. :)

Michael: The article "Team Development with Visual Studio .NET and Visual
SourceSafe" that Brett is very good on this topic. It introduces detailed
information on team environment setup on VSS. Every source control tool has
its advantages and disadvantages. This article could help you better
understand what VSS can bring to you.

Thanks very much.

Best regards,
Yanhong Huang
Microsoft Community Support

Get Secure! ¨C www.microsoft.com/security
Register to Access MSDN Managed Newsgroups!
-http://support.microsoft.com/default.aspx?scid=/servicedesks/msdn/nospam.as
p&SD=msdn

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

Hi Peter,

I indeed find the article very helpful.
Many of the items explained I practice by "trial and error" over the
years. It is nice to see that my implementations are correct 8-)

On the other hand starting now with a "team" (> 1) brought me some new
issues I didn't need before (working alone). The article is a very good
guideline in this issue.

Another link I found very helpful is
'http://software.ericsink.com/scm/index.html'. OK, it's a guy from
SourceGear but I think he's as neutral as possible.



Thanks to you all for the help.



Regards,



Michael

[quoted text, click to view]