Hi --
I have a vsx package that was generated by the wizard with C# code. It executes and debugs like a charm and when I set a breakpoint in the Package-derived class's Initialize method, this is hit when the package is loaded. Just to be clear, I debug the package from one instance of Visual Studio, which on starting the debugger, launches a second Experimental instance of Visual Studio and loads the package there. This is standard and it works completely as advertised.
Now at the tail end of this Initialize routine I call into a mixed (managed and unmanaged) DLL where I have the code that initializes my own language's runtime (the language I will be adding to Visual Studio via the package). It's here where things get a little funky. This mixed code DLL is implemented in the same solution as the vsx package (although the vsx package is set as the default startup project). I have added an assembly reference to this dll in the package's project and the managed object and method that I construct and call from the package's Initialize routine are seen both at design time and during debugging by Intellisense. And I can step into this method and single-step through it. And inside this method intellisense is still reporting type information correctly, but not letting me drill down into any of the objects contained inside this managed object. Moreover, I can't set any breakpoints. And when it comes to tracing into sub functions, sometimes it works and sometimes it doesn't. Sometimes when I choose to step into a function, it shoots me to the disassembly window, and if I can trace through the assembly code and eventually step into the c++ routine, if I manually move to that routine's source file, C++ stepping is active and I can switch back to stepping through the C++ code.
I'm wondering if there is some build setting I need to turn on in order to make full-fledged debugging follow into this dll from the package code. Does anyone have any ideas for me?
Thanks.
Mike