Re: Suggestions for tools, processes for new team

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Ron Ruble (raffles2_at_att.net)
Date: 01/07/05 

Date: Fri, 07 Jan 2005 15:48:09 GMT

Kevin Yu [MSFT] wrote:
> Hi Ron,
>
> First of all, I would like to confirm my understanding of your issue. From
> your description, I understand that you need some suggestions on bug
> tracking, project managedment and source control tools. If there is any
> misunderstanding, please feel free to let me know.
>
> Based on my experience, VSS is of course the best choice for your to do
> source control. It can be integrated with VS.NET IDE perfectly.

Others have commented on SourceSafe's limits. I don't hate
it*, but I'm not wedded to it. I don't care for integrating
an RCS into the IDE, but others like it.

> For bug
> tracking and project management, you can try to use Bugzilla. Bugzilla is
> server software designed to help you manage software development. For more
> information, please check the following link.
>
> http://www.bugzilla.org/

Looked at it, never used it. Thanks.

> In the next version of .NET, there will be many tools like that integrated
> in Visual Studio Team System. For more information, please check the
> following link
>
> http://lab.msdn.microsoft.com/vs2005/teamsystem/

I'll check it out, thanks.

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

* Actually, I'm kind of fond of it. I first used SourceSafe
on a project after a project on which I fought with a couple
of teams of developers who absolutely would not use a revision
control system without being hammered on the head every day.

Constantly whining about the inconvenience.

By contrast, I have run into exactly 2 developers in the
last 10 years who failed to use SourceSafe. In both cases,
a little one on one coaching resolved the problem (one
developer had never used an RCS, and just needed training).

A great tool is no good if no one uses it, and I've been
in a lot of shops with great tools no one uses. SourceSafe,
in my experience, gets used. I'll use almost anything,
personally.

Relevant Pages

  • Re: Visual Studio 2005 Web Site <-> Visual Source Safe Problems...
    ... small shop with individual developers working on Windows XP Pro and then ... SourceSafe and did a recursive get of the project to a directory ... Sounds like amateur hour again? ... VS2005 built-in Cassini web server, this will avoid any issues with IIS, ...
    (microsoft.public.vsnet.general)
  • RE: Sharing VS.NET projects (use FTP?)
    ... developers so that they can modify code and build them. ... I think we can use Visual Sourcesafe to manage code in team ... When the project is put on the Sourcesafe server, ... third-party tool to access Sourcesafe server via Internet. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Visual SourceSafe 2005 and MS Access 2003
    ... "Paul Shapiro" wrote: ... Sourcesafe, choose to create a new db from Sourcesafe. ... Other developers can either recreate their local db from ... database into VSS can use the VSS functionality within MS Access. ...
    (microsoft.public.vstudio.sourcesafe)
  • Source control doesnt work after upgrading from FP2000 to 2002
    ... we upgraded her MS FrontPage from 2000 ... Since the upgrade, ... SourceSafe 6.0 for version control is no longer working. ... external source control via SourceSafe. ...
    (microsoft.public.frontpage.client)
  • Partitioned Single Solution Model
    ... I have been reading the "Team Development with Visual Studio .NET and ... Visual SourceSafe" guide on MSDN. ... The "Partitioned Single Solution Model" ... other developers to work on Project C in another Solution. ...
    (microsoft.public.vstudio.sourcesafe)