none
Assembly "zlib.dll" is not a valid .NET assembly and will be skipped for analysis

    Question

  • Our application uses zlib.dll and we copy it to the application's bin directory using a post-build step. Because zlib.dll is a unmanged C dll, TFS Build throws an error when it tries to perform test impact analysis.

    Is there any way to fix this short of disabling all test?

     

    Thanks.

     

    From the build summary:

    Release | Any CPU
     0 error(s), 0 warning(s)
     1 projects/solutions compiled
     No Test Results
     No Code Coverage Results
    Other Errors and Warnings
     0 error(s), 1 warning(s)
     An error occurred when opening a file "C:\MyProject\Binaries\zlib.dll": Assembly "zlib.dll" is not a valid .NET assembly and will be skipped for analysis.


    From the build log:

    Get Impacted Tests, Index Sources and Publish Symbols

    00:11
    If PerformTestImpactAnalysis

    00:11
    Get Impacted Tests

    00:00
    Find Build Outputs

    00:11
    Get Impacted Tests
    Build "MyProject_20101115.4" on drop share "\\buildserver\Builds\MyProject\MyProject_20101115.4" will be used as a baseline for test impact analysis.
     An error occurred when opening a file "C:\MyProject\Binaries\zlib.dll": Assembly "zlib.dll" is not a valid .NET assembly and will be skipped for analysis.
    • Edited by __spatel Sunday, November 14, 2010 11:54 PM Typo
    Sunday, November 14, 2010 11:49 PM

All replies

  • Hi,

    Did you specify Test in your build definition? The step to Get Impacted Tests, Index Sources and Publish Symbols is after test, so the warning will not affect Test. and only the assembly will be skipped.

    Make sure you enable test in the build definition. You can also disable Index Sources in the build definition

     


    Best regards,
    Ruiz


    MSDN Subscriber Support in Forum
    If you have any feedback on our support, please contact msdnmg @ microsoft.com
    Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
    Monday, November 15, 2010 3:48 AM
  • Thanks for the reply Ruiz. We already have Tests enabled on the build. I tried disabling the 'Index Sources' setting but that didn't make any different - we still get warnings. The warning isn't causing the build or tests to fail but I'm trying to eliminate all errors and warnings from the build. Right now we get a bunch of warnings (one for every unmanaged DLL in the binaries/drop folder) under the 'Other Errors and Warnings' section when the build finishes.
    Monday, November 15, 2010 7:08 PM