|
Re: Sage.SalesLogix.NetExtensions.Framework.dll
Posted: 10 Jul 09 5:12 AM
|
James:
Are you working remotely?
If not, then you shouldn't have to develop remotely (e.g. via the Citrix server).
If that is the case, you would want to install SalesLogix client and Administrative tools locally, and then configure the SLX Extensions. By doing so you will have all necessary files on your machine, which I would assume is where you have your development tools.
Once you have developed your tools and are ready to deploy, you would use SLX Architect to move the changes into Production and that would make the changes available to the users (off course, the Citrix server would need to be properly configured as well).
Also, keep in mind that you should not be working out of the production environment, you should setup a Separate Development environment that doesn't conflict with production (separate database, separate Logging Path, distinct Site Code, etc). And by the same token, once you have built your changes, you would want to have a Stage environment that would be a clean copy of production on which you would deploy your changes and test before going live. (And you would want if possible for this environment to also replicate your Citrix setup, I mean are you doing App Publishing? If so, you would want to test your code under the same configuration).
Lastly, depending on the licensing level of your organization, there may be restrictions in place. You either need to have SalesLogix Premier or a Premier Architect (and External Access if needed). [Disclaimer: I am not a licensing expert] |
|
|