Itzam/Sharp is a C# class library for creating and manipulating keyed-access database files containing variable-length, random access records. Information is referenced by a user-defined key value; indexes may be combined with or separate from data. Itzam/Sharp implements the Itzam engine (see Itzam/Core and Itzam/Java) in 100% managed C#. At 32K, the Itzam/Sharp engine is both small and powerful, and it works with any .NET language, including F# and Visual Basic.
Vici MVC is a MVC Web application framework for .NET 2.0 or higher. It runs on the low-level ASP.NET layer provided by the .NET framework, but does not use ASP.NET WebForms and Controls. The framework is controller-centric as opposed to the view-centric architecture of ASP.NET WebForms. This allows Web applications to be built according to the MVC pattern with minimal effort. Vici MVC emphasises complete separation of concerns, ease of use, minimal configuration requirements, integration with any data access technology, performance, and easy deployment ("XCOPY deployment").
Duplicati is a backup system and an implementation of Duplicity. Duplicati enables you to set up and monitor backups on Windows or Linux. Duplicati is based on the Linux-only Duplicity backup system. Duplicati has a very user friendly interface that allows you to configure and monitor your backups. It supports backing up to a variety of destinations, such as a network folder, a USB disk, a remote FTP server, a remote SSH server, Amazon S3 storage, or a WebDAV enabled server. All backups can be encrypted and are digtally signed, so that no other person can read or tamper with the backed up data.
Git# is a C# implementation of the Git version control system for the .NET platform. It is meant to be fully compatible to the original Git implementation in C for Linux. It can be used as a stand-alone command line application (potentially replacing msysGit on Windows) or as a library for applications such as GUI frontends or plugins for IDEs.
CVS, GIT, and Mercurial as well as other well-known version control systems cannot version directories. In other words, you cannot add empty directories. A "workaround" for this issue is to use placeholder files that are placed into empty directories. These placeholder files can then be committed into the repository and will make sure that, upon checkout, the directory tree is entirely reconstructed. The problem with using placeholder files is that you need to create them, and need to delete them if they are not necessary anymore (because sub-directories or real files were added). With big source trees, managing these placeholder files can be cumbersome and error prone. MarkEmptyDirs can manage the creation/deletion of such placeholder files automatically. It creates placeholder files in all empty "leaf" directories. If later on new files or directories are put into such directories, the placeholder files are not necessary anymore, and are removed automatically.