-
Notifications
You must be signed in to change notification settings - Fork 392
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
Custom VS extension development #6441
Comments
Hi, My team and I are relying on this great extension from @13thirteen to handle our various launch scenarios (Project1 + Project2, Project1 + Project 3, Project1 + Project2 + Project3,..). It adds a really useful overlay upon the launch profiles feature of VS2019. However, some caveats still persist, like the fact that the actual version of the nuget package Thank you. |
@13thirteen do you know the location of the feed? The myget link is broken. I also need the IActiveDebugFrameworkServices to read the current framework that is selected |
ok, I found the pre-release feed in a nuget.config |
The pre-release versions of the packages are in the vs-impl feed. |
Visual Studio Version:
VS Community 2019 16.6.5
Summary:
In my custom VS extension SwitchStartupProject (on the Marketplace) I use
ILaunchSettingsProvider
to programmatically change debug settings of multiple startup projects.So far I referenced nuget package
Microsoft.VisualStudio.ProjectSystem.Managed
2.0.6142705
on nuget.org.Recently, I found a slightly newer version
2.3.6152103
on your team feed which includesIActiveDebugFrameworkServices
that allows my extension to also set the target framework of multi-targeting projects.Now, I saw there is
IPersistOption
which might allow my extension to change debug settings without affecting thelaunchSettings.json
files. (I didn't study it in detail yet.) Unfortunately, I didn't find any non-beta and non-rc releases ofMicrosoft.VisualStudio.ProjectSystem.Managed
that includeIPersistOption
.The beta releases are not that useful because they have a dependency on package
RoslynTools.SignTool
which seems not to be public (for obvious reasons) and therefore installation fails.Questions:
Are there somewhere newer non-beta releases of the nuget packages for use by custom VS extensions?
As I understand it, these nuget packages are deployed with VS. (e.g. at
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\Extensions\Microsoft\ManagedProjectSystem\Microsoft.VisualStudio.ProjectSystem.Managed.dll
in my case.) Should my custom VS extension use that VS-bundled DLL somehow instead of the pretty old nuget package? How would I do that?Given the circumstances above, my current approach feels like a hack. Am I even supposed to use
Microsoft.VisualStudio.ProjectSystem.Managed
from a custom VS extension? Is there another/better way to programmatically set debug settings of CPS projects?The text was updated successfully, but these errors were encountered: