BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage migration Content on InfoQ

  • The Complete List of Migration Issues Upgrading to .NET 4.0

    Microsoft has published a complete list of issues migrating from .NET Framework 3.5 SP1 to .NET 4.0. The list contains changes in 6 domains: Core, ASP.NET, ADO.NET, WCF, WPF, and XML.

  • The End of an Era: Scala Community Arrives, Java Deprecated

    It was recently announced that InfoQ is creating a new Operations community. In addition to that, another major change which has been in the works for the last few months at InfoQ is the conversion of the Java community to the Scala community. InfoQ spoke with a prominent Scala expert and members of the former InfoQ Java editorial team to learn more about this change and why it was made.

  • Azure Drive Eases the Migration to Microsoft’s Cloud

    Initially announced as XDrive during PDC 2009, Microsoft has released the beta version of Windows Azure Drive, a storage access solution simplifying the migration of Windows applications to the cloud by creating an NTFS virtual drive on top of a storage blob.

  • Case Study: Migrating a VB6 Large Application to .NET

    An IT services provider company has migrated an ERP application totaling 950,000 lines of VB6 code to .NET in 9 months.

  • Simplify SQL Migration Scripts with SQrbL

    Managing SQL-based scripts can become a nightmare with time. Rails solved this with ActiveRecord Migration. Sam Livingston-Gray wrote a small standalone Ruby tool to generate hierarchical migration script. Based on the fact that SQL scripts can become very verbose and duplication-prone, Sam started SQrbL which is a mix of SQL and Ruby.

  • COBOL to Java Automatic Migration with GPL'ed Tools

    During the NACA project run by Publicitas Ltd., 4m lines of COBOL were automatically trans-coded (migrated) toward their Java equivalent. The company claims that the recurrent annual savings in cash-outs amount to a total of 3m euros and has released the tools from the NACA project under GPL.

  • 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.

  • Is COM a Dying Technology?

    Does COM still have a place or is it a dead end technology?

  • 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.

BT