Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Suggestion: Allow LibMan support in Visual Studio to be activated by a project capability

Open
#605 2 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp
Domain
tooling

Research direction

Start by reviewing how LibMan detects project support and how the LibMan wizard is exposed for projects containing libman.json. Then inspect the project file and project-capability integration points in the Visual Studio extension. Done means a project can opt in through a capability and use the wizard and context-menu actions outside the currently supported project types.

Written by the indexing model from the issue text.

Description

Functional impact

This would allow any project to opt-in to libman support (context menu items, add library wizard).

Minimal repro steps
  1. Create a Razor Class Library project
  2. Try to add a library via LibMan wizard (e.g. for image assets)
Expected result

Some way to allow enabling the LibMan wizard.

Actual result

Editing libman.json works, but there's no way to get the wizard to work.

Further technical details

Enabling LibMan via a project capability means that anyone could edit their project file, even if not a web project, to opt-in to LibMan support.

Since the editor support works as long as there's a libman.json file, this issue is mostly to see if there's interest in enabling wizard support in other project types.

Dominant language
C#
Stars
486
Forks
91
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aspnet/LibraryManager

All issues in aspnet/LibraryManager

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.