Summary: Setting up Visual Studio project to use the space-based .NET API.
OverviewA few settings need to be configured before you start developing using the GigaSpaces API. These are described in the following sections. Managed ReferencesThe main assembly is GigaSpaces.Core.dll. This assembly provides the core space functionality (read, write, take, notify, etc.) for PONOs. It is strong-named, so you can use it in strong-named solutions, place it in the GAC (Global Assembly Cache), etc. It has two dependencies:
In most scenarios, all you need to reference is GigaSpaces.Core.dll – Visual Studio automatically copies the dependencies to the output folder to simplify debugging. However, since some features are not yet fully supported by the .NET proxy (for example, JDBC), you can also reference GigaSpaces.Core.Interop.Java.dll and work with Java classes directly. Unmanaged ReferencesIn-process Java-.NET interoperability requires an unmanaged component to bridge the managed platforms. Hence, the managed runtime library, netrtsn.dll, uses an unmanaged library called xmogrt.dll. Unfortunately, the Visual Studio dependency mechanism only detects managed dependencies, so the xmogrt.dll file is not copied to the output folder. Since the unmanaged library is required only at runtime, your project might compile successfully, but when you run it you will get an exception indicating that xmogrt.dll is not found. There are two common solutions to this problem:
|
![]() |
GigaSpaces.com - Legal Notice - 3rd Party Licenses - Site Map - API Docs - Forum - Downloads - Blog - White Papers - Contact Tech Writing - Gen. by Atlassian Confluence |