Hi --
I have a package that on initialization (i.e from within the Package.Initialize routine) generates a bunch of code by writing assembler bits to memory. As part of the sequence of generating this code, I manipulate a DTE pointer to the Host Visual Studio Enviornment (i.e. the one from which I have launched the package debugging session) and set several breakpoints on the code I've just generated. The breakpoints appear in the Breakpoints window and look active -- they have a solid red circle instead of a hollow one. But when I execute the code, these breakpoints are never hit.
In fact, if I try to step into the generated code from from some inline assembly inside the unmanaged C++ function where the inline assembl is located, I can't do it. I try this from the Dissambly window, where I can successfully step through the inline assembly code that has been compiled into the project. But when I attempt to step through my generated assembly code, it won't do it.
This is something that worked perfectly when my language runtime bootstrapper was the project being debugged in a single instance of Visual Studio. But now that I have introduced the package into the mix (and the second experimental hive instance of Visual Studio where the code is actually running), it no longer works. It's frustrating, because the breakpoints look normal and look like they should be activated (and it took a lot of effort to reach the point where that was the case). And I feel that if I can figure out how to enable the single stepping, then my breakpoints should work.
Does anybody have any thoughts as to what I might do to get this working in the current environment?
Thanks for any help anyone can offer.