Home | Forums | Contact | Search | Syndication  
 
 [login] [create account]   Saturday, June 7, 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: .NET Extensions Deployment
Ingmar Schaefer
Posts: 4
 
.NET Extensions DeploymentYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 21 Jun 07 10:36 AM

I have successfully created a .NET extension and I am able to access it from the sales client on the machine where the admin tools are installed without any problems.

But using a sales client on another machine (same login) did not work.
So I used the "Deploy All" menu item within the Extension Manager, which created an sxb bundle file. I then installed this bundle using Administrator and restarted the client on the other machine.
Unfortunately, the extension is still not available on this one (the handle returned by app.Managed.Create is always empty).

Is there something I am missing that needs to be done in order to make this work?
Any ideas?

Thanks in advance,
Ingmar
[Reply][Quote]
Ryan Farley
Posts: 2265
slxdeveloper.com Site Administrator
Top 10 forum poster: 2265 posts
 
Re: .NET Extensions DeploymentYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 21 Jun 07 3:56 PM
Hi Ingmar,

Basically you create the bundle and then apply to the other system or you can load up the Extensions Manager on the other system and load the assembly in there.

If you open the assembly in the extension manager on the other system does anything look different than on the first system?

One other thing I've seen on occasion is that the .NET extensions stuff didn't get properly registered on a machine. If this is your case you can manually rerun the registration by running the batch file location in the SLX dir named "RegisterSLXNetExtentions.bat". Give that a try.

-Ryan
[Reply][Quote]
Ingmar Schaefer
Posts: 4
 
Re: .NET Extensions DeploymentYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 22 Jun 07 2:04 AM

Thanks, Ryan!

After running "RegisterSLXNetExtentions.bat" on the other machine everything worked fine.

I hope I will not have to do this on each client when we roll out the new version...

Ingmar
[Reply][Quote]
Jeff Weight
Posts: 219
 
Re: .NET Extensions DeploymentYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 22 Jun 07 12:52 PM
This post is to everyone in this newsgroup.

I ran into this same problem, and I called SalesLogix tech support. They gave me the same answer, and it worked as well. Ingmar's hope at the end of the message before this message is my hope as well. .Net Extensions should work on any installation of SalesLogix, not after digging through newsgroups and calling tech support, only to find you have to get access to installation privileges and perform a separate installation on every machine. It looks like, according to Ryan, this only happens sometimes - and from what it looks like to me, it happens on any machine where SalesLogix is installed using a built client network install, not the install disk.

Anyway, last time I complained about something being a defect (remote office creation errors out if you set up a join on an enabled view in the join manager), tech support said it technically wasn't a defect, that I should submit it as a feature request, and that if enough people requested to have it taken care of, the product manager would probably take care of it (Really? You think someone out there is fine with failure on creating a 5 gig remote office database?) So, if any of you wouldn't mind, please take a moment to log into Support.SalesLogix.Com, click on "Feature Request" in the bottom left corner, and fill out the form requesting automatic .Net Extensions install.

Thanks!
[Reply][Quote]
Jeff Weight
Posts: 219
 
Re: .NET Extensions DeploymentYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 25 Jun 07 9:54 AM
So, after speaking with my business partner, Unison, about this, they mentioned that it should be part of the install package for the client if you choose to build a separate client install. I took a peek, and indeed, it is listed. However, it is checked by default, and I am 99.9% sure I did not uncheck it - which means, despite it being checked, .Net Extensions were not installed. Does that mean this is a defect?
[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): 6/7/2025 6:04:58 PM