Code coverage analysis engine threw exception (s) : Image file could not be found

Locked Code coverage analysis engine threw exception (s) : Image file could not be found

  • terça-feira, 20 de julho de 2010 08:20
     
     

    Hi,

    I am trying to view the coverage results in visual studio. After importing the coverage result, when i expand the coverage result tree , the Error appears "Code coverage analysis threw exception (s) : Image file (say)"c:\temp\test.dll"could not be found". where as the test.dll is present at that same location.

    Can anyone help me in this issue ?

     

     

     

     

     

     

     

     

     

     

Todas as Respostas

  • quarta-feira, 21 de julho de 2010 11:31
    Moderador
     
     

    Hello Akshay,

    Thanks for your thread!

    Can you please tell me how did you do code coverage for your assembly? Through command line or Visual Studio IDE? If possible, please provide a detail step to reproduce the issue, thanks in advance!

    Best regards


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have any feedback, please tell us.
    Welcome to the All-In-One Code Framework!
  • sexta-feira, 13 de agosto de 2010 05:02
     
     
    Hi,

    I am trying to view the coverage results in visual studio. After importing the coverage result, when i expand the coverage result tree , the Error appears "Code coverage analysis threw exception (s) : Image file (say)"c:\temp\test.dll"could not be found". where as the test.dll is present at that same location.

    Can anyone help me in this issue ?

    It sounds like a similar problem that I am having (http://stackoverflow.com/questions/3464402/code-coverage-missing-when-building-net-4-apps-on-team-build-2008). I'm building a VS 2010 solution on a Team Build 2008 build agent, and while tests run fine with 100% pass rate, publication of code coverage fails. If I try to open the data.coverage file created by the build process, I get the same error that Akshay reports above.

    If I try to use the .testsettings file locally, then code coverage reports just fine - it's only when the build agent runs it that things go wrong.

    • Editado David Keaveny sexta-feira, 13 de agosto de 2010 07:12 Fixed a typo.
    •  
  • sexta-feira, 3 de setembro de 2010 20:15
     
     
    I have the same problem. Can anyone solve it?
  • quarta-feira, 8 de dezembro de 2010 09:33
     
     

    Hi Roahn

    I also faced same problem as Akshay. I am doing my code coverage via command line. The code coverage report gets generated fine for my exe, and I can view it in VS2010 IDE. The problem occurs if I make some changes to the exe project. Once the project is built again, the previous .coverage file doesn't get opened in VS 2010 IDE, and I receive same error as mentioned by Akshay -

    Code coverage analysis engine threw exception (s) : Image file "c:\MyExe.exe"could not be found

    There should be something simple which I am missing here. I cannot think that a code coverage report generated using one file becomes inaccessible/redundant if the corresponding file changes(In my case, the exe). This defeats my purpose of comparing 2 different .coverage files to determine how much additional code got covered after making a particular code change. Please suggest what can be done?

  • sexta-feira, 14 de janeiro de 2011 13:51
     
     

    I was able to get past this error by deselecting "Instrument Assemblies in place" 

    Bernhard Richter

     

  • quarta-feira, 11 de julho de 2012 09:11
     
     Resposta Proposta

    Go To Solution Items---->Local.TestSettings(Double click)--->select Data And Diagnostics ----> Code Coverage

    Double click on Code Coverage--->Select assembly ---->At bottom (Deselect Instrument assemblies in place)

    This will work ..

    • Sugerido como Resposta Shree Badugula quarta-feira, 11 de julho de 2012 09:11
    •  
  • sexta-feira, 7 de setembro de 2012 21:31
     
     

    This is if I am running a code coverage from Local.TestSettings.

    What is the solution, if the test binary has been instrumented through vsinstr.exe and the tests are run through mstest.exe.

    I am getting this error when i am running in the above scenario.

  • sexta-feira, 12 de outubro de 2012 05:12
     
     

    I have the same problem. 

    when I run the code coverage batch file script containing the code, which is 'C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Ldr64.exe setWoW' to make the 32 bit .net application run on top of x64 cmd prompt. everything worked fine.

    but  I changed the code into "C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Ldr64.exe setWoW"

    several problems took place in terms of bit-problems.

    I need to solve this issue. can anybody help me ?  


    • Editado Patrick_Kim sexta-feira, 12 de outubro de 2012 05:13
    •