Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>5 hours later and this is a tumbleweed. I found some <a href="http://blogs.msdn.com/b/phuene/archive/2009/12/01/programmatic-coverage-analysis-in-visual-studio-2010.aspx" rel="noreferrer">additional detail here</a>, which helped get me further down the path.</p> <p>In order for this to work, you need to include a few additional files alongside the custom task and supply folder locations for the pdb's and instrumented dll's.</p> <p>Regarding additional files, you need the following:</p> <ol> <li>The custom build task must reference Microsoft.VisualStudio.Coverage.Analysis.dll</li> <li><p>Your bin folder must contain the following additional files:</p> <ul> <li>Microsoft.VisualStudio.Coverage.Symbols.dll</li> <li>dbghelp.dll</li> </ul></li> <li><p>(If you don't have visual studio installed, you must perform regsvr32.exe on msdia100.dll)</p></li> </ol> <p>Regarding paths to assemblies and symbols, the <em>CreateFromFile</em> method takes a collection of folders to search. What seems really strange is that error complains about not being able to locate missing instrumented assemblies, and it specifies the full path..</p> <blockquote> <p>Image file c:\project\output\Assembly.dll could not be found.</p> </blockquote> <p>...but if you specify that path, it doesn't work.</p> <pre><code> CoverageInfo current = CoverageInfo.CreateFromFile( "c:\project\testresults\x\In\data.coverage", new string[] { "c:\project\output" }, new string[] { "c:\project\output" }); </code></pre> <p>However, changing the path to be the folder of the TestResults output works fine:</p> <pre><code> CoverageInfo current = CoverageInfo.CreateFromFile( "c:\project\testresults\x\In\data.coverage", new string[] { "c:\project\testresults\x\Out" }, new string[] { "c:\project\testresults\x\Out" }); </code></pre> <p>I question whether "instrument in place" really means <em>in that folder</em>, or instrument and copy to the MS Test run folder.</p> <p>Well dear SO folk, if you're reading this, you get a cookie.</p>
    singulars
    1. This table or related slice is empty.
    1. POMerging Visual Studio Code Coverage fails with ImageNotFoundException
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USbryanbcook
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POMerging Visual Studio Code Coverage fails with ImageNotFoundException
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO+1 and Thanks... saved me a few hours, even if no-one else got the answer first!
      singulars
      1. PO
      1. USJulia Hayward
    2. CO+1 One more point, the place where you have to add the references (or copy the dlls such as Microsoft.VisualStudio.Coverage.Analysis.dll,Microsoft.VisualStudio.Coverage.Symbols.dll, dbghelp.dll ) is not in your main project file but the one that uses CoverageInfo class. I spent sometime to figure out where to add the references. Also there should not be any trailing '\' in the Out folder. e.g. c:\project\testresults\x\Out\ will cause an error.
      singulars
      1. PO
      1. USSriwantha Attanayake
    3. COI've MS2013Pro edition and I don't have that Symbols.dll file in PrivateAssemblies folder. Help please!!
      singulars
      1. PO
      1. USadeel41
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload