{"action":"opened","issue":{"url":"https://api.github.com/repos/josetr/VsixTesting/issues/14","repository_url":"https://api.github.com/repos/josetr/VsixTesting","labels_url":"https://api.github.com/repos/josetr/VsixTesting/issues/14/labels{/name}","comments_url":"https://api.github.com/repos/josetr/VsixTesting/issues/14/comments","events_url":"https://api.github.com/repos/josetr/VsixTesting/issues/14/events","html_url":"https://github.com/josetr/VsixTesting/issues/14","id":369594714,"node_id":"MDU6SXNzdWUzNjk1OTQ3MTQ=","number":14,"title":"Add option to launch Visual Studio from VsixTesting.ExtensionInstaller","user":{"login":"jcansdale","id":11719160,"node_id":"MDQ6VXNlcjExNzE5MTYw","avatar_url":"https://avatars3.githubusercontent.com/u/11719160?v=4","gravatar_id":"","url":"https://api.github.com/users/jcansdale","html_url":"https://github.com/jcansdale","followers_url":"https://api.github.com/users/jcansdale/followers","following_url":"https://api.github.com/users/jcansdale/following{/other_user}","gists_url":"https://api.github.com/users/jcansdale/gists{/gist_id}","starred_url":"https://api.github.com/users/jcansdale/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jcansdale/subscriptions","organizations_url":"https://api.github.com/users/jcansdale/orgs","repos_url":"https://api.github.com/users/jcansdale/repos","events_url":"https://api.github.com/users/jcansdale/events{/privacy}","received_events_url":"https://api.github.com/users/jcansdale/received_events","type":"User","site_admin":true},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-10-12T15:13:23Z","updated_at":"2018-10-12T15:13:23Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"We've recently been struggling to keep the GitHub for Visual Studio extension working on both Visual Studio 2017 and 2015. The team now primarily uses 2017 and the extension is built with 2017. Installing, running and debugging on 2015 has become a pain.\r\n\r\nI was wondering how feasible it would be to use various components on `VsixTesting` to create a painless F5 experience for installing and running extensions in 2015.\r\n\r\n1. Add an option to launch Visual Studio from `VsixTesting.ExtensionInstaller` after installing\r\n2. Use the debug propagation trick, so that if `VsixTesting.ExtensionInstaller` is started with the debugger attached, it would automatically attach the debugger from the parent `devenv` process to the child process\r\n\r\nWe could then create a `launchSettings.json` entry for the Visual Studio versions we want to target. It might be something like this:\r\n```json\r\n    \"Start VS 2015\": {\r\n      \"commandName\": \"Project\",\r\n      \"commandLineArgs\": \"/ApplicationPath \\\"C:\\\\Program Files (x86)\\\\Microsoft Visual Studio 14.0\\\\Common7\\\\IDE\\\\devenv.exe\\\" /RootSuffix Exp\r\n            /InstallAndStart \\\"$(SolutionDir)build\\\\$(Configuration)\\\\GitHub.VisualStudio.vsix\\\"\"\r\n    },\r\n```\r\n\r\nDo you think that would work?\r\n"}}
{"actor":{"display_login":"jcansdale"}}