When writing Visual Studio extensions for Windows, that use the Mono stack, currently customers have to install the MAUI workload (a few GB download) for the extensions to work, due to the Mono.Debugging.VisualStudio dependency. Who do we need to speak to about getting Mono.Debugging.VisualStudio included in this lib, or alternatively nugetized so we can use it directly in our extensions, without the MAUI dependency?
Currently our DebuggerLaunchProvider class makes use of the IDebugLauncher, DebuggingOptions, DebuggerSession, StartInfo and SessionMarshalling interface/classes. As well as the Guids.PortSupplierGuid and Guids.EngineGuid in our DebugLaunchSettings class.
When writing Visual Studio extensions for Windows, that use the Mono stack, currently customers have to install the MAUI workload (a few GB download) for the extensions to work, due to the
Mono.Debugging.VisualStudiodependency. Who do we need to speak to about gettingMono.Debugging.VisualStudioincluded in this lib, or alternatively nugetized so we can use it directly in our extensions, without the MAUI dependency?Currently our
DebuggerLaunchProviderclass makes use of theIDebugLauncher,DebuggingOptions,DebuggerSession,StartInfoandSessionMarshallinginterface/classes. As well as theGuids.PortSupplierGuidandGuids.EngineGuidin ourDebugLaunchSettingsclass.