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!

Architect Forums - SalesLogix .NET Extensions
Forum to discuss the use of .NET Extensions in SalesLogix version 7 and higher. View the code of conduct for posting guidelines.

Forums RSS Feed

Back to Forum List | Back to SalesLogix .NET Extensions | New Thread

View: Search:

Author

Thread: .NET Extension Dependencies

drey
Posts: 16

.NET Extension Dependencies Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 19 Oct 10 10:36 AM

When adding a DLL in .NET Extensions Manager, the manager recognizes the dependent DLLs and adds it to the dependencies.

The .NET Plugins and dependencies are copied to the user computer path:

"C:\Documents and Settings\[user name]\Application Data\SalesLogix\NETPlugins\[saleslogix user]\[Plugin Name]

My problem is: Some of the dependent DLLs are common for several DLL plugins, and they are moved to the users computer several times .

I am trying to find a way to centralize the common dependencies, so they would not be copied every time to the user computer.

But, without installing them to the GAC.

I appreciate any help

[Reply][Quote]

Ryan Farley
Posts: 2265

Re: .NET Extension Dependencies Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 19 Oct 10 5:44 PM

Based on the way that .NET Extensions works (putting everything under a folder named the pluginid of the extension) I don't think you'll be able to do it without putting them in the GAC. Are the dependencies large in size? Does the fact that it does this create some sort of problem?

[Reply][Quote]

drey
Posts: 16

Re: .NET Extension Dependencies Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 21 Oct 10 5:17 PM

Yes, unfortunately we are running saleslogix on citrix and the DB is getting very big. I am using DevExpress controls and those DLLs are taking a lot of space.

[Reply][Quote]

Ryan Farley
Posts: 2265

Re: .NET Extension Dependencies Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 21 Oct 10 5:23 PM

Another way to do this is to have the .NET Extension just be an installer, which installs the applications in a common area. The app is registered as COM and set with the ComVisible attribute. Then the extension each time it is run checks to make sure it was previously installed and if so loads the components in using Win32 API calls. I've done this on many occasions (before .NET extensions exisited and since for other reasons). You can see an example of this on the article here: http://www.slxdeveloper.com/page.aspx?action=viewarticle&articleid=91

It's really the only way I can think of to accomplish this

[Reply][Quote]

Page 1 of 1

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!

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/22/2024 10:09:25 AM