InfoQ Homepage migration Content on InfoQ
-
Rails Style Database Migrations in .NET
Versioning database schema along with your .NET code is essential for managing volatile codebases especially when employing continuous integration. Ruby on Rails accomplishes this with a popular solution of abstracting DDL SQL into Ruby commands. Similar solutions are available in .NET with third party libraries.
-
-
Mainsoft: Running .NET on the JVM While Maintaining Performance
Mainsoft recently released version 2.0 of Mainsoft for Java EE (formerly known as Visual Mainwin), and also released a whitepaper which showed that a .Net-based application which was cross-compiled to run on Java EE using Mainsoft for Java EE performed as well as or better than the original .NET-based application did in several areas. InfoQ spoke with Mainsoft CEO Yaacov Cohen to learn more.
-
Migrating Applications to Struts2
Struts was first released in June of 2001 and has become the de-facto standard for web application development. In December 2002 it was announced that WebWork and Struts Ti would join forces to become Struts Action Framework 2.0 and the official successor to Struts. In a new InfoQ article series, Ian Roughley looks at the task of moving applications from Struts to Struts2.
-
Opinion: Every Project should have an Upgrade Framework
HostedQA, JIRA, Confluence, and Jive Forums all have implemented frameworks to manage changes to db schema's and data migrations between subsequent versions of their products. Pat Lightbody proposes that all enterprise apps should include an upgrade framework and provides some best practices.