In software development version control is often associated with tool supported team work in projects. In these cases it supports the central storing of versions of files in a repository. Filing, change logging and providing the versions are the most common scenarios. Subversion (SVN) is a widely used, and license -free version control software. SVN and several free APIs facilitate the use of the version control via the application. But there is also an enormous benefit from the combined usage of version control software and web applications like DotNetNuke. Apart from the actual development of software the need for version control increases in several other areas. Examples are functional specification documents, manuals, as well as design plans from the marketing department or reports from the controlling department. Products like SVN cover the requirements completely.
The DNN module “svnModule” form one of my colleagues at ITM
, Simon Meraner, integrates SVN into a DNN-based web application. Files can be updated from and committed to the repository via browser. The local directory for the exchange can be selected via the module. The files can then be checked out from the repository into the local directory on the webserver. The first check out establishes the connection between the local directory and the SVN repository. The svnModule uses this connection to identify changed files and log changes, to commit files to the repository, and to update or revert files in the local directory.
Furthermore, the project contains a WCF component, which is integrated into the DNN module IWebCF, and a demo client. The WCF clients can start remote updates on the server.
Another supported scenario is the "content flow". Files and folders can be committed to the DNN file system directly by the user via i.e. Tortoise (Explorer Integration). And the commit process uses the http protocol. This offers plenty of benefit. Think about the possibilities.
The module and its source code can be downloaded at http://svnmodule.codeplex.com