Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to add some sort of launch profile or automatize the debug Current Instance to auto load a project/solution #371

Open
luislhg opened this issue May 9, 2024 · 3 comments
Assignees
Milestone

Comments

@luislhg
Copy link

luislhg commented May 9, 2024

Hello, I've been trying the new VSExtensibility and it's waaaay better than the previous sdk/api!

I'm struggling on how to automatically load a project/solution whenever I start debuging my "Current Instance". Since everytime singletime I start debugging I must dig into some test projects...
Tried to use Debug Launch passing as argument some test solution, but no luck.

Any tips are appreciated, thanks

@tinaschrepfer
Copy link
Member

@luislhg - Apologies for the delayed response on this. I'd like to make sure I understand what you're asking. Reading your question, our assumption is that you have developed a VisualStudio.Extensibility extension and when you F5 debug that extension, you see the Experimental instance of VS launch with your extension loaded, and in that Experimental instance of VS, you'd like your test project to be loaded. Is that what you're looking for?

@luislhg
Copy link
Author

luislhg commented Jul 27, 2024

@tinaschrepfer
Thanks for the response.
Yes, that is correct.

I'd expect to have some way to specify a path to a solution, project or file, in which whenever I F5 debug my VisualStudio.Extensibility extension it automatically open the VS Experimental instance with that solution/project/file already being opened by the VS Experimental instance.

I believe this is a very common situation, when you are developing an extension for something you are probably going to be testing against some projects/files that you always have to keep opening everytime you start debugging the extension.

Something in a launchSettings.json would make sense to me, but anything that could help is appreciated.

@tinaschrepfer tinaschrepfer modified the milestones: Triage, Backlog Aug 9, 2024
@tinaschrepfer
Copy link
Member

@luislhg - Thanks for the clarification! This is a gap in our F5 debug experience and I've added this request to our backlog for future consideration. We will update this thread when we have more information to share.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants