150 likes | 781 Views
Why Use Microsoft Visual SourceSafe with Microsoft Visual InterDev ... The Web Application and Visual SourceSafe Server Reside on the Same Server ...
E N D
Slide 1:Troubleshooting Integration of Microsoft Visual InterDev 6.0 and Visual SourceSafe 6.0 Ray DixonDeveloper Support ProfessionalMicrosoft Corporation
Slide 2:Overview
Why Use Microsoft® Visual SourceSafe™ with Microsoft Visual InterDev™? How InterDev Communicates With the Web Server Common Scenarios for Source Control Permissions Requirements Common Problems and Resolutions Other Resources
Slide 3:Why Use SourceSafe?
De-conflict Code Changes Within a Team Provide a History
Slide 4:How InterDev Communicates with the Web Server
Microsoft FrontPage™ Server Extensions Security NTLM Basic Authentication
Slide 5:Common Scenarios for Source Control With InterDev
The Web Application and Visual SourceSafe Server Reside on the Same Server Visual SourceSafe Residing on a Server Other Than the One With the Web Application
Slide 6:Permissions Requirements
Web Permissions (FPSE Permissions) UNC Share Permissions Visual SourceSafe Accounts
Slide 7:Permissions
Slide 8:Common Problems & Resolutions
Slide 9:Common Problems and Resolutions
This occurs when the user doesn’t have Change permissions to the VSS file share If you don’t have a local copy, clicking Yes will produce the same message with an OK button
Slide 10:Common Problems and Resolutions
If the user doesn’t have Change permissions to the VSS share, they will be able to open the project and create new files, and those files will appear on the Web project. However, they will not be under source control. If the user without permissions tries to then add the new page to source control, this error will appear:
Slide 11:Common Problems and Resolutions
If the user doesn’t have an account in VSS Admin and tries to check out a file, the error below will appear. If the user doesn’t have an account in VSS Admin and creates a new file, it will be part of the project, but not under source control.
Slide 12:Common Problems and Resolutions
Also, some files may not appear to be under source control to the user without the VSS Admin account when, in fact, they are. When the user tries to save changes to the file up to the project on the Web server, the error below will come up. If the user has neither a VSS Admin account nor Change permissions to the VSS Share and tries to open a file, the “Access Denied” error to Um.dat will come up.
Slide 13:What Are Glyphs and How Do I Read Them?
Slide 14:Other Resources
Q187648 - INFO: FrontPage and VID Local Files on a Controlled Web Q186320 - INFO: Determining if a Web Project is Source Code Controlled Q183735 - PRB: Saving a File in FrontPage Does a Silent Checkin Q171116 - HOWTO: Enable VSS Integration with FrontPage and Visual InterDev Q166259 - INFO: Visual Interdev/Visual SourceSafe Integration Discussion Q165831 - PRB: Anonymous User in NT Admin Group Breaks Source Control Q191289 - HOWTO: Enable Event Error Logging for FrontPage 98 & SourceSafe Q162232 - PRB: Server Error: Visual Source Safe Failure Q158914 - PRB: Web Root Busy Opening Source-Controlled Web Q199003 - PRB: Visual InterDev Permissions for Users Who Are Not Local Admins