![]() ![]() With Microsoft Visual Studio Express 2013 the debugger integration has improved. And believe me, you will need the debugger. Nor did the debugger offer the option to Attach To Process, which would have allowed you to start SAS Enterprise Guide, get your task loaded in, and then attach a debugging session to hit your breakpoints. The integrated debugger in the Express edition did not allow you to debug into an external application - anything that you didn't build in the tool. ![]() NET code library (DLL file) - necessary for a custom task - you had very few options for debugging it. While you could use the Express tools to build a. In my book, I also provided a stern caution about using the Express editions. After 30 days, you must "sign in" to the tool with a Microsoft account, but the account is free too. ![]() You can download them from Microsoft's developer site and use them free-and-clear for 30 days. The advantage of the Express editions is that they are free. I even provided step-by-step instructions for how to get started with your first custom task. And I said as much in my book, Custom Tasks for SAS Enterprise Guide Using Microsoft. It's true: you can use the Microsoft Visual Studio Express tools to build custom tasks for SAS Enterprise Guide and the SAS Add-In for Microsoft Office. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |