Suggestion for an additional section to Debug Custom Controls walkthrough for newer .NET project types

[gbakeman]

Type of issue

Other (describe below)

Description

Greetings,

I really appreciate having this walkthrough for debugging custom controls using the In-Process designer for Visual Studio.

At some point, I migrated my custom control project to the newer .NET Projects system, while maintaining .NET Framework as my target framework. I've found an easy solution for launching Visual Studio within the debugger, using this launchSettings configuration:

{
  "profiles": {
    "Debug devenv": {
      "commandName": "Executable",
      "executablePath": "$(DevEnvDir)devenv.exe",
      "commandLineArgs": "$(SolutionPath)"
    }
  }
}

I wonder if it would be worth adding this to the walkthrough, to help people who are using the new Projects format?

Page URL

https://learn.microsoft.com/en-us/dotnet/desktop/winforms/controls/walkthrough-debugging-custom-windows-forms-controls-at-design-time?view=netframeworkdesktop-4.8

Content source URL

https://github.com/dotnet/docs-desktop/blob/main/dotnet-desktop-guide/framework/winforms/controls/walkthrough-debugging-custom-windows-forms-controls-at-design-time.md

Document Version Independent Id

f493ff27-e2e1-ad7e-38d4-46ded0c45022

Article author

@adegeo

[adegeo]

Thanks for this suggestion. Working in the SDK Project-system for .NET Framework isn't something we've considered documenting, though I, like you, do it. I think what the best thing to do would be to add a new article that describes the differences and config options you should take to make your project compatible, especially with debugging. However, this won't be a priority right now, unless more people come in and request it 😁

[gbakeman]

Perfectly, thank you @adegeo!

[adegeo]

I was looking back through this issue. The priority hasn't changed, as in really, no priority, no offence @gbakeman 😁 but one thing to note about this scenario (when it's written about) is that VB can't use SDK-style projects and target .NET Framework, only C# can.

[gbakeman]

@adegeo None taken at all, and good note about language support. I've been working with quite a lot of obsolete tech lately, and I totally understand how this isn't a priority. Thanks for checking in all the same.