Have you tried this: Go to solution explorer, click on the interop dll, in properties change “Embed Interop types” to FALSE. Best to use NuGet addon for .net studio and then add reference to wattin via “Add Library Package Reference”.
If you’ve installed and referenced WatiN using NuGet in VS2010, you should already have the correct references, so they don’t need to be removed and re-added. But you will still need to change the “Embed Interop Types” setting to False on the Interop.SHDocVw reference.
The Console output is not appearing is because the backend code is not running in the context of the test. You’re probably better off using Trace.WriteLine (In System.Diagnostics) and then adding a trace listener which writes to a file. This topic from MSDN shows a way of doing this. According to Marty Neal’s and Dave … Read more
Just want to say that I’m currently working hard on a beta release of WatiN 2.0 somewhere in Q1 of 2009. It will be a major upgrade to the current CTP 2.0 versions and will basically give you the same functionality to automate FireFox and IE as version 1.3.0 offers for automating IE. So no … Read more