Nick
nick at frasiervan.com
Thu Oct 27 10:40:45 CDT 2005
For .Net projects there is a project file, *.csproj for C# or *.vbproj for VB. Two things to look for. First - Add new files both to the *.vbproj file, check it out and check it in, and add the file to VSS. Second - By default the .NET IDE only shows files that are in the vbproj. You can in the solution explorer choose to "view all files" which shows the entire contents, not just what is listed in the vbproj file. You may see the file here if it was not added to the vbproj. Things get a little trickier if you've included the various vss and .Net integration files. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Steve Capistrant Sent: Thursday, October 27, 2005 10: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