Vss2git - Project Hosting on Google Code. What is it? The Vss2Git project contains several components: Vss2Git is a Windows GUI application that exports all or parts of an existing Microsoft Visual SourceSafe 6.0 (VSS) (Wikipedia) repository to a new Git repository. It attempts to construct meaningful changesets (i.e. Git commits) based on chronologically grouping individual project/file revisions. VssDump is a console-based diagnostic tool that prints a plain-text dump of the contents of a VSS repository. All components are written in C# using the Microsoft .NET Framework 3.5. How is it licensed? Vss2Git is open-source software, licensed under the Apache License, Version 2.0. What are its goals?
Several key features not found in other VSS migration tools inspired this project: Preserving as much history as possible from the VSS database, including deleted and renamed files. Admittedly, some potentially interesting features are currently outside the scope of the project, such as: Incremental migration. How well tested is it? Resources. Home - git-vss - GitHub. Using git submodules to share a backend library between two local repositories. Acknowledgements The following knowledge about git submodule usage has been achieved from on-site training with Adam Dymitruk. (Also, be sure to check out Adam's article in Code Magazine: Git from a Developer's Perspective.) What scenario is this blog entry meant to address? This blog entry addresses the common scenario where multiple web, Windows, Silverlight, console, or other clients all reference a common set of backend libaries.
The backend libraries would contain the domain model, repository layer, utils, external gateway references, and so on. Why git submodules? Git submodules present a distinct advantage over other methods for referencing backend libraries. Approaches for referencing backend libraries from multiple clients Let's have a more detailed look at each approach: Referencing compiled DLLs In this case, you treat the backend libraries as a somewhat fixed SDK, much as you might treat a 3rd party library. Which brings us to the 4th approach: Do the following: Nada Inusual… todos los dias son iguales aunque parezcan distintos.
C# Howto. Tutoriales. Opensource. Codigo. Nabaztag. Tests. Linux. Ruby.