Home | Forums | Contact | Search | Syndication  
 
 [login] [create account]   Saturday, February 22, 2025 
 
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 ThreadView:  Search:  
 Author  Thread: Control over how .net ext gets deployed
Steve Knowles
Posts: 657
Top 10 forum poster: 657 posts
 
Control over how .net ext gets deployedYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 15 Apr 08 7:08 AM
I need to deploy a .net extension that calls a web service to a citrix server farm with three servers. When I deployed automatically with the .net extension manager it deploys to a share that two of the three servers get a 'partially trusted caller' error when trying to access as a citrix user. Do I have any control over where the .dll is deployed to? I would like to deploy to each box, not a shared location. We were able to get the dll working for a couple of test users by changing the Application Data location from their user drive to the local drive of the Citrix server but the network admin will not accept this as a solution.

Also wondering if there is any documentation about how the .dll gets deployed - I am not sure I fully understand the process. Does the .dll get pushed out to each user/remote office/citrix entity? And can I direct whre the .dll gets pushed to for the citrix farm? Thanks
[Reply][Quote]
Ryan Farley
Posts: 2265
slxdeveloper.com Site Administrator
Top 10 forum poster: 2265 posts
 
Re: Control over how .net ext gets deployedYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 15 Apr 08 2:53 PM
You don't have any control over where they are deployed to. Not that this answers why this isn't working in your environment, but you don't *really* need to add them as extensions to use them like extensions. You could just install your binaries as needed on the machine and use them just the same. The only thing that extensions really manage for you is:

1) Deployment
2) Loading
3) Instanciation of the SlxApplication object

You could do those things yourself very easily. Anyway, just an idea.

-Ryan
[Reply][Quote]
Steve Knowles
Posts: 657
Top 10 forum poster: 657 posts
 
Re: Control over how .net ext gets deployedYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 15 Apr 08 2:58 PM
YOU could do those things very easily. lol. Seriously, how would I go about doing this? Would I need to deploy to each client? What would the code to call the dll look like?
[Reply][Quote]
Ryan Farley
Posts: 2265
slxdeveloper.com Site Administrator
Top 10 forum poster: 2265 posts
 
Re: Control over how .net ext gets deployedYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 15 Apr 08 3:07 PM
Quote:
Originally posted by Steve Knowles

YOU could do those things very easily. lol. Seriously, how would I go about doing this? Would I need to deploy to each client? What would the code to call the dll look like?


You would need to install your binaries on all three of the Citrix servers. The techniques described in this article would be exactly how you could do it (at least is one of many ways): http://www.slxdeveloper.com/page.aspx?action=viewarticle&articleid=91

Make sense?
[Reply][Quote]
Ryan Farley
Posts: 2265
slxdeveloper.com Site Administrator
Top 10 forum poster: 2265 posts
 
Re: Control over how .net ext gets deployedYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 15 Apr 08 3:13 PM
BTW, look at the screencast titled "Bonus Sample - Embedding a .NET Control in SalesLogix" towards the bottom. It will walk you through the entire process of doing this without using it as an extension.

-Ryan
[Reply][Quote]
Mark Dykun
Posts: 297
 
Re: Control over how .net ext gets deployedYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 16 Apr 08 6:56 AM
to get past the partially trusted caller exceptions you are having you will need to sign and register the assemblies in the GAC. This is a install process for each of the servers. I have done this for multiple clients and works like a charm.

Mark
[Reply][Quote]
Steve Knowles
Posts: 657
Top 10 forum poster: 657 posts
 
Re: Control over how .net ext gets deployedYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 16 Apr 08 9:54 AM
Mark, can you point me to some documentation on doing this?
[Reply][Quote]
Mark Dykun
Posts: 297
 
Re: Control over how .net ext gets deployedYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 16 Apr 08 10:05 AM
Hey Steve

http://support.microsoft.com/kb/910355

In VS 2005

1) Create a Setup project (under Setup and Deployment Projects templates).
2) Open the File System Editor (if it is not already open) by selecting the "View -> Editor -> File System" menu item.
3) For local file system files:
a) Select a desired folder in which to install the files (such as Application Folder) and add one or more files to the folder (right-click on folder and select "Add -> File...", and then select file).
b) Configure the properties for the folder to point to the desired destination folder on the target machine.
4) For installing into the GAC:
a) Right-click in File System Editor window and select "Add Special Folder -> Global Assembly Cache Folder" menu item to add the GAC folder to the list.
b) Add one or more assemblies to the GAC folder (right-click on folder and select "Add -> File...", and then select file).
5) Build your Setup project and then run the resulting Setup.exe (or execute the resulting .msi). During installation, Installer will copy the designated files to the destination on the target machine and install designated assemblies to the GAC. During removal, the Installer will reverse the installation process.

- Mark
[Reply][Quote]
Steve Knowles
Posts: 657
Top 10 forum poster: 657 posts
 
Re: Control over how .net ext gets deployedYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 16 Apr 08 10:20 AM
Thanks Mark. Will I need to just run this on the citrix servers or all clients?

I am doing well so far, but am not seeing Add Special Folder in 4a..
[Reply][Quote]
Mark Dykun
Posts: 297
 
Re: Control over how .net ext gets deployedYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 20 Apr 08 7:07 PM
Since citrix is hosting the client application for the user the install is only on each of the citrix boxes and not the clients.

- Mark
[Reply][Quote]
Steve Knowles
Posts: 657
Top 10 forum poster: 657 posts
 
Re: Control over how .net ext gets deployedYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 24 Apr 08 3:31 PM
More questions.. When SLX deploys the .dll it does so to a shared directory not on any of the 3 citrix servers in the farm. According to the KB article you pointed to me to (Mark D.) I need to run a comand similar to this: gacutil -I "C:\DemoProjects\GACDemo\bin\Release\GACDemo.dll" . Will a network share work here? I would need to run this on all three citirx boxes, yes?

I am really struggling with this but getting closer.. Thanks
[Reply][Quote]
Mark Dykun
Posts: 297
 
Re: Control over how .net ext gets deployedYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 24 Apr 08 5:12 PM
I do not believe that running from a network share will work for you in this case. Since you will have th dlls on a secondary machine you would continue to have security exceptions. When the assembly is registered in the gac is is pretty much copyed into the local windows assembly directory. The gac installation is only there to get past your security issues.

Mark
[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 © 2025 Customer FX Corporation. The information and opinions expressed here are not endorsed by Sage Software.

code of conduct | Subscribe to the slxdeveloper.com Latest Article RSS feed
   
 
page cache (param): 2/22/2025 8:40:04 AM