Hi - thanks for investigating. Unfortunately, I'm still running into the issue and it's an adoption blocker for my team. Here's a little more information (which will hopefully help identify the problem).
The WebUI extension is the only extension installed (and it is enabled). I'm running the test using code only. I get the same result running a test that I've written or one that is included in the framework's sample solution (if I change the call to LaunchNewBrowser(...) to specify Chrome). Chrome does actually launch and ActiveBrowser.Navigate(...) executes without throwing an exception, but Chrome does not actually navigate to the desired page; it just displays "Preparing browser for automation...".
In the following code snippet (from the framework's sample .sln), the test will run until Find.ById(...) is called, at which point an exception will be thrown because the page containing the desired element was never navigated to. This works fine using FF and IE (but not Chrome).
Description("Clicking an element on the page.")]
public void ClickAnElement()
// Launch an instance of the browser
// Some test cases may require that all cookies be cleared ahead of time.
// WebAii does not care but depending on your environment and your specific
// test case you may care.
// Navigate to the test page
// Find the elements on the page using the Find.BYxxx methods.
Element toggleOn = Find.ById("btn1");
I've also tried restarting by machine after installing the framework and setting Chrome to run as administrator, but still no luck.
Any help is appreciated!