Step into c++/CLI wrapper dll and c# dll during debug while making plugins on firebreath

0
votes

Building a firebreathplugin where there's a native dll, c# class library dll and a c++/CLI (class library) wrapper dll. No application here. Saw other posts on stack overflow. Did the Debugging Mixed mode .but in vain? UPDATE

1.  in c# dll properties I have "Enable unmanaged code debugging" unchecked 
2. in c++/CLI wrapper dll properties, I have set Debug mode as mixed and set Attach to Yes
3. in native c++ plugin dll (firebreath generated) I set Properties->Debugging>Debug Mode->Mixed and Attach as "Yes"

COMPILER for c++/cli wrapper dll is /clr and for the native c++ is set "no /clr support" USING LOCAL WINDOWS DEBUGGER for this To debug the plugin i just followed the step described in firebreath homepage(i.e.click Debug menu and then Attach to process..i selected the iexplore.exe) Hope I would get an answer soon?

1
c#debuggingdllc++-clifirebreath
Are all dlls/exes compiled with the same VS version, in the same configuration and platform? - stijn
Yes @stijn Sir! vs 2010 - Pratik Pattanayak
"Debugging Mixed mode". Describe what you did in detail. Look at the "Modules" window--do you see both native and managed dlls in the list? - Matt Smith
@Matt Smith Yes i see both modules in the properties of the native c++ plugin dll - Pratik Pattanayak
@PratikPattanayak, not sure what you mean by "in the properties of the native c++ plugin dll". Once you're attached, go to Debug->Windows->Modules, and see if all the expected dlls show up there. - Matt Smith

1 Answers

0
votes

None of those settings matter unless one of those projects is the Start-up project (i.e. the one in bold in the solution explorer). The settings of the start-up project is what matters.

Or, if you'd rather not change the start-up project, then you can do an "Attach to Process" and specify what types (Managed, Native, etc).