Resharper Integration ( dotCover ) with Typemock

So here is the config, for example, for DevPartner, [b]can someone please provide the config section for dotCover ? [/b] Specifically what is clsid and how to obtain it ? Thanks.

<Profiler Name="DevPartner.Coverage" Clsid="TM-COV{372DC2B6-0A34-4f22-BC34-BE7A18DE9137}" DirectLaunch="false">
<EnvironmentList>
<ProfilerEnvronment Name="NM_DISABLE_DA" TheValue="1" />
<ProfilerEnvronment Name="NM_DOING_COVERAGE" TheValue="1" />
<ProfilerEnvronment Name="NM_ANALYSIS" TheValue="cov" />
</EnvironmentList>
</Profiler>

Rybolt,

You are in the right place - this file controls the linked profiler configuration. clsid is the profiler's GUID, which can normally be obtained through the registry (each .net profiler registers with a unique ID). However, Jetbrains are using a new mechanism for profiler registration in the new .trace and .cover, which is not yet properly supported. We are still working with Jetbrains to provide proper linking support with their new products.

Thanks,
Doron
Typemock Support

Thanks for response. As you know, unit testing and code coverage go 'hand and hand', so if there is any way you can get me up and running with this integration that would be great :D

I would feel comfortable buying Typemock knowing these two tools work together.

Thanks for your support , and keep (us) posted on this thread with any updates :!:

Rybolt,

We are still working with Jetbrains to provide proper linking support with their new products.

Thanks,
Doron
Typemock Support

Jetbrains has announced dotCover RTM May-June. Well, it's May already, so it'll be here in no time, and we _still_ have no integration support with Typemock, is that correct? not even in there nightly build?

I can't purchase Typemock until I see these 2 work together. :!:

Unfortunately it's not supported yet, due to the changes in the profiler-registration mechanism in the new versions. We are in constant contact with Jetbrains to provide proper support for dotCover and dotTrace.
Please bear with us until we provide full support.

@igal

no worries, I should've realized it's Jetbrains and not you complicating the integration.

I don't understand Jetbrains' priority, they tweeted about supporting other 3rd parties already (and less significant than Typemock ).

Oh well, I've read the integration with PartCover (+1 free and opensource) is frictionless and adheres to the standard approach to integration with other profilers.

I am going to explore this option and appreciate the support of Typemock on this issue.

Ryan,

It's important to understand that no party is to be blamed here - there was a new product, which had a breaking change, and now we need to update our software to reflect that change. These things happen all the time...

Unfortunately I cannot give you an estimation at the moment. Like I said, we are making an effort together with JetBrains to reflect this change, and make sure that we can support all the new JetBrains products as soon as possible.

@igal

We all know you have to prioritize features to get into a product, for it's impossible to get them all in the first rev. agree?

To all MSpec lovers (including me!), latest nightly build of @dotCover should now work with MSpec!
2:49 AM Apr 9th via TweetDeck

To me, IMHO, MSpec is not a priority for most devs out there trying to unit test, I may be wrong, but I'd be shocked if MSpec (no offense) is used more than mock frameworks. Spec frameworks are awesome for TDD/BDD, but I am just saying _priorities seem to be in reverse here_.

Notice the bias towards MSpec :) Sorry MSpec you just got caught in the crossfire.

Just to let you know that PartCover has been upgraded to handle .NET 4.0 and has a number of issues fixed

Vote for TypeMock support in the Jetbrains issue tracker: http://youtrack.jetbrains.net/issue/DCVR-2292