Installing
Visual Source Safe
*-
VSS works in client server environment. Code base repository is places on the
server and all clients share that repository.
*-
Code is placed in the Shared Repository from where client or developer team accesses
the code repository and maintains it.
*-
You must need VSS admin module on the server and VSs client module on the
developer machine
*-
Firstly we make the server set up and make the code repository. By the VSS
admin module you cannot download the source code but we can setup the code
repository for the VSS users to work with.
*-
Install the Visual Source Safe 2005 both client and admin tools
on the server (150 files, 20 folder, 110 mb, 100 mb) Admin only manage the project database and the users of the vss database. The client
is used mange the project folders and files
and other operations after the data base is created. The client tools populate
the newly created project folders with the project files.
*-
Make the folder “VSS-Database” somewhere suitable on
the server and give permissions read or write or both for all the client PCs IP
of the different team members working on the projects. Initially we can go with
“Every One” with “Full Control”. This only single folder contains the information
about all the projects, users and their permission and backups of the different
projects.
13-
You need to share the VSS-Database folder on
the network so that the others can access the VSS data base file on the
network. As we give the IP we get the folder containing the VSS .ini file. Open
that file; Only authorized users can open and access the contents of the
VSS-Database folder.
*-
Start VSS-Admin, create New VSS Database, set the folder path to new created
folder “VSS-Database” on the server. Do next; this
will create files and folders in the “VSS-Database” and
also the .ini file. The clients will use VSS-Client to access the Server pc by
IP, then open “VSS-Database” folder and double click
the .ini file, it will prompt for the user name password, give it, If the WRITE
access is not given to the folder, the error comes for the user.
*-
By default the Admin, Default PC Name and Guest users are created in the VSS
database. You keep or delete them as necessary.
*-
Create new users for the VSS, and note down their passwords, and very simple
dialog is there for user permission and grants, read access or both read and
write access.
*-
Install the VSS-Clients on all client machines and access the VSS database and
give user name and password and access the code repository
*-
For each project, there could be one VSS database or there can be one VSS
database containing all projects related to a team. So database could be
project oriented or team oriented. In case of team-oriented database, a big
folder contains the different folders for different projects and the then
different teammates are given permissions to different projects. All team
members log in the same VSS database, and every user see the projects, files
and folders on which different users has access according to different projects
on which he is working.
*-
By default, the permissions wizards are disabled, following figures show how to
make them enabled.
*-
VSS client component is used to access the
code repository. You access the server PC by the IP and select the .ini files.
This .ini is the database file of the VSS server. You prompt for the username
password after that you are available with the list of projects or one project
hosted on that data base.
*-
VSS Sever component can make new project in one database file and make multiple
project available under one data base file
*-
You can make different Users for the VSS database and set their user name
passwords and set their preferences like the read, write, delete, access scope
to different files and folders, usually delete option is not given to the
client or developers.
*-
Normally you make a new blank folder on the hard disk, set the working folder
to that newly making folder and get the whole source code downloaded to that
newly made folder. This works fine when the whole source code is ok
*-
Sometimes, the project include the client specific files, those are not needed
by the clients, every client has its own version of files, flex projects has
this problem. The outer 3 files included in the workspace are not needed in the
downloaded files, every developer has its own version of these files, in this situation
it is good to make a blank project in this case, and import the subset of the application
in to it.
*-
Setting the Working folder actually synchronize the local copy of the project
with the server copy of the project, both projects have same folder structure,
setting the one root folder make the things ok for the rest of the directory
structure.
*-
After setting working folder the files are not read-only, you need to make them
read-only using the Window Explorer or you Check out all files and then Check
in all files. But this second way is not preferred. You may lose update files
on your local PC in the process of check in and check out. Second approach is
safe is the local copy and server copy are same and synchronized.
11-
Check out, draw something out mean download
the file for writing, Check in, draw
something in, and upload the file after doing work.
12-
For Java projects, only put the SRC folder on the
VSS all other folders and libraries will be exclusive to the
different clients.
*-
Copy the Flex and Java source code on the server.
*-
Make the following folders using the VSS-Client on the VSS server: “Java Projects” and the “Flex Projects”. Open
VSS-Client on the Server, create folder with same names as “Java Projects” and
the “Flex Projects”. Now drag and drop the contents of these folders from the
Window Explorer to the Projects Pane in the VSS-Client. After drag-drop, select
the recursive option selected. After copying, Flex and Java source code folders
should be deleted.
*-
When you drag and drop the files to the new project using the VSS Client, the
options come, set the dragged folder as the working folder for new project.
Select OK at this.
*-
Make Blank folders using the Window Explorer on
the clients: “Java Projects” and the “Flex Projects”
*-
Open VSS-Client on the clients, same folders will appear in the VSS database
those we have created on the server. Now map these folders to the folders
on the client machines using the “Set Working Folder” option. Now do
the recursive “Get Latest” for the root project folders. All is done.
*-
Sharing VSS files means, they are viewable in two different projects but VSS
maintains one copy internally. All check in and check outs are reflected in
both project. And files are available to the users of both projects and all
users can manipulate files according to their assigned rights and permissions.
*-
I think BRANCHING is the reverse of SHARING.
*-
Renaming a project on server cause loss of “Working Folder” settings for all
clients and they are needed to be set again.
