Quantcast
Channel: YouTrackReSharper (RSRP) - Bug and Issue Tracker
Viewing all articles
Browse latest Browse all 106942

RSRP-273869: Can't step into unmanaged code when debugging a unit test

$
0
0
Reporter Mitch Barker (mitch.barker) Mitch Barker (mitch.barker)
Created Jul 12, 2011 1:41:29 AM
Updated Feb 6, 2012 7:02:25 PM
Priority Critical
Type Bug
Fix versions Mirabile Futurum
State Open
Assignee Victor Kropp (victor.kropp)
Subsystem No subsystem
Affected versions No Affected versions
Fixed in build No Fixed in build
VS2010 on W7.
R# 5.0
NUnit 2.5.8
.Net 4.0

We are writing unit tests in managed C++, and most of the these tests call un-managed C++. When debugging a unit test we need to step through the managed and un-managed code.

When I try to run a test using the R# test runner, R# pops up an error dialog that says it cannot load my test assembly because it is "...built by a runtime newer than the currently loaded runtime...". Apparently this is a known issue and is fixed in R# 6.0 ( http://89.163.94.184/issue/RSRP-236725 ).

So I downloaded a trial for R# 6.0. (We have about 15 devs licensed for R# so upgrading is not so easy to get approved.)

The tests run, but the debugger cannot step into, or hit any breakpoints in the un-managed code. We do a lot of managed/un-managed code interop, and it appears that R# was not built with the "enable unmanaged code debugging" property set to true.

Two side notes:
1) If I use the GUI test runner supplied with nunit I can debug the un-managed code.
2) If I rewrite the unit tests using the MS testing framework, and use the VS2010 test runner, I can debug manage code.

Is there a workaround to allow debugging of un-managed code?
Are there any workarounds to allow me to use R# 5.0?

Any help is appreciated.

Mitch

Viewing all articles
Browse latest Browse all 106942

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>