Menu

#8 QuickFocus not working in Windows XP SP2

open
nobody
None
5
2007-03-13
2007-03-13
Anonymous
No

I am running Windows XP with SP2, and only have .NET 2.0 installed (uninstalled 3.0 and reinstalled ieunit). Quick focus fails to even launch, it starts with an error and the program will not run. The windows debug information failed to give any useful information. I have installed all the latest patches from Microsoft, and nothing seems to allow quick focus to start running. I run the program as an administrator user, and have installed it for everyone, and just for me, and neither have helped either.

Discussion

  • Nobody/Anonymous

    Error Message I receive

     
  • Anonymous

    Anonymous - 2007-03-17

    Logged In: YES
    user_id=621533
    Originator: NO

    This seems to be tough problem. I have been using QuickFocus
    on Windows XP+SP2 most of the time, but never encountered this
    problem. I suspect that there is some incompatibility between
    QuickFocus and certain components on your machine.

    Since QuickFocus is open sourced, I'd suggest you to
    debug this issue youself on that machine. To simplify the
    process I have packaged the whole IeUnit source code
    as a single zip file. The following are suggested steps
    to debug QuickFocus:

    1. Download and install Visual Studio C# Express from
    http://msdn.microsoft.com/vstudio/express/ (it is free).
    Skip this step if you already have Visual Studio
    installed on that machine.

    2. Download and unzip IeUnitSrc.zip from
    http://www.visumap.net/index.aspx?p=Resources&q=WebTesting.

    3. Click on the IeUnit.sln file to start IeUnit project
    with Visual Studio. Then, press F5 key to start
    QuickFocus under debugger.

    The zip file contains a debuggable executable QuickFocus.exe.
    If you don't feel confortable to debug C# program, you
    can try to start the debugable QuickFocus.exe from the zip
    file. If the program shows more meaningful
    message, please post them to this place. I might be
    in better position to solve this issue.

     

Log in to post a comment.

MongoDB Logo MongoDB