For this method, set the path to VSS Remoting in the New Repository dialog and click OK to complete the setup. The second method, for FogBugz On Demand users, is to use VSS Remoting to display diffs and logs. Be sure the FogBugz user in that IIS has permissions on the VSS files on that server as specified above. If this is not feasible for you, you can install a separate instance of FogBugz on IIS on the VSS machine, whose sole purpose is to read VSS files and show you the diffs and logs. The first is to set up VSS to run on the same machine as FogBugz For Your Server so that you can use our internal tools. There are two ways to have FogBugz link to checked-in files directly from cases. You can change this setting later by clicking the Edit icon next to the repository on the Gear (or Admin) > Source Control page. Before you close the dialog, choose whether you want FogBugz to provide links to your check-ins. Instructions for setting it up are provided below. In the resulting dialog, download the script necessary to get Visual Source Safe (VSS) to transmit changes to FogBugz. In the resulting dialog, select VSS as the type and give the repository a display name. To do so, log into FogBugz as an administrator and go to Gear icon (or Admin) > Source Control. The starting point for setting up source control integration is to create the repository in FogBugz. Getting FogBugz to display VSS diffs and logs.Getting VSS to transmit changes to FogBugz.There are two aspects to setting up FogBugz Visual SourceSafe integration: 4 Entering case numbers in Visual SourceSafe.3 Getting VSS to transmit changes to FogBugz.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |