An Overview of Win Cvs and Its Usage In Software Companies

The concept of windows is introduced with windows class viewer. Whenever we open a browser a single window is opened. The window contains the document which one is currently viewing. It is possible as it depends to a great extent on the browser as well as the operating system used to have multiple browser windows open simultaneously with either the same or different amount of documents displayed within them. Windows and view windows are the bare classes for creating any type of user interface. A window represents a geometric space on a screen, while the view acts as a container for the other objects. Small user interface components, such as navigation bars, text boxes and buttons are attached to the view and the view is anchored to the button. One can think of the windows as the frame of the painting and the view as the actual canvas. In fact windows can only frame up one view, but views can contain smaller sub views including the other views which may arise at any point (Zdziarski, 2008). Students need help in setting up reposterios since this is something which they cannot do it from their unprivileged accounts. The subsequent uses of the courses can make use of their skills also. In fact the introduction of XP can also affect the courses at the introductory level. In a way the practice of test first and pair programming can also be pushed down to this level. There are several reports from trying out XP or parts of XP programmes. From the experience point of view, most of them are very positive about the outcome of XP in the domain of education.

Available online at www.ignited.in Page 2

The document describes the day to day usage of the win CVS. It replicates a classical situation of you wanting to do something and not being aware of how to do it. Win Cvs differs from virtual source safe (VSS) in a variety of ways. It does not require the users to lock the files which they are working on and does not encourage locking. In a rare occasion where several people have changed the file at the same time a merge is possible to some extent. If two or more developers have changed the file, then is rest assured of the fact that a conflict will be reported for sure. Win Cvs provides a client view and will not provide you with the information of changes unless you tend to update it as well as query the status of the current files. In fact the changes which are reported in the file view of CVS are the ones which are done after the modifications occurred after the last view. On the other side of the coin a simplistic view of win CVS is preferred as it may give a feeling of control to the experienced users.

If one has a background in programming with net 1.1 then on all counts they might be familiar with the windows forms class viewer utility. This tool allows you to type in the name of a .net file and view its C definition (Troelsen, 2007). Among the long term developers Concurrent versions system (CVS) is a reliable as well as an old warehouse. On windows the most commonly used implementation system is Win Cvs. In the domain of Mac one can get a CVS implementation known as Maccvs. Wincvs has proven exasperating for most of the developers of Dreamweaver in environments related to production. but they are a couple of options for making it viable for versioning (White, 2004). Win Cvs is a class viewer analogous to the visual studio object viewer for those not using the visual studio. It is located in the programme files/Microsoft.net/sdk/v1directory and can be run from the command prompt. When the window appears, type the name of the class you want to view into the searching for box. It provides a wealth of information about any type in the base class libraries. The four highlighted areas provide a sampling of what is available which are

• System- Array is the class that is being explored

• This class is located in the mscorlib.dll assembly. As already mentioned this assembly contains the .net types

• This list consists of class, objects as well as interfaces that the array class inherits them from

• The definition of each method in the class is included. This definition which includes the accessibility, type and methods is called the method’s signature (Perry, 2009).

WinCvs could be referred to as the open source engineering platforms. It is one of the free clients that give the users a choice of platform. Adoption of CVS among open source projects is near vital and the concepts embedded in CVS have clearly influenced the open source methodology. It can provide universal access to users of many platforms and many native languages at locations all over the globe. In fact the command line syntax of CVS follows conventions established by the earlier RCS system. Peer review is enabled by easy access to the repository, and is encouraged by small notifications of changes (Feller, 2005). CVS is a revised control system. It can track the changes in your project files and can inform of the conflicts when two developers make changes to the same file. On the other side Win CVS is a graphical interface which makes the CVS client easier to use. If you have made changes that causes a conflict the update command will tell you. In WinCvs file window, the file affected will have a status of conflict. Editing your file will show where your changes conflict with others. Using the query/log command you can find out who made the change and editing the file will help one to resolve the conflict (Norvell, 2002).

Cvs is pretty easy to set up as well as install. In fact the biggest strength of wincvs is that many developers are already familiar with it in the first place. It bonds with large scale projects (involving hundreds of users) as well as large files which might be billions of megabytes in size as well. It must be mentioned that the time span increases to

Available online at www.ignited.in Page 3

tag the files with the number of files as well as their sizes increasing as well. Most Cvs servers have the longest uptime in any company. Though it has been cracked in the past but to a large extent it is secured of sorts. Since it happens to be an open source as well as mature domain a host of tools are also related to its which are

• ACL- this is the basic the control operation which helps one to control files. It identifies who can commit the files according to the user, the directory along with the directory name (Doar, 2005).

In fact one can take a clue from the software giant Microsoft. They incorporate a shrink module which is built upon the daily smoke as well as the build test. WinCvs is similar to virtual source in a lot of ways. It has been observed that CVs does not have a good support system for restructuring a project and it is suggested that you undergo a process of planning before you install it. The cornerstone for such a situation to arise is a clean directory structure which does not mean that one will get rid of a backup plan as well. This is all the more important if your project has been running for a considerable amount of time in the first place and you do not want to place all the modules under version control. But the fact of the matter is that you anyway want to keep them also, so it is suggested that you move them out before importing and again bring them again also. In the midst of all this one needs to be aware of the fact that CVS directories are empty and one needs to create a dummy file inside it also. In this regard it is suggested that you create a file with a short description of what is the ultimate objective of the file as well. Once in a while during the working of CVs conflicts are bound to rise. This happens when two developers have changed the same lines of the project. The fact of the matter is that CVS is not aware of any details of the project and chooses to stay from it. The developers settle the conflicts among themselves. When a conflict arises one should open the line from where the command arises and this can be found from the question marks which arise. One must decide on how the code looks like, remove the mark up as well as make the necessary changes so that the software is in a perfect shape to run.

Windows class viewer comes with Net. It offers another view of every class. As CVS been around for a long time, there are clients for virtually every platform. If you have a Linux box, chances are there you already have CVS client and the server software installed. Windows and OS X have clients in abundance, both with official command line clients and with independent GUI clients. WinCvs for windows is fairly popular as well as easy to use. CVS has a couple of major web interfaces commonly referred to as viewCVS. It has a plugged system for executing random commands whenever someone logs in. In fact this pluggable system offering benefits which allowing such things as automated administration weakening test suites when new codes are formulated, popular database with comments and keeping modified copies in alignment with the supreme head. In addition to this the CVS supports the bonsai commit database through his pluggable triggers feature. Bonsai w===as created as a Mozilla project tool and written in Perl, using and storing its data in MySQL. It supports all the usual commit database features and it is fairly easy to set up as well as use also. It is easy to integrate the application using the stored data directly as well (Hendersen, 2006). There is an open source project underway to develop a replacement for CVS which is referred to as subversion. Preliminary reports are encouraging but it is not ready for prime time yet. In the meantime the focus has to be on CVS. Once the directory is set up its time to check the project into the repository. CVS will keep track of the information locally and it is necessary to do the checkout once we have imported the information in the first place. If one examines the hierarchy it will be observed that each directory contains a new CVS. One of the other major advantages is that it is quick and inexpensive for both the employer as well as the employee. The official release version is ancient, the CVS version which is some sort of a moving target supports many hardware platforms and has many more features than the old release. If one is using the windows it is suggested that they download as well as install the official eCos version and update it with the current version of CVS. By doing this all the default configuration information, registry values and so on can be initialized by the automated installer.

WinCvs is a well written graphical application that works well with CVS repositories ease and delicate way. It can be obtained at the official website of the company. Once it is installed you can configure it with the SQL repository in the following ways. Create a folder to check the source code in the first place

• On the left pane open win Cvs and navigate to the folder which you have created

 From the main menu select admin- login as well as select remote- checkout in the module name as well as the path of the server (Owens, 2006)

Available online at www.ignited.in Page 4

From the commercial point of view it has a host of advantages associated with it. In fact the most popular version control system is the concurrent version system or known as CVS which is an open source product used by millions of developers for both commercial as well open source products. It has been available for a long point of time and most of the platforms as well. The fact of the matter is that it is not all that powerful like some of the commercial products but it is more than sufficient for a lot of projects because of the simplicity as well as the low cost factor. Many a times one comes across such users of win Cvs who are hesitant to switch over to using their IDEs as a version control system. The question is why one bother should in the first place and the obvious answer to the question is the convenience factor. In this regard when one creates a file name or class the change is ready to commit into the respiratory. One can review the changes and commit the files within a few clicks and that too without leaving the IDE in any way. This definitely calls for a reason to investigate also (Fields and Saunders, 2006). The way one should look at CVs is a series of steps in a systematic way and considers the way on how one wants to make changes like

• Check out one of the files from the CVs repository

• Make the necessary changes to the file

• Execute the update command on the file

• Commit your changes back to the file

This is not all that a difficult proposition. One collects a file, makes the necessary changes to it and ascertains the fact whether there are any duplicate versions of it available on the web. It is a common scenario that while you were working on the file someone would submit one. In this regard it is suggested to merge the file and submit it again. In the world of today all things come at a price and so does the CVs server. It is quiet difficult to install a server and configure it but it has a steep learning curve attached to it also. We can consider ourselves lucky to a considerable extent as there is software which is available at each and every step for our guidance (Elst and Yard, 2006) Wincvs a windows based utility can be used to browse classes and one of the greatest advantages form a developer’s point of view is that one gets to use the .net class library. It has a massive collection of coded class libraries and can perform any sort of task that was previously performed by any windows platform. This in a way means that you can initiate of objects of whichever .net base or one could derive their own classes from them also. In fact one of the greatest focal points is that they are designed in a simple manner and pretty easy to use as well (Nagel et al, 2007). Such is the evolution that anyone who uses a computer for a project development system can benefit from version controls. The prime objective of version controls is to save time as well as money. It enables to ascertain whether all the development teams are on track and to see whether all the assets involved in the development of the application are protected also. Of all the assets the most important one is the source code but documentation, graphics and pretty much all things which are involved with the project are important (Gousset, 2007).

Both the WinCvs and the SSH protocol provide great enhancements to the CVS applications software. Win Cvs is a windows based programme that allows us to access a CVS repistory running on any UNIX server and this can be reached in any network. It needs to be kept in mind those two major applications. In the first place it requires the installation of the python programming language. Without Python windows Cvs will not run at all. The easiest way is to follow the instructions from the official website. In addition to this some of the features of Win Cvs are in built using the TCL version. To enable these versions active TCL or latest version of TCL should be installed. From the analysis the major fact which stems out is that Win Cvs happens to be the responsibility of the windows, otherwise several errors can stem up also. In fact it will be added value of the IDS. Clean fix could one of the effective solutions in this regard and this issue will support this decision to a considerable extent. The main problem for such a situation arising is the inability of the windows to understand the names of the files. From all counts Wincvs is an effective tool

1. Zdziarski, J. (2008). iPhone Open Application Development: Write Native Objective-C Applications. CA: O’Reilley 2. Bennedsen, J., Caspersen, M., and Kölling, M. (2008). Reflections on the Teaching of Programming: Methods and Implementations. Berlin: Springer. 3. Troelsen, A. (2007). Pro C# with .NET 3.0, Special Edition. NY: Springer.

Available online at www.ignited.in Page 5

4. White, C. (2004). Developing Killer Web Apps with Dreamweaver MX and C#. CA: SYBEX 5. Perry, S. (2008). Essentials Of .Net Related Technologies: With A Focus On C#, Xml, Asp.Net. New Delhi: Dorling Kindersley. 6. Feller, J. (2005). Perspectives On Free And Open Software. Massachusettes: MIT 7. Norvell, T. (2002). Quick intro to WinCVS. Engr 7893. Memorial Unversity of Newfoundland 8. Doar, M. (2005). Practical Development Environments. CA: O’Reilley 9. Henderson, C. (2006). Building Scalable Web Sites. MA: O’Reilley. 10. Owens, M. (2006). The Definitive Guide to SQLite. NY: Springer. 11. Fields, D., and Saunders, S. (2006). Intellij Idea In Action. New Delhi: Dreamtech 12. Elst, P., and Yard, T. (2006). Object-Oriented ActionScript For Flash 8. NY: Springer. 13. Nagel, C., Evjen, B., Glynn, J., Watson, K., and Skinne, M. (2007). Professional C# 2005 with .NET 3.0. NJ: Wiley. 14. Gousset, M. (2007). Professional Team Foundation Server. New Delhi: Wiley.