partcover

PartCover producing empty xml when upgrading applications to .Net 4.0

由 纵然是瞬间 提交于 2019-12-24 01:26:17
问题 We have been running PartCover on applications, and they were producing xml reports just fine. However, we upgraded all our applications from .Net 3.5 to .Net 4.0, and now, PartCover just produces an empty XML file. I tried upgrading to latest NUnit and latest PartCover, but that did not help. Is there anything else I can do to try to resolve this issue? We've been using code coverage frequently as part of our process, and need to resolve. This is the command: "C:\Program Files (x86)

PartCover 4.0 Only Reports NUnit Libraries

由 我是研究僧i 提交于 2019-12-22 07:59:13
问题 I'm using PartCover 4.0 (from the sourceforge page, latest dev build) with NUnit 2.5.8 on Windows 7 (x64). PartCover runs ok (using the -x86.exe), but it only shows me coverage for various NUnit packages -- not my own source-code. I originally didn't use CorFlags.exe since I didn't get the COM error; I tried it anyways, and it didn't make any difference. I've looked at all the other questions on Stack Overflow, and none seem to apply; I'm using PartCover 4.0, there are no spaces in any of my

Why PartCover report shows 0% when mstest runs successfully and all tests pass

由 倾然丶 夕夏残阳落幕 提交于 2019-12-12 10:54:17
问题 I'm trying to get code coverage with mstest tests. I'm using PartCover 2.2.0.36424. The problem is with real assemblies, I get 0% code coverage (Note: All tests pass). On demo test for demo source that I created, it worked fine (the report makes sense). I noticed that in log file: for demo files, after line "Assembly AAAAAA loaded (MyTestesAssemblyName)", there is line "Class NNNNNN loaded (MyTestesAssemblyName.MyClassname)"; and for the real files ther is no second line (for class) after the

CorfFlags warning CF011 about strong name signed even after /force

由 試著忘記壹切 提交于 2019-12-11 02:27:46
问题 Im trying to use Corflags to get PartCover running under x64. When I use: CorFlags.exe PartCover.exe /32BIT+ /Force i get: corflags : warning CF011 : The specified file is strong name signed. Using /Force will invalidate the signature of this image and will require the assembly tobe resigned. without /force i get: corflags : error CF012 : The specified file is strong name signed. Use /Force to force the update. On web there appears that others are runnig partcover throught corflags with no

Using PartCover 2.3 with .NET 4.0 runtime?

由 心已入冬 提交于 2019-12-07 00:53:54
问题 I've successfully got PartCover 2.3 working with VS 2008 on my 64-bit machine. I'm now trying to get it to work with VS 2010 and NUnit 2.5.3. I've got NUnit using the correct CLR version, but I can't get PartCover to produce any output. All I get is an "empty" report XML file: <PartCoverReport date="2010-03-30T16:09:05.1009099+01:00" /> How do I get PartCover 2.3 (or 2.2, I guess) to work with NUnit 2.5.3 on .NET 4.0? 回答1: I have recently completed a portcover fork that will hook into the

PartCover 4.0 Only Reports NUnit Libraries

由 ☆樱花仙子☆ 提交于 2019-12-05 16:36:46
I'm using PartCover 4.0 (from the sourceforge page , latest dev build) with NUnit 2.5.8 on Windows 7 (x64). PartCover runs ok (using the -x86.exe), but it only shows me coverage for various NUnit packages -- not my own source-code. I originally didn't use CorFlags.exe since I didn't get the COM error; I tried it anyways, and it didn't make any difference. I've looked at all the other questions on Stack Overflow, and none seem to apply; I'm using PartCover 4.0, there are no spaces in any of my names, my coverage rule is the most broad ( +[*]* ), and I've run CorFlags.exe. What am I missing? I

Using PartCover 2.3 with .NET 4.0 runtime?

由 不羁岁月 提交于 2019-12-05 05:44:58
I've successfully got PartCover 2.3 working with VS 2008 on my 64-bit machine . I'm now trying to get it to work with VS 2010 and NUnit 2.5.3. I've got NUnit using the correct CLR version , but I can't get PartCover to produce any output. All I get is an "empty" report XML file: <PartCoverReport date="2010-03-30T16:09:05.1009099+01:00" /> How do I get PartCover 2.3 (or 2.2, I guess) to work with NUnit 2.5.3 on .NET 4.0? I have recently completed a portcover fork that will hook into the .NET4 CLR - maybe you could give that a try http://github.com/sawilde/partcover.net4 If you're not able to

How do I include full PartCover results with TeamCity 5?

由 时间秒杀一切 提交于 2019-12-03 07:38:15
问题 I'm trying to get PartCover reports to generate correctly in TeamCity 5.0. When I click the Code Coverage tab in the build details, the reports are empty. I'm using the sln2008 build agent and my PartCoverage settings are as follows: Include Patterns: [*]* Report XSLT: C:\Program Files\PartCover .NET 2.3\xslt\Report By Assembly.xslt=>ByAssembly.html C:\Program Files\PartCover .NET 2.3\xslt\Report By Class.xslt=>ByClass.html Bonus points if you can describe how to include those reports (or

How do I include full PartCover results with TeamCity 5?

由 淺唱寂寞╮ 提交于 2019-12-02 21:05:33
I'm trying to get PartCover reports to generate correctly in TeamCity 5.0. When I click the Code Coverage tab in the build details, the reports are empty. I'm using the sln2008 build agent and my PartCoverage settings are as follows: Include Patterns: [*]* Report XSLT: C:\Program Files\PartCover .NET 2.3\xslt\Report By Assembly.xslt=>ByAssembly.html C:\Program Files\PartCover .NET 2.3\xslt\Report By Class.xslt=>ByClass.html Bonus points if you can describe how to include those reports (or just the important parts) with the email that TeamCity sends for successful/failed builds. I would like to

How do I run PartCover in x64 windows

由 泄露秘密 提交于 2019-12-01 03:06:48
I am trying to run PartCover to test the coverage of some tests with Gallio on windows x64. However trying to run it gives the following error. Retrieving the COM class factory for component with CLSID {FB20430E-CDC9-45D7-8453-272268002E08} failed due to the following error: 80040153. Edit: I am using PartCover 2.2.0 The problem is caused by PartCover trying to load a 32 bit dll when it is running under the 64-bit .NET VM. The trick is to force PartCover to run in the 32 bit VM. In order to do this you have to use a tool called CorFlags.exe to modify the exe and flag it as 32 bit. This is
订阅 partcover