Skip to content

Remove the Areas of Interest selection and the PostSharp Learning Hub #66

Description

@gfraiteur

User story

As a PostSharp user, during license registration I am asked to select my "areas of interest", and the Visual Studio extension shows a "PostSharp Learning Hub" tool window that recommends learning content based on those selections. This feature is being retired. I want the areas-of-interest selection and the Learning Hub removed entirely, so registration is shorter and the extension no longer shows or auto-opens the Learning Hub.

Current behavior

  • The license registration wizard includes an Areas of Interest page where the user selects topics. The selections are stored in the registry (HKCU\Software\SharpCrafters\PostSharp 3, value AreasOfInterest) and appended to the welcome-page URL as an interests parameter.
  • The Visual Studio extension provides a PostSharp Learning Hub tool window (PostSharp menu -> PostSharp Learning Hub) that downloads content from postsharp.net and ranks it according to the selected areas of interest. It can auto-open when a solution is opened, and offers a "Customize" dialog to edit the areas of interest and an open-on-startup option.

Desired behavior

  • No "Areas of Interest" page in the license registration wizard.
  • No "PostSharp Learning Hub" tool window, menu command, or auto-open behavior in the Visual Studio extension.
  • No collection or storage of areas of interest, and no interests parameter sent to the welcome page.

Acceptance criteria

  • The Areas of Interest wizard page and control, and the AreasOfInterestSet/FeatureSet types, are removed.
  • The Learning Hub tool window, its menu command, view models, content downloader, options, and service are removed.
  • The "Customize areas of interest" dialog is removed.
  • The welcome-page URL no longer includes the interests parameter.
  • The registry values AreasOfInterest and AutoDisplayLearnToolWindow are no longer read or written; obsolete settings are ignored on upgrade.
  • No orphaned references remain (menu/command IDs, tool window registration, project includes).
  • The removal is documented in the Release Notes.

Implementation scope (for the dev team)

Touches roughly 35 files across PostSharp.VisualStudio (Learning Hub: tool window, control, view models, content downloader, options/service, AreasOfInterestDialog, the cmdLearnPostSharp command in VsPackageUI.vsct, and registrations in PostSharpPackage.cs), PostSharp.Settings.UI (Areas of Interest page/control, FeatureSet, the RegisterLicenseProcess wizard flow, and OpenWelcomeWebPageTask), and a small change in PostSharp.Compiler.Settings (UserSettings.AutoDisplayLearnToolWindowUser).

Notes

  • The same feature exists in the Metalama Visual Studio Tools and is tracked separately in metalama/Metalama.Vsx.Public (companion issue cross-linked below).

  • Claude for Gael

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions