There were a couple of recent posts in the forum asking what GAT was and how one gets started on using this, so I thought of writing a post to cover the answers.
Let’s just take one aspect: Say for example architecting the data access in software solutions developed at your company.
You might define whether it be using CRUD operations or using an ORM. Once you decide on the architecture you want all your developers to follow that methodology along with the best practices.
One way that you give guidance to your developers is through writing a document with all the relevant guidelines. Another option that you could do is build a utility that let’s the developer walk through a wizard which would then generate the skeleton or handle most of the mundane things like writing the insert, update sp’s and related .NET code.
Now building a utility like this takes a lot of time and effort, this is exactly where GAT fits in. It let’s you define the guidance to developers in an easier manner (than if you were to write your own) so that it becomes very easy for your developers to follow the guidance that you have defined. They don’t need to read long documents but can instead use the toolkit that you provide.
The best way to learn GAT is to practice it. Try out this HOL (Hands-On Lab: Data Client Application) which walks you through creating a guidance package for generating the data access classes as well as connecting them to a simple smart client.