FeResPost is a library that allows the rapid development of small programs for the post-processing of Nastran or Samcef finite element results. The library allows easy manipulation of finite element models, groups, and results. Efficient post-processing is possible because the time-consuming operations are written in C/C++. The library is distributed as a COM component, a .NET assembly, as well as a Ruby compiled extension.
i-net Clear Reports (formerly i-net Crystal-Clear) is a very powerful reporting solution. It can accommodate a broad range of reporting needs, from a simple standalone application to a really big enterprise Web solution. It can produce many different output formats like Java Viewer, PDF, HTML, PS, RTF, XLS, TXT, CSV, SVG, and XML. It can generate reports from many different data sources like JDBC, ODBC, Java API, JNDI Data Source, and without data.
EC2 Mobile manages Amazon AWS EC2 instances from a Windows Mobile device. It allows you to start, stop, and manage running EC2 instances. If you have multiple clients who run their services on EC2, you can also store multiple profiles so that you can see all of the instances running across all clients. Similarly, you can see each profile's AMI images.
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").
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.