DOCSLIB.ORG

Using Visual Sourcesafe – File Diff, Please Click Here

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Using Visual Sourcesafe – File Diff, Please Click Here by Kevin Gao CEO, Architect of Dynamsoft www.dynamsoft.com Introduction _________________________________________________________ 4 What is VSS? ________________________________________________________ 5 Market position _______________________________________________________ 6 What can VSS do? ____________________________________________________ 7 History preserving _____________________________________________________________ 7 File Difference _________________________________________________________________ 8 Project/Folder Difference _______________________________________________________ 9 Easy Collaboration ____________________________________________________________ 10 Several Important Concepts ___________________________________________ 12 VSS Database/Repository _____________________________________________________ 12 Working Folder _______________________________________________________________ 12 Master Copy and Local Copy ___________________________________________________ 12 Basic operations ____________________________________________________ 13 Add _________________________________________________________________________ 13 Get _________________________________________________________________________ 14 Check Out ___________________________________________________________________ 15 Check In _____________________________________________________________________ 16 Some Screenshots___________________________________________________ 17 Working folder ______________________________________________________ 19 Working folder introduction _____________________________________________________ 19 Setting working folder _________________________________________________________ 19 Working folder is inheritable ____________________________________________________ 21 Clear working folder ___________________________________________________________ 21 Add operation of SourceSafe __________________________________________ 22 Add introduction ______________________________________________________________ 22 Differences between SourceSafe 6 and 2005 ____________________________________ 22 Store only latest version _______________________________________________________ 23 File type filter _________________________________________________________________ 25 Binary or not _________________________________________________________________ 28 Get Latest __________________________________________________________ 32 Get Latest Version Basics _____________________________________________________ 32 How does VSS determine if our local copy is the latest version? ____________________ 33 Build tree ____________________________________________________________________ 34 Set file time __________________________________________________________________ 35 Replace writable ______________________________________________________________ 36 Lock-Modify-Unlock or Copy-Modify-Merge ______________________________ 38 The details of Lock-Modify-Unlock mode: ________________________________________ 38 The details of Copy-Modify-Merge ______________________________________________ 38 Icons for different checkout modes ______________________________________________ 39 How to choose the Lock-Modify-Unlock or Copy-Modify-Merge mode _______________ 40 Check Out __________________________________________________________ 42 Check out basics _____________________________________________________________ 42 1 Recursive, Build tree, Replace writable and Set file time ___________________________ 43 Allow multiple checkouts _______________________________________________________ 43 File Diff ____________________________________________________________ 44 Why File Diff _________________________________________________________________ 44 What File Diff can do __________________________________________________________ 44 How File Diff works ___________________________________________________________ 46 Example of File Diff ___________________________________________________________ 46 File Merge __________________________________________________________ 48 File Merge Introduction ________________________________________________________ 48 How merge is performed_______________________________________________________ 48 Example of merge ____________________________________________________________ 49 Four scenarios that merge may be performed ____________________________________ 51 Project Diff _________________________________________________________ 54 Why Project Diff ______________________________________________________________ 54 How to Launch Project Diff _____________________________________________________ 54 Project Diff Results ___________________________________________________________ 55 VSS in Visual Studio 2005 & 2008 _______________________________________ 57 Choosing SourceSafe as the SCC Provider in Visual Studio _______________________ 57 Adding Solution into Source Control of SourceSafe _______________________________ 58 Performing SourceSafe Operations in Visual Studio _______________________________ 58 Changing Source Control Binding _______________________________________________ 60 Pending Checkins Window _____________________________________________________ 61 Viewing Source Control Message _______________________________________________ 61 Share ______________________________________________________________ 62 Why Share ___________________________________________________________________ 62 How to Share file(s) ___________________________________________________________ 62 How to Find the Share Links ___________________________________________________ 64 How Project Share is performed in VSS _________________________________________ 65 Switching Visual Studio projects from SourceSafe to other SCC providers _____ 66 For Visual Studio 2005/2008 ___________________________________________________ 66 For Visual Studio .NET 2003/Visual Studio 6.0 ___________________________________ 69 Branch ____________________________________________________________ 74 Introduction to Branch _________________________________________________________ 74 Why Branch __________________________________________________________________ 74 How to Branch _______________________________________________________________ 75 How to Track Different Branches _______________________________________________ 77 Cloak ______________________________________________________________ 79 Why Cloak ___________________________________________________________________ 79 To Cloak a Visual SourceSafe Project ___________________________________________ 79 How Cloak Works _____________________________________________________________ 81 Introduction to Microsoft Source Code Control Interface (MSSCCI) ____________ 83 Microsoft Source Code Control Interface (MSSCCI) Registry Entries ___________ 84 MSSCCI Registry Structure ____________________________________________________ 84 2 How to Edit/View the Registry __________________________________________________ 87 Improvement in Visual Studio 2005 and 2008 ____________________________________ 87 Label ______________________________________________________________ 88 Label Introduction _____________________________________________________________ 88 How to Label a File/Project ____________________________________________________ 88 How to Modify a Label _________________________________________________________ 90 How to Get Files/Projects by Label ______________________________________________ 91 Scenarios When Label May Be Performed _______________________________________ 92 Integrating VSS with Access 2007_______________________________________ 93 Integrating VSS with Access 2003_______________________________________ 98 Integrating VSS with SQL Server 2008 __________________________________ 105 Integrating VSS with SQL Server 2005 __________________________________ 108 Integrating VSS with Dreamweaver ____________________________________ 110 Integrating VSS with Flash ____________________________________________ 113 How to manage users _______________________________________________ 119 Integrating VSS with Visual C++ 6.0 ____________________________________ 121 Integrating VSS with Visual Basic 6.0 ___________________________________ 126 Integrating VSS with PowerBuilder _____________________________________ 132 How to backup & restore VSS DB ______________________________________ 136 To archive a SourceSafe database: ____________________________________________ 136 To restore the projects from an archive file: _____________________________________ 139 A Free Tool to Manage the MSSCCI Provider _____________________________ 143 Pin _______________________________________________________________ 144 Show History ______________________________________________________ 147 Show History Basics _________________________________________________________ 147 How to view the history of an item _____________________________________________ 147 History Explorer _____________________________________________________________ 148 Share an old version of project ________________________________________________ 150 How to Manage Security _____________________________________________ 152 Introduction _________________________________________________________________ 152 Managing project level security ________________________________________________ 152 How to version control SQL Server Stored Procedures with Visual Studio 2003_ 157 3 Introduction SourceSafe / VSS is a version control tool used by many Windows developers. I started to use SourceSafe in 1995. Before
Load more

