Integrating a custom launcher into the Visual Studio Debugger -


we're creating visual studio debugger extension needs launch application being debugged through custom launcher sets runtime (not clr or win32) , launch target application in new process. in other words, custom launcher in charge of creating new process. in vs debugger, 1 typically launches debugger calling vsshellutilities.launchdebugger() , supplying vsdebugtargetinfo object dlo field set debug_launch_operation.dlo_createprocess, along coordinates of exe file launched , debugged. doesn't conform our launching model.

there dlo value debug_launch_operation.dlo_custom seems purpose (using clsidcustom field indicate launcher), current documentation says that's obsolete , directs debug_launch_operation.dlo_createprocess, not doesn't fit our model, clsidcustom used in case indicate debug engine (if it's single one).

so, recommended way launch vs debugger , use our custom launcher configure , start our runtime (and application within it)?

according visual studio api document, provide dlo_createprocess launches process. use dwclsidcount , pclsidlist specify debug engines use.

following example introduce how call custom launcher through vsix project.

https://code.msdn.microsoft.com/visual-studio-debug-engine-c2e21c0e


Comments

Popular posts from this blog

ios - MKAnnotationView layer is not of expected type: MKLayer -

ZeroMQ on Windows, with Qt Creator -

unity3d - Unity SceneManager.LoadScene quits application -