Software

Ask something
Discussion Locked

VSS - Visual Interdev integration

0 helpful
6 replies

by kkramesh 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have an IIS server where we have all our web sites running. We are using Visual Sourcesafe to manage version control. Visual sourcesafe is also installed in the same server. When we try to move the VSS database to another server machine, we are facing problems in Visual interdev. We are not able to change the sourcesafe connection to the new VSS database.
Is it possible to keep the web projects and VSS database in different machines. If so, how do we configure the existing web projects to look at the new VSS database ?

6 replies

by myjunk

Source Code Control in Microsoft Access 2000
Shawn McDowell
Microsoft Corporation

Revision Date: January 1999

For the latest information, see http://msdn.microsoft.com/officedev/default.asp.

Contents
Overview of Source Code Control Integration
Source Code Control Commands in Microsoft Access 2000
Changes to Microsoft Access Behavior
Objects Microsoft Access Puts Under Source Code Control
Limitations of Source Code Control in Microsoft Access 2000
Questions and Answers

Overview of Source Code Control Integration
Microsoft? Office 2000 Developer provides the Access Source Code Control add-in that integrates source code control into Microsoft Access using Microsoft Visual SourceSafe?.

By integrating source code controlinto Microsoft Access 2000, you can now work with a team of developers to build a Microsoft Access application and version objects. You can now:

See which objects are checked out.

Check out an object to control changes to it.

Check in an object so other developers can get your changes.

View a history of changes for each object or the entire database.

Visually compare differences between versions of an object.

Merge differences between different versions of an object.

Version objects and revert to a previous version of an object (even deleted objects).

Add new developers easily to your team who synchronize to the latest versions of all objects.
The Access Source Code Control add-in communicates with both Microsoft Access 2000 and the source code control application. While you work with Microsoft Access 2000, the source code control component lets you do things like add, check out, or check in Microsoft Access objects to the source code control project. Source code control integration with Microsoft Access is very similar to source code control integration with Microsoft Visual Basic?.

The Basic Model
One or more users

by gbworld

Unfortunately, this is a bit painful. In order to integrate on a different machine and have the users see the changes, you are going to have some growing pains.

First, check in all code and lock out all users from VSS. This ensures no changes during the move.

Next, make sure the latest code is on the new web server.

Next, integrate this web server with VSS. This is a bit involved, so check the MSDN documents on this. It is basically the same thing you did when the VSS database was on the same machine, but you are specifying a directory on another machine. This will set up the new VSS database.

Now, the pain. Developers will have to delete their old project and create a new one. Fortunately, this is more time consuming than painful.

Now, all developers should be synced to the new VSS database and web and be able to check in and check out.

Rule number 1. Developers only check out web pages (VID code) through VID. Never check out directly from VSS unless everyone is checking out from VSS. I wish the cooperation of the products was better, but it is not.

Greg

This discussion is closed to new replies.