Book Image

Mastering Microsoft Forefront UAG 2010 Customization

Book Image

Mastering Microsoft Forefront UAG 2010 Customization

Overview of this book

While UAG is built to integrate with many environments and publish dozens of application types, many organizations require a certain level of customization to meet their needs. With this book in hand, you will be equipped to deal with these types of customization scenarios, and you will be confident in using such workarounds without hassle and trial and error. Written by some of the leading experts on UAG, "Mastering Microsoft Forefront UAG 2010 Customization" covers the most complex and challenging options for customizing UAG in a way that is friendly and easy to follow. It walks you through various customization tasks, including explanations and code samples, as well as creative ideas for troubleshooting your work. Until now, only a few of the extensions to UAG's services have been publicly available, and most were only known to a select few. Now, this can include you! Throughout this book, you will tackle how to change the system's look-and-feel, deal with advanced authentication schemes and write special functions that need to be executed as part of the client interaction. With "Mastering Microsoft Forefront UAG 2010 Customization", you too can learn how to customize various aspects of UAG's functionality to enhance your organization or customers' experience.
Table of Contents (16 chapters)
Mastering Microsoft Forefront UAG 2010 Customization
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface

Troubleshooting and debugging detection scripts


Even though you can test changes you make to the detection script as you develop it even without an activation (except with array configurations, as noted earlier), you do need to close the browser on the client and re-open it to test again. This type of trial-and-error can be frustrating, but there are other things you can do. The easiest way to keep an eye on things during development is by the use of the MSGBOX command to output harvested data. Simply embedding these into your code will allow you to observe the response of each function as you step through the script, plus the information that was collected. For example, consider the following screenshot:

Using so many of those may seem like over-kill, but it's exactly the kind of methodology that will help you isolate those little annoying typos that could take hours to find otherwise. Did you notice the bug above? Line 4 names the variable incorrectly (stsVuzepath instead of strVuzepath...