Home | Forums | Contact | Search | Syndication

[login] [create account]   Thursday, November 21, 2024

slxdeveloper.com   Home   Search   Contact us   About slxdeveloper   Syndication  Community   Forums (NEW!)   Newsletter Archive  Members   Your Profile   Submit Article  General   Administration (6)   OLE DB Provider   Miscellaneous (2)  Architect   VBScript (9)   ActiveX Controls (6)   How To's (14)   .NET Extensions (3)  External   OLE DB Provider (12)   SLAPI (SlgxApi.dll)   SalesLogix COM (1)  Web   ASP/ASP.NET (2)   Web Services   Web Client  Downloads   Samples (17)   Documentation (7)   Utilities (18)  Resources   SalesLogix (3)   Programming (1) 11/21/2024 3:50:37 PM slxdeveloper.com Now Live!   View User Profile    User Profile - Jason Lindsay     Jason Lindsay (SalesLogix Business Partner) Unison, Inc. fjrigjwwe9r1SiteUser:UserBio fiogf49gjkf0d Log in to send this member a message!    Jason Lindsay's Contributions Jason Lindsay has contributed 1 comments and 0 articles.   Select to view: Comments  Articles  Comment: Re: Introduction to .NET in SalesLogix Version 7 fiogf49gjkf0d I'm wondering how exactly the .NET extensions deploy out to the client. Do the dll's have to reside physically on each remote computer for them to work correctly in the client, or can they simply be invoked from the server? We have some extensions that are working correctly for some users, but not working at all for others, and we can't seem to isolate the problem to the existence of the extension dll files on individual workstations. Being new to the SalesLogix environment, I'm a little confused on exactly how these extensions are deployed. Thanks! Jason Lindsay Unison, Inc. Author: Jason Lindsay - 6/4/2008

slxdeveloper.com is brought to you courtesy of Ryan Farley & Customer FX Corporation.  This site, and all contents herein, are Copyright © 2024 Customer FX Corporation. The information and opinions expressed here are not endorsed by Sage Software. code of conduct |

page cache (param): 11/21/2024 4:03:32 PM