Home/ Questions/Q 7946955
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-04T01:17:42+00:00

We just set up TFS 11 for the first time. Running a gated check

  • 0

We just set up TFS 11 for the first time. Running a gated check in, it succeeds but returns this message:

‘srctool.exe’ returned an unexpected exit code: ‘-1’. An error
occurred when opening a file “CustomDllName.dll”: Assembly
“CustomDllName.dll” is not a valid .NET assembly and will be skipped
for analysis.

Well, it’s right: that file is a legacy Visual Basic 6 DLL that we don’t have much control over. It’s included in the project for COM access to some of the methods.

Is there a way to instruct srctool.exe/TFS to skip that file when doing the inspection? Or another way to attack this?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Here is the solution that ultimately worked for me

    A member of the TFS 11 team at Microsoft mentioned to me that the problem is due to a change in behavior that the Windows 8 team made to the srctool.exe tool.

    By copying this file from the Windows 7 SDK (WinDBG) toolkit and overriding the one included in TFS 11 Beta, I was able to successfully run a build without any errors.

    • 0