The pain of Guidance Automation Toolkit

I'm telling you, writing guidance packages using GAT can be infinitely frustrating! At least on my rather slow laptop with a measly 1 Gb of RAM. Why is that, you might ask yourself? Well, here's the process you use when finding errors in a package:

  1. Rebuild your package (about 45 seconds)
  2. Register your package (about 90 seconds)
  3. Open a new Visual Studio 2005 instance (about 30 seconds)
  4. Create a solution using your new package (about 30 seconds)
  5. Realize that you've made yet another stupid mistake (less than 1 second)
  6. Shut down the new Visual Studio instance (10 seconds)
  7. Fix the bug (a second or two)
  8. Repeat

Sure, it might not sound that bad, but remember that there is hardly any compile-time checking going on here and I'm making tons of spelling errors and other stuff that would usually be caught by the compiler. This is going to take me the rest of the week.. Easily..

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

About Me

Consultant, Solution Architect, Developer.

Do note that this blog is very, very old. Please consider that before you follow any of the advice in here!


%d bloggers like this: