百科.dev
全部条目在线工具AI 编程趋势榜开源项目技术资讯提交条目
登录
< 返回工具列表
V

vscode-solution-explorer

> 编程语言
开源

这是一个 Visual Studio Code 扩展,提供了一个 (.sln 和 .slnx) Visual Studio 解决方案浏览器面板。

395 stars0 点赞2 次浏览
访问官网GitHub

工具介绍

这是一个 Visual Studio Code 扩展,提供了一个 (.sln 和 .slnx) Visual Studio 解决方案浏览器面板。

⚠️ Please note, while there is another extension offering a solution explorer for Visual Studio Code, it's important to clarify that this is not the official Microsoft extension. For the official extension, you can visit this link.

vscode-solution-explorer

This extension adds a Visual Studio Solution File explorer panel in Visual Studio Code. Now you can navigate into your solution following the original Visual Studio structure.

It was originally intended to work with .Net Core solutions and projects. For this reason, the compatibility with other types of projects (such as .Net Framework or C++) is not guaranteed.

If you want to enjoy the full experience, you should install:

  • .Net SDK (dotnet command line is required)
  • Microsoft C# extension (aka Omnisharp)

Table of Content:

  • vscode-solution-explorer
    • Getting Started
    • Open Solutions
      • Open Solution command
      • Omnisharp integration
      • Find Solution files
    • Features
      • Run dotnet commands in solutions and projects
      • Drag and drop files, folders and projects
      • Create, delete, rename or project folders and files
      • Create, delete, rename or move solution, solution folders and projects
      • Add new project (panel)
      • Add or remove nuget packages
      • Update all nuget packages versions
      • Inline nuget package version management (csproj)
      • Add or remove project references
      • Create file templates
      • Solution syntax highlighting
      • Create Directory.Packages.props
      • MSBuild property and condition evaluation
      • Edit MSBuild Properties
      • Multilanguage support
    • Extension Settings - Example
    • Known Issues
    • License
    • Thanks to contributors

If you like my work you can buy me a beer and show that love

Getting Started

To activate vscode-solution-explorer you have to first open a folder or workspace.

Then, you can find this extension displayed as:

  • a tab in the "Explorer" activity

  • an activity with the Visual Studio icon

You can configure it in the Visual Studio Code settings panel, looking for "VsSolution: Show Mode" section:

Open Solutions

vscode-solution-explorer has several ways to open the solution files and you can configure them in the Visual Studio Code configuration panel.

Open Solution command

You can execute the "Open solution" command from the command palette or from the welcome view (if no solution has been found).

Omnisharp integration

You can enable omnisharp integration and vscode-solution-explorer will open the same .sln or .slnx file you open with Microsoft`s extension.

It will ignore .csproj files because vscode-solution-explorer cannot open a project file without a Solution.

You have to install Microsoft C# extension to enable omnisharp integration.

Find Solution files

You can use the automatic solution file finder activating some options in the Visual Studio Code settings panel.

The vssolution.openSolutions.inRootFolder setting will look for the solution files in the root folder.

The vssolution.openSolutions.inFoldersAndSubfolders setting will search for the solution files in the root folder and its subfolders.

And if you want to specify the subfolders where you want to look for the solution files you have to activate the vssolution.openSolutions.inAltFolders setting and specify the folders in the vssolution.altSolutionFolders setting:

You can combine all of these options to find the best configuration for you.

Features

Adds a Solution Explorer panel where you can find a Visual Studio Solution File Explorer:

Run dotnet commands in solutions and projects

Only available when the project is of kind CPS (dotnet core).

  • Build: dotnet build
  • Clean: dotnet clean
  • New: dotnet new
  • Pack: dotnet pack
  • Publish: dotnet publish
  • Restore: dotnet restore
  • Run: dotnet run
  • Watch: dotnet watch run

If you want to customize the terminal commands you can change them in the settings json file. These are the default commands configuration:

…

It will replace keywords like $solutionPath or $projectPath with the actual values.

As an example, if you want to compile in Release mode every time you publish a project you can create something like:

json
{
  "vssolution.customCommands":  {
    "publish": [ "dotnet", "publish", "\"$projectPath\"", "-c", "Release" ]
  }
}

Drag and drop files, folders and projects

Create, delete, rename or project folders and files

Create, delete, rename or move solution, solution folders and projects

Add new project (panel)

Besides the classic step-by-step "Add new project" wizard, solutions have an "Add new project (panel)" command that opens a Visual Studio-style, two-pane dialog: a searchable list of the dotnet new templates installed on your machine on the left (filterable by name or tag), and on the right a form to set the Project Name, Project Language, Location (with a folder picker) and .NET Framework once you pick a template.

The template's description and the frameworks it actually supports are fetched on selection, so the Framework field is populated per-template rather than a generic list; fields that don't apply to a given template (e.g. one that only supports a single language, or doesn't expose a --framework option) are disabled instead of shown as free-form input.

Add or remove nuget packages

Only available when the project is of kind CPS (dotnet core).

If you want to use custom nuget feeds it will look for a file called nuget.config in the root folder of the project and its parent folders. If it finds this file, it will read the configuration and use it. If it does not find it, it will use the default nuget feed.

As an Example:

xml

  
    
    
  
  
	  
	    
      
	  
  

If you are working with /drive/path/to/project.csproj, it will look for:

  • /drive/path/to/nuget.config
  • /drive/path/nuget.config
  • /drive/nuget.config
  • /nuget.config

Note vscode-solution-explorer only supports ClearTextPassword credencials in nuget.config

Update all nuget packages versions

Only available when the project is of kind CPS (dotnet core).

Inline nuget package version management (csproj)

Only available when the project is of kind CPS (dotnet core) c# projects.

If you open a .csproj file you can see if the nuget packages versions are out-dated. You can update them by clicking on the `` icon and select the version you want to use. It also adds code completions for packages names and versions.

Or if you hover over a package version you can see a tooltip with all the available versions.

Notes: This feature uses caching to avoid unnecessary calls to the nuget server. If you want to force the cache update you can use the Solution Explorer: Invalidate Nuget Cache command.

Add or remove project references

Only available when the project is of kind CPS (dotnet core).

Create file templates

This extensions has a custom template system to create new files. When you create a new file you can select a template from the dropdown list:

You can customize the templates for your project. First of all click with the right mouse button on your solution file and select Install File Creation Templates. Then you have to move to .vscode/solution-explorer folder and you can find the file called template-list.json. This file contains the list of templates.

We strongly recommend you to update your templates after updating this extension:

Solution syntax highlighting

This extension adds syntax highlighting to .sln files.

And also for .slnx files.

Create Directory.Packages.props

You can add a Directory.Packages.props on Solution under Solution items folder. This option will remove all Version attribute of the PacakageReferences in the projects files. You can also add an existing Directory.Packages.props with Add Solution file on a folder.

If a Directory.Packages.props are already present on the solution, after add a new project all PackageReferences will be updated and added the PackageVersion to the current file.

MSBuild property and condition evaluation

The project reader understands a realistic subset of MSBuild, so the tree reflects what would actually be built instead of just what's literally written in the xxproj file:

  • Condition attributes are evaluated (not just stored) on PropertyGroup, ItemGroup and individual items, supporting ==, !=, And/Or/!, parentheses, Exists() and boolean literals. This fixes the common "same property set for Debug and Release in two different PropertyGroups" case, which previously always resolved to whichever one appeared last in the file.
  • Properties ($(...)) cascade in document order like real MSBuild, including reserved ones seeded up front: MSBuildProjectDirectory, MSBuildProjectDirectoryNoRoot, MSBuildProjectFullPath, MSBuildProjectFile, MSBuildProjectName, MSBuildProjectExtension, MSBuildThisFileDirectory, MSBuildVersion, Configuration and Platform.
  • Multi-targeted projects (net8.0;net472) get a derived $(TargetFramework) (the first entry) so per-TFM conditions still resolve, even though this reader evaluates the project once rather than per target framework.
  • `` elements, and auto-discovered Directory.Build.props / Directory.Build.targets / Directory.Packages.props (found by walking up from the project directory, same as MSBuild), are merged into the evaluation - including central package management version resolution for PackageReferences that don't specify a Version.
  • Changes to any of these .props/.targets files - even ones living outside the project's own folder - automatically reload the affected project(s) in the tree.

Edit MSBuild Properties

Solution and project nodes have an "Edit MSBuild Properties..." command (also in their context menu) that opens a form to override Configuration, Platform, TargetFramework (offered as a dropdown when the project multi-targets) and any custom property, without touching the project files themselves. Overrides set on a project take precedence over the ones set on its solution, which in turn take precedence over the vssolution.defaultMsBuildConfiguration / defaultMsBuildPlatform settings below.

Multilanguage support

The extension's UI (commands, menus, settings descriptions and the panels above) is localized and follows VS Code's display language automatically. Currently supported languages: English (base), German (de), Spanish (es), French (fr), Portuguese - Portugal (pt-pt), Portuguese - Brazil (pt-br) and Simplified Chinese (zh-cn).

The de, es, fr, pt-pt, pt-br and zh-cn translations are AI-generated. If you're a na

Issues· 49 开放

查看全部 Issues在 GitHub 打开

暂无开放 Issues,或尚未同步最近议题。

> 标签

TypeScript

暂无评论,来聊聊你的看法吧

> 工具信息

发布日期2026年8月1日
最后更新2026年9月17日
分类编程语言
定价开源

> 相关工具

T
TypeScript
JavaScript 的超集,为前端与全栈提供静态类型
P
Python
通用编程语言,广泛用于 Web、数据与 AI
G
Go
Google 推出的简洁高效系统语言