Charlotte Foust
cfoust at infostatsystems.com
Thu Oct 27 10:26:37 CDT 2005
We use VSS with .Net in our shop with multiple developers and I don't feel that it's any more trouble than it was in Access ... Usually. The biggest problem we had was with a non-existent object that had once existed and been deleted but it was still referenced in the project file somehow. Once we manually edited the project file, the problem disappeared. The other problem I've seen is that references between projects can occasionally cause an extraneous reference to the current project to be inserted, which then needs deleting before the project is checked back in, since it won't compile otherwise. The approach I use is to select Add-->New Item, which automatically checks out the project. I add a shell form, class, whatever, and check the project back in. Then I check out just the new object and work on it. Another approach might be to create the object outside source safe in another solution and then use Add-->Existing Item to include it in the VSS project. We break our solution up into multiple projects for each part: data, data providers, Nunit tests, Configuration, Reports, UI, etc. That way checking out one project to add an object doesn't create such a hassle for everyone. Once the object is checked into the project, you needn't check the project out again unless you need to add or delete something else. I don't recall the problem of not being able to see a new object, but it is most effective to close all open objects before doing a Get Latest and then do a build or rebuild of the solution. Charlotte Foust -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Steve Capistrant Sent: Thursday, October 27, 2005 8:10 AM To: Access Developers discussion and problem solving Subject: [AccessD] VSS misbehaving We're having a growing number of problems using Visual Source Safe. Used with Access over the years, it presents occasional problems, not terrible. But our problems have amplified since applying it to .NET projects. 1. When one user creates a new object and checks it in, other users can't see it (after attempting to Get Latest Version). Yet the object is clearly seen in the Source Safe project itself. 2. Adding or deleting an object to a VB.NET project seems to require that the person have the entire project checked out to them (unlike the way it works in Access). Has anyone else encountered these things? If so, are there solutions? Or...if these are just known VSS hassles, do you have any suggestions about other source control solutions that work well with .NET? Thank you! Steve Capistrant scapistrant at symphonyinfo.com Symphony Information Services 7308 Aspen Lane North, Suite 132 Brooklyn Park, MN 55428 763-391-7400 www.symphonyinfo.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com