SCCBridge project

10. Requirements, installation and sources.

This section discusses requirements and installation of BridgeServer web service, BridgeConsole, RepositoryExplorer applications and module that integrates SCCBridge project into the Visual Studio .NET 2003 IDE.

Requirements:: Since all of applications are written in C# and they use DIME messages, they require .NET Framework version 1.1 and Web Service Enhancement 2.0 for Microsoft .NET should be pre-installed on both the server and client machines. BridgeServer also requires IIS 5.0 or higher on the server. The applications were tested under Windows 2000/XP (Pro) and Windows Server 2003 , but they have to work properly also under other Windows OS where .NET Framework 1.1 and WSE 2.0 are installed.

Server-side setup:

To install the SCCBridge server you have to do the following:

Download Windows installer package for server.
On the computer where IIS 5 is installed, run the "SCCBridge server.msi ".
Read message on the first screen carefully and then click "Next" button.
Specify a virtual directory for the web service, by default it will has name BridgeServer.
Click the "Next" button. That's almost all you have to do.
On the next screen just click the "Next" button again.
When the installation is finished, click the "Close" button.

Please keep in mind the following:

path in Web.config has to point at SourceSafe database (exactly at srssafe.ini file). Take a look at "RepositoryPath" key.
since the access to SourceSafe is implemented using of COM+ component (SCCBridge COM+ application), so, you have to grant to the user under which this application runs the read/write/browse and modify access on the folder, where srcsafe.ini is placed (and on its subfolders too). By default the SCCBridge application is configured to use credentials of logged in user.
to access to SourceSafe database on the LAN do the following:
- Open "Component Services" MMC snap-in (Start/Settings/Control Panel/Administrative Tools/Component Services );
- Expand "Component Services", "Computers", "My Computer" and "COM+ Applications " nodes;
- Right click on "SCCBridge " application;
- Click "Properties " menu item.
- Specify user name and password on the "Identy" tab. The SCCBridge COM+ application will use this credentials to access to VSS database on the LAN.
Note: check that the provided user has full access to the temporary folder, returned by Test() method of the SCCBridge web service.
- Click OK. Do shutdown and then start of "SCCBridge " COM+ application.
- Change "RepositoryPath" in your web.config file appropriately, e.g.:

In order to test web service I've implemented the Test() method, which works through HTTP GET:

Open in a browser the following link: http://localhost/BridgeServer/Repository.asmx?op=Test . Replace please "localhost" by your server name.
Input a SourceSafe user name and password and click "Invoke" button.

When service was configured correctly then you will see the following message:

"Test passed. Support cryptography: yes, database path: <path to your database>, temp folder: <path to temp folder>."

Using of cryptography allows encrypting of user's password during login. To allow using of cryptography to ASPNET user you have to do either:

grant ASPNET user "Read & Execute" + "List folder contents" + "Read" rights on the following folder: "C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA"
or append ASPNET user to group "Users".

then you can change Web.config:

Client-side setup:

To install the SCCBridge client you have to do the following:

Download Windows installer package for client.
Run the "SCCBridge client.msi ". Read message on the first screen carefully and then click "Next" button.
Determines a folder to where client-side files will be installed. Then click "Next" button.
Click the "Next" button. That's almost all you have to do.
At the end of installation you have to specify the current "Source Code Control Provider", which will be used in Visual Studio .NET IDE.
When the installation is finished, click the "Close" button.

Please keep in mind that you can change back the current "Source Code Control Provider" at any time using of "SCCPSwitcher.exe" utility.