Below is the list of issues fixed in WebAii 1.1:

Reported bugs on the forum fixed:

1. CPU Utilization issue : http://artoftest.com/CommunitySite/forums/p/198/757.aspx#757.
2. FrameIndex issue: http://artoftest.com/CommunitySite/forums/t/235.aspx. Regarding this bug, the change was to lazy load the frames on demand instead of always having all frames loaded. There are no breaking changes.
3. BaseUrl issue: http://artoftest.com/CommunitySite/forums/p/242/940.aspx#940
4. 64Bit and Vista support: http://artoftest.com/CommunitySite/forums/p/162/834.aspx#834. Note with Vista, IE needs to have IE Protection Mode turned off (Tools/Options/Security tab, uncheck the protected mode)
5. FindParam fixtures issue: http://artoftest.com/CommunitySite/forums/p/256/1020.aspx#1020
6. VS2008 templates issue: http://artoftest.com/CommunitySite/forums/p/191/1027.aspx#1027

Feature requests implemented:

1. Annotator to filter based on native/custom annotations. The annotator now has an Annotation Mode in the Settings object. Annotation can be set to [1. All (default/legacy behavior), 2. CustomOnly. Only custom annotations coming from the test code are displayed, 3. NativeOnly. Only native annotations from the WebAii framework are displayed]
2. Allow the AspNet Development Port to be set (http://artoftest.com/CommunitySite/forums/t/266.aspx). The Settings object now allows you to set the AspNetDevServerPort.
3. HtmlTable now has Table.ColumnCount
4. Logging actions from the Annotator to the log: http://artoftest.com/CommunitySite/forums/t/268.aspx. You can now enable this by setting Settings.LogAnnotations = true;
5. FindParamAttribute now also Frame aware. You can describe elements on specific frames by name or id. An Elements[] accessor is now available off the Manager object that allows you to find an element on any frame. (If a frame is defined as part of the FindParamAttribute, it will find the Browser object frame and use its Find object to find the element.
6. Waiting on an element to exist can now be achieved using a simpler syntax. The Element object now has a public constructor that takes in a FindParam. You can then call the Wait.ForExists() for that element to be found on the page. Once the element is found, you can simply start using it! Pretty sweet... You can also use this with an HtmlControl... Check out this post: http://artoftest.com/CommunitySite/forums/p/302/1134.aspx#1134
7. LINQ. All Find objects now have a AllControls or AllElements properties. These properties return IEnumerable which can be use to enumerate through the entire page collection using a Linq expression. The AllControls filter on a specific control type to use for your LINQ expression. We will dedictate a blog post about this topic.. Example:

// Query for all links on the page that have an Href that ends with foo.jpg

IEnumerable<HtmlAnchor> myLinks = (from link in f.ActiveBrowser.Find.AllControls<HtmlAnchor>() where link.HRef.EndsWith("foo.jpg") select link);

And finally, the performance and Assert extensions described here: http://artoftest.com/CommunitySite/blogs/artoftest/archive/2008/02/28/webaii-1-1-and-verification-patterns.aspx

Please give 1.1 a try and let us know how your experience have been...