Subscribe

Intent to fork

  1. 2009-12-03 13:24:46 PST
    I've tried to contact the owners of this project to get commit access as I've fixed a few bugs and would like to devote some time to moving PartCover on. Unfortunately I haven't met with much success. I am planning, therefore, to create a fork of PartCover (which I've provisionally named "SharpCover"). I'm intending to host it at google code, and hopefully get an inital release by the end of the year. Any comments / requests for bug fixes / features for the first release are welcome.
  2. 2009-12-03 18:08:21 PST
    You can take a look at some of the things I did on github: http://github.com/geofflane/partcover-fork The main thing there is that I refactored the report generation so that it could output partcover's format or an ncover compatible format.
  3. 2010-05-01 07:59:58 PDT
    .NET 4.0 support would be great.
  4. 2010-06-03 12:59:44 PDT
    Are all of these kinda dead? I noticed geofflane added some functionality. Any one have plans on keeping these going?
  5. 2010-06-04 20:08:36 PDT
    I've considered being involved - but not sure what support there is available among the community - I've just grabbed the main trunk and looking to see how it works (and may be get an understanding of why it no longer does)
  6. 2010-06-06 01:19:54 PDT
    okay I have got partcover up and running on .NET4 (however there may be issues due to the new interface and the need to handle side-by-side support) The code is being hosted on github (see http://wiki.github.com/sawilde/partcover.net4/) Alternatively you can use the COMPLUS_ProfAPI_ProfilerCompatibilitySetting environment setting to allow a .NET2 profiler to work againsta .NET4 target. i.e. set COMPLUS_ProfAPI_ProfilerCompatibilitySetting=EnableV2Profiler
Jump To:
< Previous | 1 | Next >

Add a Reply

This forum does not allow anonymous participation.

Log in to add a reply. Not registered? Create an account to participate and receive email updates when replies are posted to this topic.