MSTest with codecoverage - attempts to instruments DLLs it can't

MSTest with codecoverage - attempts to instruments DLLs it can't

I have 
"Error VSP1039 : VSInstr does not support instrumenting binaries built with 
prevous version of the compiler." 

When trying to use MSTEST on a set of tests. 

It is trying to instrument a 3rd party DLL, which is indeed compiled in VS6.0.

I don't want it to instrument that DLL, only "my" code, but I do not see any 
way of ignoring the error, or getting it to not attempt to instrument it. 

I presume it is aggressively following all dependancies it detects my code 
uses (dll import / pinvoke on that DLL) 

/IGNOREWARN:1039 appears to not be allowed (presumably because it is an 
error not a warning) 

If I edit the test configuration, it only allows me a granularity of "per 
project" on and off, and it is a large project that happens to include at one 
point the use of that 3rd party dll.

(repost, because email reply settings have changed)

date: Tue, 29 Jul 2008 02:24:01 -0700 author: Tristan MSDN Keen am

RE: MSTest with codecoverage - attempts to instruments DLLs it can't

Hi Tristan,

From your description, you have some .NET managed assemblies which use 
MSTest to perform tests(profiling , code coverage...), however, since some 
of the assembly use some unmanaged DLL, you encountered the following error 
when performing the test, correct?

"Error VSP1039 : VSInstr does not support instrumenting binaries built with 
prevous version of the compiler." 

Are you using Visual studio 2005 or 2008 series? Since you've mentioned 
there does have unmanaged assembly(built with vs 6.0) in the project, I 
think it is likely to be the cause. Currently, my suggestion is that you 
first try simplify the solution for test(or just generate a simplified copy 
of the original solution for our troubleshooting), make sure it can result 
to the same error and include minimized number of components.

Generally for the Instrumentation and Code coverage, it is a feature 
provided by visual studio team system (tester edition). In Visual studio 
IDE, we can run this kind of test via a test project. And based on my 
research, for Code coverage, it require those assemblies(you want to 
perform code coverage test) to be instrumented first. And you can configure 
which assemblies you want to perform code coverage via "Test 
Configuration". In visual studio, you can access the setting via the 
following menu (in test project):

"Test ---> Edit Test Run Configuration---> Local Test 
Run(localtestrun.testrunconfig)"

in the popup dialog, there is "code coverage" section let you to control 
the assemblies to perform instrument and code coverage. You can choose to 
save a copy of the configuration file.

#How to: Specify a Test Run Configuration
http://msdn.microsoft.com/en-us/library/ms182480.aspx

#Editing a Test Run Configuration XML File
http://msdn.microsoft.com/en-us/library/ms404663.aspx

For tests performed by "MSTest" command utility, I find that it support the 
"/runconfig:[ file name ] "  command option which is used to specify a test 
run configuration.  The run configuration file is just the same format of 
the "Local test Run" setting I mentioned above(for IDE GUI based test):

#MSTest.exe Command-Line Options
http://msdn.microsoft.com/en-us/library/ms182489(VS.80).aspx

You can have a look to see whether it helps.

Sincerely,

Steven Cheng

Microsoft MSDN Online Support Lead


Delighting our customers is our #1 priority. We welcome your comments and 
suggestions about how we can improve the support we provide to you. Please 
feel free to let my manager know what you think of the level of service 
provided. You can send feedback directly to my manager at: 
msdnmg@microsoft.com.

==================================================
Get notification to my posts through email? Please refer to 
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues 
where an initial response from the community or a Microsoft Support 
Engineer within 1 business day is acceptable. Please note that each follow 
up response may take approximately 2 business days as the support 
professional working with you may need further investigation to reach the 
most efficient resolution. The offering is not appropriate for situations 
that require urgent, real-time or phone-based interactions or complex 
project analysis and dump analysis issues. Issues of this nature are best 
handled working with a dedicated Microsoft Support Engineer by contacting 
Microsoft Customer Support Services (CSS) at 
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
>From: =?Utf-8?B?VHJpc3RhbiBNU0ROIEtlZW4=?= <QASDev@nospam.nospam>
>Subject: MSTest with codecoverage - attempts to instruments DLLs it can't
>Date: Tue, 29 Jul 2008 02:24:01 -0700

>
>I have 
>"Error VSP1039 : VSInstr does not support instrumenting binaries built 
with 
>prevous version of the compiler." 
>
>When trying to use MSTEST on a set of tests. 
>
>It is trying to instrument a 3rd party DLL, which is indeed compiled in 
VS6.0.
>
>I don't want it to instrument that DLL, only "my" code, but I do not see 
any 
>way of ignoring the error, or getting it to not attempt to instrument it. 
>
>I presume it is aggressively following all dependancies it detects my code 
>uses (dll import / pinvoke on that DLL) 
>
>/IGNOREWARN:1039 appears to not be allowed (presumably because it is an 
>error not a warning) 
>
>If I edit the test configuration, it only allows me a granularity of "per 
>project" on and off, and it is a large project that happens to include at 
one 
>point the use of that 3rd party dll.
>
>(repost, because email reply settings have changed)
>

date: Wed, 30 Jul 2008 03:36:11 GMT author: (Steven Cheng [MSFT])