2/19/2025 3:58:13 PM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss the use of .NET Extensions in SalesLogix version 7 and higher. View the code of conduct for posting guidelines.
|
|
|
|
Dependancies not found when adding a .NET extension
Posted: 14 May 09 12:55 PM
|
Hi all,
I have a created a simple .NET extension to pass a value from SLx to call another .NET DLL function. When I attempt to add the .NET Extension (with what it is calling in the same directory) within the Saleslogix .NET Extensions Manager, I get a message of:
|
|
|
|
Re: Dependancies not found when adding a .NET extension
Posted: 15 May 09 9:00 AM
|
Update:
Forgot to mention that this was v7.0.1, in case it makes a difference.
I added all the DLLs that the child DLLs were dependant on and was able to add the .NET extension (including 37 dependancies). On my client's machine this resulted in errors at runtime about the assembly not allowing partially trusted callers (even after I added the attribute AllowPartiallyTrustedCallers).
After all that I recompiled as a COM visible class and called via COM from SLx without issue.
James |
|
|
|
Re: Dependancies not found when adding a .NET extension
Posted: 16 May 09 10:30 AM
|
I've run into a similer problem and found that if I can get the DLL into the directory where SLX deploys the assemblies, the app will run.
Where it deploys looks like:
C:\Documents and Settings\[username]\Application Data\Saleslogix\NETPlugins\[servername]\[dbaliasname]\[user]\[.net extension name]
My situation has a DLL that is not picked up in dependencies, and I can't import to .net extensions directly.
I don't have a solution yet either, but am considering putting the additional files in the library, force them out to all users, and then have the Initialize function (or the vbscript wrapper) copy them to the appropriate .net extension folder prior to running it.
I have not had a chance to try this out yet, and it is kind of low on the list at the moment.
Please keep us all posted on your progress - you're not the only one with this issue.
ws |
|
|
|
Re: Dependancies not found when adding a .NET extension
Posted: 27 May 09 4:24 AM
|
Walter,
To be honest I gave up on the .NET extension in this instance and use a COM enabled DLL instead. Just felt we were going from one error to another, so sought an alternative.
I suspect that adding the dependant DLLs into the same folder as the .NET extension caused some kind of additional complication, as they were also in the GAC, but with all the other dependancies that we did not need to add the .NET extension.
James |
|
|
|
Re: Dependancies not found when adding a .NET extension
Posted: 02 Nov 09 1:23 PM
|
We ran into this as well. What we did was simply create a variable with the type of an object that was in the .dll we needed.
Something like this:
MyObjectType myVariableName = null;
Doing this was enough to cause SLX to realize it needed this .dll as a dependency and would then copy it over to the clients.
Hope this helps. |
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|