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!
|
|
How to Setup Visual Studio 2005 as a Debugging Environment for SalesLogix 7.2
Posted: 27 Aug 08 3:48 PM
|
I hope someone can help me.
I've seen many posts saying how wonderful VS 2005 is for debugging SLX VBScripts. However, I can't seem to find any that explain how to configure this. Microsoft Script Debugger comes up when an error is encountered since I have that installed. But how do I get VS 2005 to come up?
Thanks for your help
Tim |
|
|
|
Re: How to Setup Visual Studio 2005 as a Debugging Environment for SalesLogix 7.2
Posted: 27 Aug 08 10:20 PM
|
OK, got it working and it is WELL WORTH IT!!
But how?
1. Install VS 2005 and SP1
2. Uninstall old Microsoft Script Debugger (don't need and didn't know if it could be disabled)
3. In VS 2005 go to Tools;Options and in the lower left hand corner check the box "Show all settings." Debugging Options are now available. In the Just-In-Time section I checked all three boxes and left everything else default.
4. In SalesLogix use the SalesLogix Administrator Utility and once open, select the User you'll be debugging with and open the Users Profile
5. Choose Client Settings and in the Script Debugging dropdown select "On Error."
6. Run the buggy code and when it errors, close the SLX Error dialog and choose New Instance of VS 2005.
7. At this point I got an error that requested I reinstall VS 2005 if the error persists. It did, so I did. At this point I installed VS SP1 and rebooted.
8. The VS 2005 Dev Environment came up.
Lots of other problems installing SP1 on 2003 Server, but google it and follow the instructions on what you find. This is definitely nice to work in.
Tim  |
|
|
| |
|
Re: How to Setup Visual Studio 2005 as a Debugging Environment for SalesLogix 7.2
Posted: 28 Aug 08 9:34 AM
|
Tim,
I hit reply last night and I guess it never got posted, but one thing I learned after getting debugging working was that the Stop keyword will launch the debugger for you. Makes it easy if you know where you want to step through and force it to break. Until I learned that, I'd intentionally divide by zero or some other nonsense to launch it. I like stop much better.
Jeff
|
|
|
| |
| |
| |
| |
|