Intent to fork

2009-12-03
2013-04-29
  • Gareth Erskine-Jones

    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.

     
  • geofflane

    geofflane - 2009-12-04

    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.

     
  • GiddyUpHorsey

    GiddyUpHorsey - 2010-05-01

    .NET 4.0 support would be great.

     
  • nportelli

    nportelli - 2010-06-03

    Are all of these kinda dead?  I noticed geofflane added some functionality.  Any one have plans on keeping these going?

     
  • Shaun Wilde

    Shaun Wilde - 2010-06-05

    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)

     
  • Shaun Wilde

    Shaun Wilde - 2010-06-06

    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

     

Log in to post a comment.