none
AppVerifier does not create logs RRS feed

  • Question

  • We are testing our .net application prior to submission for certification and find that when testing it on a 64-bit system with the application verifier no logs are created. I have tried other .net applications and no logs are created. Notepad creates a log. On a 32-bit system. logs are created. This had been tested on 64-bit Vista Ultimate and 64-bit Windows XP, the latter running on and AMD processor, the former on an Intel Xeon E5420, both running on virtual machines on VMware workstation.

     

    Is this a know issue with the application verifier and .net applications and if so how do we proceed for certification?

     

     

    Friday, August 22, 2008 2:54 PM

Answers

  • Thank you for your question.

     

    I hope the below information is helpful to you:

     

    1.       Are you running Windows operating system inside of VMWare? Just FYI – this may be valid for your pretesting, though is not supported by Logo Program. All final Logo testing will be performed on Windows Server 2008 64-bit or Vista SP1 64-bit, physical or Hyper-V based OS.

    2.      Q/A for Application Verifier:

     

    Where are the logs stored?

    By default, the logs

    for services/apps running under user account are under: %USERPROFILE%\AppVerifierLogs

    for services/apps running under local service account are under: %windir%\serviceprofiles\LocalService\AppVerifierLogs

    for services/apps running under network service account are under: %windir%\serviceprofiles\NetworkService\AppVerifierLogs

    for services/apps running under system account are under: %windir%\system32\config\systemprofile\AppVerifierLogs

     

    Does Application Verifier verify managed code?

    AppVerifier cares about the interfaces between the operating system and the application. As a result, unless your managed code is performing interop against native APIs that have to do with Heaps, Handles, Critical Section, etc. your test cases are not going to give you any interaction with the interfaces that are verified.
    We recommend leveraging the Managed Debugging Assistants for verifying your managed code. Please read more about them on
    MSDN.

     

    Hope this helps,

     

    Friday, August 22, 2008 11:18 PM

All replies

  • Thank you for your question.

     

    I hope the below information is helpful to you:

     

    1.       Are you running Windows operating system inside of VMWare? Just FYI – this may be valid for your pretesting, though is not supported by Logo Program. All final Logo testing will be performed on Windows Server 2008 64-bit or Vista SP1 64-bit, physical or Hyper-V based OS.

    2.      Q/A for Application Verifier:

     

    Where are the logs stored?

    By default, the logs

    for services/apps running under user account are under: %USERPROFILE%\AppVerifierLogs

    for services/apps running under local service account are under: %windir%\serviceprofiles\LocalService\AppVerifierLogs

    for services/apps running under network service account are under: %windir%\serviceprofiles\NetworkService\AppVerifierLogs

    for services/apps running under system account are under: %windir%\system32\config\systemprofile\AppVerifierLogs

     

    Does Application Verifier verify managed code?

    AppVerifier cares about the interfaces between the operating system and the application. As a result, unless your managed code is performing interop against native APIs that have to do with Heaps, Handles, Critical Section, etc. your test cases are not going to give you any interaction with the interfaces that are verified.
    We recommend leveraging the Managed Debugging Assistants for verifying your managed code. Please read more about them on
    MSDN.

     

    Hope this helps,

     

    Friday, August 22, 2008 11:18 PM
  • Thanks for the reply.  We do have Hyper-V machines set up for the actual tests. I am now consulting Veritest for details of how they will execute the Appverifier test cases given the circumstances.

     

    Tuesday, August 26, 2008 7:30 AM