OpenMake Meister leverages the Microsoft ALM process for multi-lingual and multi-solution environments making it simpler for all developers, regardless of language or application complexity, to take advantage of TFS and TeamBuild.  OpenMake Meister preserves the integrity of the Microsoft ALM process for diverse development environments from Java to C-Unix.    We can help you when you are facing the challenges of building complex applications using:

• Complex Multi-Solution .NET Builds.
• Complex cross compiler environments were multiple versions of the .Net compiler are used.
• The acceleration of large .NET compiles.
• Multi-lingual development requiring the need for building applications using .Net and/or Java.

Complex Multi-Solution .NET Builds

Many Microsoft developers have created large and complex applications that use multiple Solution files with cross dependencies. This means that one Solution exports functions to another Solution.  These Solutions need to be compiled as a single Solution in order to resolve the dependency relationships.  OpenMake Meister resolves this challenge by compiling multiple Solution files as a single Solution, resolving all dependencies in a single build pass.  There is no need to define the order in which the Solutions should be compiled.  Meister performs this build decision making automatically and accurately.

Complex Multi Version .NET Builds

Many Microsoft developers have been using the Visual Studio suite to build applications for several years. This means that multiple versions of the Microsoft VS IDE (VS 6.0, VS 2003, 2005, 2008, 2010) may be used.  In most cases, these applications have shared objects where, for example, a VS 2008 application may use a shared object written in VS 2003.  OpenMake Meister supports the building of applications that use more than one version of the .NET compiler in a single build pass.  With Meister, you can easily assign which version of the compiler needs to be used to build any single binary.

Accelerated Parallelized builds with Build Avoidance

Building faster is critical for large projects.  Meister accelerates builds by managing the compiler calls, sorting out dependencies and leveraging the power of multi-core processing machines to build the objects in parallel.  This is by far the most efficient method of speeding your builds. In addition, Meister uses Build Avoidance for supporting accurate incremental build processing.  Build avoidance simply means that your builds will be done incrementally, re-compiling only the objects that are out of date. With MSBuild you can define "Transform" relationships between objects and MSBuild will check the time and date of the relationships to determine if on object is out of date.  To do this, you must code the "Transform" statements manually in the MSBuild script to define how you want to handle the date/time checking process. OpenMake Meister uses machine intelligence to automatically track these dependencies and perform the date/time checking for you without the manual coding of "transform" statements.

Multi-lingual and Mutli-Platform Development Environments

Meister extends the use of TFS and Team Build to support multi-lingual and multi-platform builds.  With Meister, developers can check-in Java source into TFS, and use Meister and TeamBuild to compile the Java objects.  Meister extends the .NET development environment to the following languages and platforms:

C#, J#, VB.NET, C.NET, ASPX, C - VS 6, C++ - VS 6, VB - VS 6, MSI Installers, Other .NET project file formats, Biztalk 2005, Java, COBOL

Meister Leverages MSBuild and TeamBuild

OpenMake Meister leverages team build to support complex Microsoft development environments.   This allows an application written in multiple versions of the VS IDE or uses multiple solution files to be compiled as a single application.  Meister performs all of the build decision making, using source dependency management, that allows the Microsoft ALM process to stay in place.  Meister preserves the well thought out Microsoft ALM process even when the application goes beyond what the .NET IDE intended.