Of course, yes!! :-) So use Windows Update & get the .NET Framework (if not done so already). [The .NET API is built/tested with .NET Framework v1.1.4322 (MS VS.NET 2003), however it does work with 1.1 as well as 2.0 deployments (MS VS.NET 2005). We have not tested with .NET Framework 3.x (MS VS.NET 2008) yet.] Appajee
________________________________ From: Action Request System discussion list(ARSList) on behalf of Grooms, Frederick W Sent: Fri 10/12/2007 11:40 AM To: [email protected] Subject: Re: .NET api and related files Just off hand ... Wouldn't you also need Microsoft .NET installed on any machine that is going to run a program that uses the .NET API? -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Papolu, Appajee Sent: Friday, October 12, 2007 1:02 PM To: [email protected] Subject: Re: .NET api and related files Jarl, .NET API is a self-contained distribution (given out as a ZIP file) available at the BMCDN site. So it contains all of the files (most important being BMC.ARSystem.DLL, then arcni71.dll then the typical AR C API binaries such as arapi71/arrpc71/arutl71.dll/so on, then their dependencies such as icuXXX.dll etc; also the cmdb*.dll as well) one needs to build an AR API application using .NET/COM environments. As you can quickly validate by extracting this distribution to a folder and comparing the contents with that of a User Tool instance -- there is quite a overlap between these files. If you want to distribute AR .NET API app into a system that already has **matching** version User Tool -- then technically speaking --- you can do this : a. User User Tool installation directory as .NET API install dir as well; b. Copy over the .NET API distributed files onto User Tool installation dir (to be safe, you could back up original dir; OR choose to copy only .NET API specific files alone, about 3-5 of them & ignore copying pre-existing same named files); c. then complete the installation steps described in readme. Things should work just fine. While that is the case, I suggest you to consider aspects such as -- testing this approach on a dev box; pros/cons of keeping .NET API install dir separate from User Tool's (Vs. overloading User Tool install dir as that of .NET API's as well) Appajee ________________________________ From: Action Request System discussion list(ARSList) on behalf of Jarl Grøneng Sent: Fri 10/12/2007 7:01 AM To: [email protected] Subject: Re: .NET api and related files Hi, I now, but that was not my question. My question was if I need additionals dll's to use the .NET api on a client where the user tool is installed. - Jarl On 10/12/07, CONDREA, Daniel <[EMAIL PROTECTED]> wrote: > Hello Jarl, > > There is no need for User Tool to use ".NET api" > > If you need just to read data from an ARS server you do not need ".NET api". > Use ARODBC to read data from an ARS server. > > Best regards, > Daniel Condrea > > -----Original Message----- > From: Action Request System discussion list(ARSList) [mailto:[EMAIL > PROTECTED] On Behalf Of Jarl Grøneng > Sent: Friday, October 12, 2007 12:40 PM > To: [email protected] > Subject: .NET api and related files > > Hi, > > There is a need to create an excel sheet that does a query into AR System. I > have an understandment that this can be done using the .NET api from inside > excel. > > Question: > Is there any need for additionals files to be installed on the clients other > than user tool 7.1 to get this working? We need to know if we need to > distribute additionals files to the clients. > > > Thanks, > Jarl _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
