02.04.2013 Views

Custom Tasks for SAS® Enterprise Guide® Using Microsoft .NET

Custom Tasks for SAS® Enterprise Guide® Using Microsoft .NET

Custom Tasks for SAS® Enterprise Guide® Using Microsoft .NET

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 1. Why <strong>Custom</strong> <strong>Tasks</strong>? 11<br />

of the source code that you need to build the examples and modify them <strong>for</strong> your own use. Some<br />

examples are provided in the C# language, some in Visual Basic .<strong>NET</strong>, and some in both.<br />

You do not need to understand how these tasks are built be<strong>for</strong>e you use them. You can simply deploy<br />

them into your existing SAS <strong>Enterprise</strong> Guide installation and explore some of the capabilities that you<br />

can add with custom tasks.<br />

Exercise: Download, Deploy, and Access <strong>Custom</strong> <strong>Tasks</strong> from SAS<br />

In preparation <strong>for</strong> this book we have built a collection of custom tasks that illustrate many of the<br />

possible features that you can implement. Most of these examples are described in greater detail later<br />

in this book, but <strong>for</strong> now you can deploy a read-to-use DLL that contains the tasks, and see them in<br />

action.<br />

To download the example custom tasks, follow these steps:<br />

1. <strong>Using</strong> your web browser, navigate to http://support.sas.com/hemedinger [Note: example code<br />

and data will be available on this page once the full book is published.]<br />

2. Click on the "Ready-to-use custom tasks examples" link. The link refers to a ZIP archive file.<br />

Use your web browser to download the ZIP file to your PC.<br />

3. Navigate to the location where the ZIP file is located, and extract the contents of the ZIP file<br />

to a folder on your PC. The ZIP file contains a DLL named SAS.<strong>Tasks</strong>.Examples.DLL.<br />

4. Copy the DLL file to the appropriate custom task folder on your PC, according to the version<br />

of SAS <strong>Enterprise</strong> Guide that you are using. For example, if using SAS <strong>Enterprise</strong> Guide 4.3,<br />

the location is "%appdata%\SAS\<strong>Enterprise</strong>Guide\4.3\<strong>Custom</strong>". (For the list of folders to use<br />

<strong>for</strong> each of the different versions of SAS <strong>Enterprise</strong> Guide, see the section about "drop-indeployment"<br />

earlier in this chapter.)<br />

Tip: The %appdata% location is specific to your local Windows profile, and the folder<br />

structure varies among different versions of Windows. An easy method <strong>for</strong> navigating to the<br />

proper folder is to open a new Windows Explorer window, and type "%appdata%" (without<br />

the quotes) in the address bar.<br />

5. Start SAS <strong>Enterprise</strong> Guide. In the Tools->Add-Ins menu, you should see several new menu<br />

items that provide access to the example tasks.<br />

6. Select one of the task menu items to launch your first custom task!<br />

Chapter Summary<br />

<strong>Custom</strong> tasks provide a powerful way to extend SAS business intelligence applications. They aren’t<br />

the only way to present custom features to your end users, but they are often the most flexible<br />

mechanism. When you need them, nothing else will do.<br />

Hemedinger, Chris. <strong>Custom</strong> <strong>Tasks</strong> <strong>for</strong> <strong>SAS®</strong> <strong>Enterprise</strong> <strong>Guide®</strong> <strong>Using</strong> <strong>Microsoft</strong> .<strong>NET</strong>. Copyright © 2012 SAS Institute Inc.,<br />

Cary, North Carolina, USA. ALL RIGHTS RESERVED. For additional SAS resources, visit support.sas.com/bookstore.<br />

Draft copy <strong>for</strong> promotional purposes. Additional changes may be made during the production process <strong>for</strong> the book.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!