Hi Jean-Louis,
I have a 64 bit .net api for Remedy, but it's one that I wrote and is not
based on the community version. A few facts about it...
- I began work on my .net API nearly 10 years ago because I needed one that
provided more functionality and flexibility than the community version did
at that time. Mine has now been in production use, in one way or another,
for over 7 years now (at clients such as Google & eBay/PayPal), so it's
very stable and robust.
- That said, I have not looked at the object model of the community version
since, nor have I ever familiarized myself with the object model in the
Java API, so I have no idea how closely mine matches those. However, it'd
be hard to imagine that they're very different.
- Mine is based on and uses the C API. So it was only with v8.1 (or was it
8.0?) when they published the 64 bit C API that I was able to upgrade to 64
bit.
- Since I've been pretty much the only user of this work, the external
documentation is lacking (which is primarily why I've never tried to
publish the work). But it's pretty well documented internally (for
intellisense).
- It's largely build using code generation tools I created that allow me to
very easily keep pace with new versions of Remedy and any changes they make
to the API.
- It covers most of the C API, though I have not yet coded for some of the
newer, more esoteric functions.
- It "comes with" add on tools such as ARFormToClass, a program that
creates a set of classes based on specific Remedy forms that allows for
very easy and type-safe (and tightly bound) programming against those
forms. Here's an example of making some changes to an imaginary Customer
form:
//
// Create the server connection
MCSARServer arServer = new MCSARServer("host", "username", "password");
//
// Loop thru the relevant Customers
foreach (CUSTForm.Entry custEntry in CUSTForm.Query(arServer, "'Status' =
\"Sad\"")) {
//
// Update the Status to be Happy
custEntry.Status = CUSTForm.StatusType.Happy;
//
// Set the 'Formal Name' to a combination of the 'First Name' and 'Last
Name'
custEntry.Formal_Name = custEntry.First_Name + ' ' + custEntry.Last_Name;
//
// Update the entry
custEntry.SetEntry();
}
I recognize that you probably have a body of work based on the community
version and don't want to consider refactoring to use mine. But if you do
find you're interested I'd be willing to consider distributing it to you,
including source code, under GPLv3. I'd also be happy to help bring you up
to speed on usage.
-charlie
On Wed, Nov 12, 2014 at 11:35 PM, Jean-Louis Halleux <supp...@arsmarts.com>
wrote:
> Hello listers,
>
> Does anyone know about a 64 bit version of the .net api ? Are there any
> plan to make them one day ?
>
> Thanks a lot for your input.
>
> Jean-Louis Halleux
>
> http://mailtrack.me/tracking/raWzMz50paMkCGR2ZGp1AQVjZGRzMKWjqzA2pzSaqaR9ZGRjZmpmAGt2Way2LKu2pG0mZwDjAmN0BQRjZD
>
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> "Where the Answers Are, and have been for 20 years"
>
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"
