Some developers believe that source-code control is a necessary evil. Yet, source-code control is a sound business practice supporting your software development process. In this article you will be shown a real-world step-by-step approach to effectively using Microsoft® Visual SourceSafe® as your source-code control mechanism. In this article, you will be shown how to create a new SourceSafe database, how to check in and check out files, and how to create releases using labels. Take a look about how to use Visual SourceSafe for ASP.NET
No one person can master all the languages, techniques, tools, and processes required to create world-class software applications rapidly and consistently. That's why most professional developers work in teams. Efficiency and economy demand it. In the same way, most software development teams adopt a parallel development methodology that liberates individuals from the constraints of serial development, where one developer completes one task before the next can begin another. Parallel development allows multiple individuals to work in isolation, safely developing the same, or different parts and versions of a project at the same time. To realize the benefits of parallel development, teams must implement processes so that project contributors can expeditiously, incrementally, and sometimes automatically resolve small conflicts before they grow into big ones. Visual Studio .NET can improve a team's ability to cooperate by ensuring adequate developmental isolation.
By Edge Pereira