Recommended publications
  • Pragmatic Version Control Using Subversion
    What readers are saying about Pragmatic Version Control using Subversion I expected a lot, but you surprised me with even more. Hav- ing used CVS for years I hesitated to try Subversion until now, although I knew it would solve many of the shortcom- ings of CVS. After reading your book, my excuses to stay with CVS disappeared. Oh, and coming from the Pragmatic Bookshelf this book is fun to read too. Thanks Mike. Steffen Gemkow Managing Director, ObjectFab GmbH I’m a long-time user of CVS and I’ve been skeptical of Sub- version, wondering if it would ever be “ready for prime time.” Until now. Thanks to Mike Mason for writing a clear, con- cise, gentle introduction to this new tool. After reading this book, I’m actually excited about the possibilities for version control that Subversion brings to the table. David Rupp Senior Software Engineer, Great-West Life & Annuity This was exactly the Subversion book I was waiting for. As a long-time Perforce and CVS user and administrator, and in my role as an agile tools coach, I wanted a compact book that told me just what I needed to know. This is it. Within a couple of hours I was up and running against remote Subversion servers, and setting up my own local servers too. Mike uses a lot of command-line examples to guide the reader, and as a Windows user I was worried at first. My fears were unfounded though—Mike’s examples were so clear that I think I’ll stick to using the command line from now on! I thoroughly recommend this book to anyone getting started using or administering Subversion.
    [Show full text]
  • Version Control 101 Exported from Please Visit the Link for the Latest Version and the Best Typesetting
    Version Control 101 Exported from http://cepsltb4.curent.utk.edu/wiki/efficiency/vcs, please visit the link for the latest version and the best typesetting. Version Control 101 is created in the hope to minimize the regret from lost files or untracked changes. There are two things I regret. I should have learned Python instead of MATLAB, and I should have learned version control earlier. Version control is like a time machine. It allows you to go back in time and find out history files. You might have heard of GitHub and Git and probably how steep the learning curve is. Version control is not just Git. Dropbox can do version control as well, for a limited time. This tutorial will get you started with some version control concepts from Dropbox to Git for your needs. More importantly, some general rules are suggested to minimize the chance of file losses. Contents Version Control 101 .............................................................................................................................. 1 General Rules ................................................................................................................................... 2 Version Control for Files ................................................................................................................... 2 DropBox or Google Drive ............................................................................................................. 2 Version Control on Confluence ...................................................................................................
    [Show full text]
  • Microservices and Monorepos
    Microservices and Monorepos Match made in heaven? Sven Erik Knop, Perforce Software Overview . Microservices refresher . Microservices and versioning . What are Monorepos and why use them? . These two concepts seem to contradict – why mix them together? . The magic of narrow cloning . A match made in heaven! 2 Why Microservices? . Monolithic approach: App 3 Database Microservices approach . Individual Services 4 DB DB Database Versioning Microservices . Code . Executables and Containers . Configuration . Natural choice: individual repositories for each service Git . But: • Security • Visibility • Refactoring • Single change id to rule them all? 5 Monorepo . Why would you use a monorepo? . Who is using monorepos? . How would you use a monorepo? 6 Monorepos: Why would you do this? . Single Source of Truth for all projects . Simplified security . Configuration and Refactoring across entire application . Single change id across all projects . Examples: • Google, Facebook, Twitter, Salesforce, ... 7 Single change across projects change 314156 8 Monorepos: Antipatterns User workspace User workspace 9 Monorepos – view mapping User workspace . Map one or more services . Users only access files they need . Simplified pushing of changes 10 What does this have to do with Git? . Git does not support Monorepos • Limitations on number and size of files, history, contributing users • Companies have tried and failed . Android source spread over a thousand Git repositories • Requires repo and gerrit to work with 11 How can we square this circle? https://en.wikipedia.org/wiki/Squaring_the_circle 12 Narrow cloning! . Clone individual projects/services . Clone a group of projects into a single repo 13 Working with narrowly cloned repos . Users work normally in Git . Fetch and push changes from and to monorepo .
    [Show full text]
  • Version Control – Agile Workflow with Git/Github
    Version Control – Agile Workflow with Git/GitHub 19/20 November 2019 | Guido Trensch (JSC, SimLab Neuroscience) Content Motivation Version Control Systems (VCS) Understanding Git GitHub (Agile Workflow) References Forschungszentrum Jülich, JSC:SimLab Neuroscience 2 Content Motivation Version Control Systems (VCS) Understanding Git GitHub (Agile Workflow) References Forschungszentrum Jülich, JSC:SimLab Neuroscience 3 Motivation • Version control is one aspect of configuration management (CM). The main CM processes are concerned with: • System building • Preparing software for releases and keeping track of system versions. • Change management • Keeping track of requests for changes, working out the costs and impact. • Release management • Preparing software for releases and keeping track of system versions. • Version control • Keep track of different versions of software components and allow independent development. [Ian Sommerville,“Software Engineering”] Forschungszentrum Jülich, JSC:SimLab Neuroscience 4 Motivation • Keep track of different versions of software components • Identify, store, organize and control revisions and access to it • Essential for the organization of multi-developer projects is independent development • Ensure that changes made by different developers do not interfere with each other • Provide strategies to solve conflicts CONFLICT Alice Bob Forschungszentrum Jülich, JSC:SimLab Neuroscience 5 Content Motivation Version Control Systems (VCS) Understanding Git GitHub (Agile Workflow) References Forschungszentrum Jülich,
    [Show full text]
  • Distributed Revision Control with Mercurial
    Distributed revision control with Mercurial Bryan O’Sullivan Copyright c 2006, 2007 Bryan O’Sullivan. This material may be distributed only subject to the terms and conditions set forth in version 1.0 of the Open Publication License. Please refer to Appendix D for the license text. This book was prepared from rev 028543f67bea, dated 2008-08-20 15:27 -0700, using rev a58a611c320f of Mercurial. Contents Contents i Preface 2 0.1 This book is a work in progress ...................................... 2 0.2 About the examples in this book ..................................... 2 0.3 Colophon—this book is Free ....................................... 2 1 Introduction 3 1.1 About revision control .......................................... 3 1.1.1 Why use revision control? .................................... 3 1.1.2 The many names of revision control ............................... 4 1.2 A short history of revision control .................................... 4 1.3 Trends in revision control ......................................... 5 1.4 A few of the advantages of distributed revision control ......................... 5 1.4.1 Advantages for open source projects ............................... 6 1.4.2 Advantages for commercial projects ............................... 6 1.5 Why choose Mercurial? .......................................... 7 1.6 Mercurial compared with other tools ................................... 7 1.6.1 Subversion ............................................ 7 1.6.2 Git ................................................ 8 1.6.3
    [Show full text]
  • Scaling Git with Bitbucket Data Center
    Scaling Git with Bitbucket Data Center Considerations for large teams switching to Git Contents What is Git, why do I want it, and why is it hard to scale? 01 Scaling Git with Bitbucket Data Center 05 What about compliance? 11 Why choose Bitbucket Data Center? 13 01 What is Git, why do I want it, and why is it hard to scale? So. Your software team is expanding and taking on more high-value projects. That’s great news! The bad news, however, is that your centralized version control system isn’t really cutting it anymore. For growing IT organizations, Some of the key benefits Codebase safety moving to a distributed version control system is now of adopting Git are: Git is designed with maintaining the integrity considered an inevitable shift. This paper outlines some of managed source code as a top priority, using secure algorithms to preserve your code, change of the benefits of Git as a distributed version control system history, and traceability against both accidental and how Bitbucket Data Center can help your company scale and malicious change. Distributed development its Git-powered operations smoothly. Community Distributed development gives each developer a working copy of the full repository history, Git has become the expected version control making development faster by speeding up systems in many circles, and is very popular As software development increases in complexity, and the commit process and reducing developers’ among open source projects. This means its easy development teams become more globalized, centralized interdependence, as well as their dependence to take advantage of third party libraries and on a network connection.
    [Show full text]
  • Branching Strategies with Distributed Version Control in Agile Projects
    Branching Strategies with Distributed Version Control in Agile Projects David Arve March 2, 2010 Abstract Branching strategies play an integral part in traditional software de- velopment. In Agile projects however branching is seen as the opposite to embracing change and therefor given little attention. This paper describes what branching strategies would support an agile workflow. It also describes how a distributed version control tool will fit better around these branching strategies then a centralized tool. This pa- per puts forth some original work on what branching strategies and team organization that fully takes advantage of a distributed version control tool. This paper aims to describe how a distributed version control can support agile teams with advanced branching strategies without slowing down or complicating the lightweight agile processes. 1 Introduction Software development is a process that produces a massive amount of highly complicated content. All of this content is produced by teams that range from just a few developers up to several thousands. It is obvious that this process needs to be highly coordinated. The coordination of this content is a part of Software configuration management (SCM). Traditionally this has been done by a centralized version control tool. [2] Branching strategies have not gained a lot of popularity in agile teams. [3] In recent years several new version control tools have emerged. These new tools break with the standard model of centralized version control (CVC) made popular by tools like CVS [9] and Subversion[6]. The new tools are based on a distributed model. Recent tools include Arch [5], Bazaar [8], BitKeeper [7] and Git [11].
    [Show full text]
  • An Introduction to Mercurial Version Control Software
    An Introduction to Mercurial Version Control Software CS595, IIT [Doc Updated by H. Zhang] Oct, 2010 Satish Balay [email protected] Outline ● Why use version control? ● Simple example of revisioning ● Mercurial introduction - Local usage - Remote usage - Normal user workflow - Organizing repositories [clones] ● Further Information ● [Demo] What do we use Version Control for? ● Keep track of changes to files ● Enable multiple users editing files simultaneously ● Go back and check old changes: * what was the change * when was the change made * who made the change * why was the change made ● Manage branches [release versions vs development] Simple Example of Revisioning main.c File Changes File Version 0 1 2 3 Delta Simple Example Cont. main.c 0 1 2 3 makefilemain.c 0 1 Repository -1 0 1 2 3 Version Changeset Concurrent Changes to a File by Multiple Users & Subsequent Merge of Changes Line1 Line1 Line1 Line1 Line2 UserA Line2 UserA Line3 Line2 Line3 Line2 Line4 Line3 UserB Line3 Line4 Line4 UserB Line4 Initial file UserA edit UserB edit Merge edits by both users Merge tools: r-2 ● kdiff3 Branch Merge ● meld r-4 Merge types: ● 2-way r-1 ● 3-way Revision Graph r-3 Some Definitions ● Delta: a single change [to a file] ● Changeset: a collection of deltas [perhaps to multiple files] that are collectively tracked. This captures a snapshot of the current state of the files [as a revision] ● Branch: Concurrent development paths for the same sources ● Merge: Joining changes done in multiple branches into a single path. ● Repository: collection of files we intend to keep track of.
    [Show full text]
  • A Quick (And Maybe Practical) Guide to Git and Version Control by Jay Johnson Necessary Shout Outs and Reference Links
    A quick (and maybe practical) guide to Git and version control By Jay Johnson Necessary shout outs and reference links • from slides from CSE 380 with Dr. Chris Simmons (UT-Austin) and • notes from Prof. Jean-Luc Thiffeault (UW-Madison) • https://betterexplained.com/articles/a-visual-guide-to-version-control/ • http://www.math.wisc.edu/~jeanluc/gitlab_instructions.php • https://betterexplained.com/articles/a-visual-guide-to-version-control/ • http://rogerdudler.github.io/git-guide/ • https://git-scm.com/book/en/v2/Getting-Started-Git-Basics • https://docs.gitlab.com/ce/gitlab-basics/start-using-git.html What is version control? • It tracks your files over time! • Makes life easier. You probably have already done this… • Have you ever done something like?... • Resume-may2015.docx • Resume-june2017.docx • Or this… • Seminar_20171116_Spratt_Draft1.tex • Seminar_20171116_Spratt_Draft2.tex • We want a new version without destroying the old ones! • We may even use a shared folder so you don’t have to email things back and forth, and hopefully everyone relabels them when they change things. This works for small projects but large ones? A whole dissertation? Not really… What does version control do? • Backup and Restore. Files are saved as they are edited, and you can jump to any moment in time. Need that file as it was on Feb 23, 2007? No problem. • Synchronization. Lets people share files and stay up-to-date with the latest version. • Short-term undo. Monkeying with a file and messed it up? (That’s just like you, isn’t it?). Throw away your changes and go back to the “last known good” version in the database.
    [Show full text]
  • Version Control) Installation and Configuration Guide Version 8.0 and Higher
    Source Management (Version Control) Installation and Configuration Guide Version 8.0 and Higher July 05, 2018 Active Technologies, EDA, EDA/SQL, FIDEL, FOCUS, Information Builders, the Information Builders logo, iWay, iWay Software, Parlay, PC/FOCUS, RStat, Table Talk, Web390, WebFOCUS, WebFOCUS Active Technologies, and WebFOCUS Magnify are registered trademarks, and DataMigrator and Hyperstage are trademarks of Information Builders, Inc. Adobe, the Adobe logo, Acrobat, Adobe Reader, Flash, Adobe Flash Builder, Flex, and PostScript are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries. Due to the nature of this material, this document refers to numerous hardware and software products by their trademarks. In most, if not all cases, these designations are claimed as trademarks or registered trademarks by their respective companies. It is not this publisher's intent to use any of these names generically. The reader is therefore cautioned to investigate all claimed trademark rights before using any of these names other than to refer to the product described. Copyright © 2018, by Information Builders, Inc. and iWay Software. All rights reserved. Patent Pending. This manual, or parts thereof, may not be reproduced in any form without the written permission of Information Builders, Inc. Contents Preface ......................................................................... 5 Documentation Conventions ............................................................5 Related Publications
    [Show full text]
  • Version Control with Git
    Version control with Git Kees den Heijer Data2day January 29, 2020 DOI 10.5281/zenodo.3629176 Kees den Heijer (Data2day) Version control with Git January 29, 2020 1 / 22 Introduction Outline 1 Introduction Reproducibility Why version control Version control systems Git 2 Hands-on exercises Carpentries material Collaboration Branching Continuous Integration Kees den Heijer (Data2day) Version control with Git January 29, 2020 2 / 22 Introduction About the speaker Educated in Coastal Engineering Experienced in data and information matter Data Steward @ TU Delft Owner / consultant @ Data2day MSc (2005) PhD (2013) Kees den Heijer (Data2day) Version control with Git January 29, 2020 3 / 22 Introduction Why version control Version control Recognize this?? source: Piled Higher and Deeper by Jorge Cham www.phdcomics.com Kees den Heijer (Data2day) Version control with Git January 29, 2020 4 / 22 Introduction Why version control Traceability by design is common practice in food industry Peanut butter Egg code Kees den Heijer (Data2day) Version control with Git January 29, 2020 5 / 22 Introduction Why version control Why version control? We need Reproducibility by design Scientists we are... Key advantages of version control professional easily trace back all steps taken human have your work reproducible proud always have a back-up aiming at quality Kees den Heijer (Data2day) Version control with Git January 29, 2020 6 / 22 Introduction Version control systems Flavours of version control Distributed Centralized Local source http://git-scm.com/book Kees den Heijer (Data2day) Version control with Git January 29, 2020 7 / 22 Introduction Version control systems Doesn't cloud storage also keep track of versions? Yes, but this has..
    [Show full text]
  • Pragmatic Version Control Using Git.Pdf
    Prepared exclusively for Trieu Nguyen Download at Boykma.Com What readers are saying about Pragmatic Version Control Using Git Pragmatic Version Control Using Git is an excellent guide to getting you started with Git. It will teach you not only how to get yourself started but also how to cooperate with others and how to keep your history clean. Pieter de Bie Author, GitX If you are thinking of using Git, I highly recommend this book. If you are not using a version control system (and code or create content on a computer), put the book down, slap yourself, pick the book back up, and buy it. Jacob Taylor Entrepreneur and Cofounder, SugarCRM Inc. Not only has this book convinced me that Git has something to offer over CVS and Subversion, but it has also showed me how I can benefit from using it myself even if I’m using it alone in a CVS/Subversion environment. I expect to be a full-time Git user soon after reading this, which is hard to believe considering this is the first distributed version control system I’ve ever looked at. Chuck Burgess 2008 PEAR Group Member Travis has done an excellent job taking a tricky subject and making it accessible, useful, and relevant. You’ll find distributed version control and Git much less mysterious after reading this book. Mike Mason Author, Pragmatic Version Control Using Subversion Prepared exclusively for Trieu Nguyen Download at Boykma.Com Pragmatic Version Control Using Git Travis Swicegood The Pragmatic Bookshelf Raleigh, North Carolina Dallas, Texas Prepared exclusively for Trieu Nguyen Download at Boykma.Com Many of the designations used by manufacturers and sellers to distinguish their prod- ucts are claimed as trademarks.
    [Show full text]