blob: b37d224565a9a6d8863edfd95636bc6f7573bbb8 [file] [log] [blame]
<div class="wiki-content maincontent"><h1 id="AMQPBuildNotes-Defaultbuild">Default build</h1><p>Executing <strong>nant</strong> in the project home directory will produce two builds:</p><ul><li>Debug/Release .NET 2.0 x86 in the \net-2.0 folder built with Visual Studio 2008</li><li>Debug/Release .NET 4.0 x86 in the \net-4.0 folder built with Visual Studio 2010</li></ul><p>Your build system must have Visual Studio 2008, Visual Studio 2010, or both to produce the desired build.</p><h1 id="AMQPBuildNotes-Dependenciesandrestrictions">Dependencies and restrictions</h1><p>The version dependencies on Visual Studio and the x86-only restrictions are artefacts of the delivery mechanism for the vendor\QPid\Apache.QPID support libraries. These restrictions are important to understand for using this provider and for packaging this provider for your application.</p><h2 id="AMQPBuildNotes-Supportlibrarycomponents(x86only)">Support library components (x86 only)</h2><p>The support libraries consist of two parts:</p><ul><li>Native C++ Qpid Messaging (qpid*.dll, boost*.dll)</li><li>.NET interop binding between .NET and the native C++ code (org.apache.qpid.messaging.dll)</li></ul><p>The C++ support libraries are compiled with specific versions of Visual Studio and linked to the corresponding MSVC runtime libraries. In this release of Apache.NMS.AMQP only the x86 versions of Apache.QPID are provided.</p><p>Running the Apache.NMS.AMQP provider in an x64 environment or in a .NET application choosing AnyCPU will not work correctly. Please choose <strong>x86</strong> for your application <em>Platform target</em>.</p><h2 id="AMQPBuildNotes-Runtimelibrarystaging">Run time library staging</h2><p>When your application runs make sure that all of the Apache.QPID support library dll files are copied to the final execution directory. When the support library files are not in same folder as <em>org.apache.qpid.messaging.dll</em> then the Apache.NMS.AMQP provider may not load correctly. Having the support files on your application's PATH is not sufficient for successful loading.</p><p>&#160;</p></div>