Can the debug option automatically attach to process

[gep13]

Since we are already in Visual Studio instance, can we skip this step:

[agc93]

I will still try and look into this, but there is at least one problem. Presently the task runner doesn't have any control over the actual execution phase: it just returns a list of tasks for Visual Studio to execute on our behalf. It looks like there might an avenue using the ITaskRunnerCommandService, but I haven't used it before.

Where would we stand on shipping without this?

[gep13]

I think that would be fine. I would see this as a longer term feature.

[matkoch]

Given the process id and this code, you should be able to attach programmatically.

[agc93]

Thanks @matkoch ! While that will work (and will be the avenue we use going forward), the major issue with the original design is that there's no way for the extension to call that code from the Task Runner at all. Once we provide the ITaskRunnerNode for our file, VS handles everything after that. We're looking into how better to approach this now.

[matkoch]

@agc93 I guess either cake.exe should signal that somehow using IPC, or you could have another thread, that watches for processes of cake.exe. You could even find out, if it's a child process of the current VisualStudio.

[agc93]

@matkoch While possible, going OOP from Visual Studio requires quite significant changes to how the extension is built, packaged and shipped so I'd prefer to avoid it if we can.