CVS, Sub. Version and Visual Fox. Pro. CVS, Sub. Version and Visual Fox.
Proby Christof Wollenhaupt, Foxpert. Overview. What's wrong with Visual Source.
Visual Studio does not support any programming language, solution or tool intrinsically; instead, it allows the plugging of functionality coded as a VSPackage. When installed, the functionality is available as a. Using Beyond Compare with Version Control Systems. For Mac OS X, see this article. Beyond Compare can be configured as the external difference utility in many popular VCS applications. The following are configuration. How to extend the web publish process without modifying project contents. When automating web publishing for Visual Studio projects in many cases your first step will be to create a publish profile for the project in VS.
Safe? For many years version control in Visual. Fox. Pro and Visual Source. Safe were synonyms. Sessions and articles covering team. Visual Source. Safe. Most commercial. alternatives were designed to be used in a bigger team, not in the small teams.
Visual Fox. Pro. Moreover, Visual Source. Safe is a. Microsoft product.
I've started a C++ column in Visual Studio Magazine. I'm sure you've read plenty of C++ columns in your time - I sure have! I wanted this one to be a little different. So, here's what I've decided to do. This article discusses how to customize assignment of version numbers to.NET assemblies to match specific requirements of the development team. It suggests use of UpdateVersion utility to handle various version. CVS, SubVersion and Visual FoxPro. Overview What's wrong with Visual SourceSafe? For many years version control in Visual FoxPro and Visual SourceSafe were synonyms. Sessions and articles.
As it is part of Visual Studio and because Microsoft made. Visual Source. Safe in some way. But does that mean that Visual Source.
Safe. is the best choice? There's no doubt that using any version. Version control systems allow multiple. They allow for documenting every change. Later you can retrieve files by label enabling you to restore. This feature is priceless if a. Nonetheless, Visual Source.
Safe has got a. number of disadvantages, too. Visual Source. Safe is not a client/server. Because the Source. Safe client directly accesses the VSS database. While this is only a.
VSS. database even across a DSL line. In addition you are deeply dependent on the. A single machine with a defective network. Microsoft released version 6.
Visual. Source. Safe in 1. VFP 6. 0. For the following almost eight years.
Microsoft released three more Versions of Visual Fox. Pro, many new operating. NET even a complete new development.
However, for Visual Source. Safe they only released minor patches. It does have a few new features for Visual Fox.
Pro Users. With Visual Studio 2. Team System. Microsoft made it pretty clear what the future path for team development and. Since VS. NET is the main development tool at Microsoft. VSS for developers.
Indeed, VSS 2. 00. The VS 2. 00. 3 developer and mostly Office developers. Visual Studio. Once that happens, Visual. Fox. Pro remains the only product that would benefit from Visual Source. Safe. To access a VSS database via a VPN or any. The most popular one is Source.
Off. Site. Even though this is. For one, the. increase in licensing costs is substantial. Source. Gear, the maker of Source. Off. Site. also offers their own version control system named Source. Vault. This inevitably.
Microsoft is reducing its support for Source. Safe. Finally, security becomes an increasing.
Even though you can grant permissions to users in VSS, this is all. As a file server based system, a user needs write access to. VSS database folder in order to check in any file. Hence, instead of. CVS and Sub. Version are open source.
Visual Source. Safe. Installing CVSCVS consists of two components: a server. Like in many open source projects there are several different. These tools share some parts, but. This document only covers the Windows version.
You can. download the most recent version from the following web sites: CVSNTCVSNT is an implementation of CVS for. Windows that was so successful that it has been ported over to UNIX. CVSNT is the. server component. As the name indicates, you need a server machine to install. CVSNT. The operating system doesn't have to be Windows Server, Windows XP works. When choosing the computer you should consider the following.
The operating system should be Windows. NT, Windows 2. 00. Windows XP Professional or Windows 2. Server. If you have more than one user, the file. NTFS. This is actually independent from CVSNT, because. FAT3. 2 file system is a serious security risk. Easily to forget: The computer must be.
TCP/IP for all developers. When accessing the server from.
TCP. port 2. 40. 1 to the CVS server. As you expect from any Windows application. Launch cvsnt- 2. 0.
If you install CVSNT on your desktop machine, you are most. Therefore right click the application. On Windows 2. 00. Shift. key while you click the right mouse button. On Windows NT you have to log on as. Administrator. Accept the license agreement and use the default settings in. CVSNT installs itself as a Windows service.
For configuring the service, you. CVSNT in the Control Panel. On a desktop machine, hold down. Shift key while right- clicking the icon in order to execute the. Administrator. CVSNT actually consists of two. Normally, the default configuration is.
To complete the installation you only have to create a repository. A repository corresponds to a Visual. Source. Safe database. The repository contains all files and projects that the. CVS server manages. Normally you have a single repository for each server to.
You only need multiple repositories, if you not. Another. reason to maintain multiple repositories is when you need to hand over the.
You create a new repository on the. Repositories page in the CVSNT configuration dialog.
You are. prompted to pick a directory that is used to store the repository files: Please write down the value of. You will need it every time you access the repository. Create. a new directory on your computer and pick it. After clicking on OK, CVS asks. Choose Yes. After that the repository is ready to use.
With. the default settings CVSNT uses the Windows user management to validate access. By granting or denying users access to the newly created.
CVSNT server. To simplify your. CVS. Then assign the. If you are logged on as a regular user on. CVS, you have to grant yourself write access to the repository. Aside from the repository, the CVS server. TEMP directory. By default, this is. C: \program Files\CVSNT\Temp.
Regular users do not have write access to this. You either have to grant users in general, or the CVS. Win. CVSCVSNT installs CVS. EXE. This is a command.
CVS server. If that's sufficiently comfortable for. However, most Windows and DOS developers don't feel. Norton. Commander or PC Tools made clear. For those developers Win. CVS is an excellent. You install CVSNT only on the server.
Win. CVS. on the other hand, must be installed on every machine from which you want to. Launch the setup program as Administrator, accept the. When Win. CVS completed its own setup, the. CVSNT setup. Even if you installed CVSNT on this machine. Win. CVS uses CVSNT to install the.
CVS Server. You can ignore. CVSNT. The first time you. Win. CVS you must do so as an administrator.
Win. CVS wants to create some. Otherwise Win. CVS will crash when you. Subsequently, you can run Win. CVS with your regular user account. Working with CVSIntroduction.
Launch Win. CVS using the Start > Programs. Win. CVS < Win. CVS menu item. You should see the main window: Developers that are used to Visual.
Source. Safe often find CVS a bit strange. Win. CVS looks a lot like the VSS. Explorer, but it works quite differently.
This starts with accessing the. VSS is an integrated system. The Explorer contains all the code. Win. CVS, however, sits on top of CVS. EXE. Every. action in Win. CVS results in a call to the external EXE. All parameters are.
Win. CVS shows all output of CVS. EXE in the. lower pane.
The second difference is the so called. CVSROOT. This environment variable defines on which server you access which. This setting isn't stored globally, but.
More precisely, it's stored separately for every folder. You. need to know this when you change the server name. Adding a project to CVSJust like with Visual Source. Safe, in CVS. developers don't work in a common directory. Every developer has his own local. CVS is called a sandbox.
The. developers loads those modules into the sandbox on which he's currently. This process is called a check out, but doesn't have to do.
VSS. Before you can check out a module from the. This. process is called an import. In the following sections I'll use the.
Tastrade project. When you import into a repository, CVS adds. During the process you. Therefore it's. recommended not to import directly from your development directory. Instead. copy the project into a new directory and delete all files that you don't want. These are, for example, all data tables, FXP files.
A further difference is the handling of binary. Contrary to VSS, CVS doesn't support exclusive check outs. In fact. everybody can edit every file anytime. Upon checking in (in CVS called a commit). CVS analyses the differences and merges your changes into the master copy.
This. isn't a problem with text files, but it's impossible to do with binary files. VCX class libraries or SCX forms.
This alone wouldn't be impossible to solve. The. real problem is Visual Fox. Pro, though. A VCX library doesn't only contain. The compiled code changes every time a. If you are building the EXE, CVS considers all. VCXes to be changed.
Therefore you can't simply get the current version from. Instead you would have to reject the changes (get the clean. CVS). Before you do this you definitely need to know.
I wrote a tool named Two. Fox, because in. practice it's impossible to deal with binary VCXes.
Two. Fox consists of two. Gen. XML and Gen. Code. Gen. XML takes a VFP project and produces XML. Gen. Code reverts these XML files into code files. In this directory create a.
Tools. Copy Gen. Code. APP and Gen. XML. APP into that directory. Launch VFP and switch to the project directory. Gen. XML. then creates XML files for every binary file.
Because Gen. XML basically uses the. Visual Fox. Pro, the conversion doesn't take very long. Close VFP and open the project directory in Windows. Explorer. Delete all files that you don't want to place under version control. In case of Tastrade. Data directory. Help\Tastrade.
These files are only. CVS. Menu\*. mpr. The project manager. The Notes directory. Tastrade doesn't use. Tastrade. app. You can build this file.
Tastrade. ini. This file is user specific. If you have INI files that must contain.
Tastrade. ini. txt, that contains all mandatory entries. By using Gen. XML you can also delete any. Gen. XML created an XML file. These are the class libraries, forms. Before you import a module, you have to log.
CVS server. From the menu choose Admin > Login. You'll get the. login dialog. Upon the first time, the CVSROOT field is empty. This dialog looks like this: In the Protocol combobox select.
As Repository path enter the name of the repository. This doesn't. have to be the physical directory name.
In the CVSNT configuration dialog this.
Beyond Compare Technical Support For Mac OS X, see this article. Beyond Compare can be configured as the external difference utility in many popular VCS applications.
BC version 2. For BC2, only change the xcompare line of the map file. BC version 3 or 4.
Navigate to the Dimensions / PVCS install folder and find the file pvcsmerge. BC version 3 or 4 with extended functionality. Download PVCSmerge.
PVCSmerge. txt instructions included in the zip file. Word documents) and archives (Zip). BC version 2. Follow the instructions above, but instead of using BComp.
PVCS 6. 8, 8. 0, and Merant Dimensions 8, or in pvcsmerge. PVCS 7. 5. Choose Properties in the Project Manager's Options menu. BC version 4. Diff. At a Windows command prompt enter the commands.
To launch a diff using Beyond Compare, use the command . To launch a 3- way merge using Beyond Compare, use the command . BC version 3. Diff. At a Windows command prompt enter the commands. BC version 4. Diff.
Open the file . Add the following lines: /usr/bin/bcompare . Add the following line: /usr/bin/bcompare .