11/25/2024 4:22:03 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 general external development topic (related or not to SalesLogix development). View the code of conduct for posting guidelines.
|
|
|
|
Visual Studio Integration
Posted: 17 Mar 06 9:33 AM
|
buy low dose naltrexone online naltrexone buy uk click here ok maybe integration is a poor word.. I have seen post in various places that you can launch the saleslogix application within the visual studio framework.. work on scripts in there using the ability to debug on the fly and modify scripts as needed. However when you save them you have to cut and paste back into the Architect. Does anyone have the steps for me to follow so I can try and have this functionality work..? |
|
|
|
Re: Visual Studio Integration
Posted: 17 Mar 06 10:55 AM
|
There is no Visual Studio integration per se for SalesLogix (at least not in this version ), however there are some things you can do to use VS with SalesLogix in a limmited capacity.
You can debug scripts in VS, basically VS registers itself as a debugger on the system, if you choose to have VS debug on error it will ask to launch the debugger for you and load the script in question. At any time, however, you can attach to the SalesLogix process from VS to see what scripts are executing, set break-points, see the call stack, variables, etc etc etc. But this does not mean that you can edit (or create) the scripts there. You can only debug them (they are read only in the debugger).
So...
1) Debugging in VS....Yes 2) Creating or editing scripts/plugins in VS....No 3) Creating .NET forms and launching in SLX....Yes
I really don't like VBScript, so any chance I can develop in .NET and just integrate things into the client I do it. By far the way to go IMO. In v7 there will be native support for building .NET form and code in VS and loading them into SLX, although it is somewhat limited (don't expect the same way you can just create an activeform in architect now)
-Ryan |
|
|
|
Re: Visual Studio Integration
Posted: 17 Mar 06 12:14 PM
|
cheap abortion clinics in md abortion pills online cheap click Ryan, is it possible to actually call the application to run within the VS enviorment..? not just when it needs debugging |
|
|
|
Re: Visual Studio Integration
Posted: 17 Mar 06 1:45 PM
|
fiogf49gjkf0d You can attach to the SLX process from inside of VS (is that what you mean by "call the application to run within the VS enviorment"?)
To attach to SLX, open VS (no need to open a solution/project) and then go to "Tools" and then "Attach to Process". Then find "SalesLogix.exe" in the list of running processes, select it and click "Attach". Now you are attached to SLX. From here you'll want to open the Script Explorer window by going to "Debug", "Windows", and then "Script Explorer" (or CTRL+ALT+N). This will show you all script documents loaded by SLX (unfortunately they'll all be named "blank"). You can double-click on any of them to see the VBScript code. Set break points as needed, execute commands in the immediate window, see the locals loaded as they run, set watches, view the call stack etc. But as I said before, you'll only be able to debug these scripts, not modify them or anything.
Does that help
-Ryan |
|
|
| |
|
Re: Visual Studio Integration
Posted: 21 Mar 06 3:20 PM
|
buy the abortion pill abortion pill buy online where can i buy the abortion pill online where to buy naltrexone naltrexone where to buy click You can launch and automate SalesLogix from a .NET app, Delphi, VB6, etc., using COM. SalesLogix.exe is an ActiveX EXE; instantiating a SalesLogix COM instance establishes a link between an app and the currently running instance, or else a new instance of, SalesLogix. Most things in the Application object you might see in script are exposed in COM (SlxApplication/SlxApplication2 class, I believe). This post is not a tutorial, you will have to look up the COM reference documentation.
For viewing and debugging scripts at runtime, attach the process (as Ryan described). The COM interface is different from the debug attachment used by the Active Scripting engine.
However, to modify scripts you will need to access the Data BLOBs in the Plugin table. Doing so outside of Architect or Bundler/Administrator is unsupported by Sage; do so at your own potential demise. |
|
|
|
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!
|
|
|
|
|
|
|
|