Repository navigation
Releases
v0.3.0
Our own refactorings in the Ctrl+. menu (a pre-release: they have been tried on a 50-project solution, not on many), Simplified Chinese (the extension speaks the language VS Code does), and fixes found while using them.
- Added, refactorings: Visual Studio's and Rider's refactorings the C# language server lacks, in the same Ctrl+. menu (the C# extension is needed; they run inside its server): Extract Interface (choose members, generic constraints kept), Extract Members to Partial Class, Extract Superclass, Extract Class, Pull Members Up, Push Members Down, Use Base Type Where Possible, Convert Abstract Class ↔ Interface, Move Type to Namespace, Change Signature, and Extract Method / Local Function checked by the compiler (the server's own makes uncompilable
outparameters). Choices are asked in a form in the editor area (Esc or Cancel changes nothing); every result is compiled in the projects it touches before it is applied, and nothing is applied when it would add errors; a new type or file whose name exists already is refused. Refactorings describes each one. - Added, settings:
shinobi.refactorings.disabledhides refactorings you never use (the entries sit in the Refactor menu group that fits them: extract, rewrite, move). - Added, all views: the manifest's strings are localized in
package.nls.jsonandpackage.nls.zh-cn.json(commands, submenus, settings with their descriptions and enum values, view titles, welcome pages, custom editors and task definitions), and the extension host's messages inl10n/bundle.l10n.jsonandl10n/bundle.l10n.zh-cn.jsonthrought()insrc/core/i18n.ts, which takes the English text as the key. - Added, webviews: a shared dictionary (
src/webview/shared/i18n.ts) translates the Solution Explorer, NuGet manager, Error List, Configuration Manager, Startup Projects, Publish and New Project panels; they follow the language VS Code runs in (<html lang>set by their HTML), not a setting of their own. - Added, refactorings: Change Signature (Ctrl+. on a method, constructor or local function, or on a call): reorder, add, remove, rename and retype parameters; callers, overrides, implementations, renamed uses and
<param>tags follow, the result is compiled before it is applied. - Added, rename: a file renamed in VS Code's Explorer offers to rename the type named after it (and its references), like the Solution Explorer already did; F2 on a type in a C# file named after it offers to rename the file afterwards.
- Added, Solution Explorer: file nesting puts
Order.Lines.csunderOrder.cs(parts of a partial class, also what Extract Members to Partial Class writes);fileNesting: offshows them flat. - Fixed, refactorings: Extract Members to Partial Class keeps the modifiers of the type (
internal,static,sealed...) on the new part. - Fixed, launch profiles: a
launchSettings.jsonthat starts with a byte order mark (Visual Studio writes it that way) was ignored with "InvalidSymbol at offset 0"; it is read. - Fixed, Solution Explorer: expanded folders are restored parents first, and a folder that is gone is no error line on every refresh.
- Fixed, rename: a renamed file in a project with several target frameworks is read again by the language server (the files using the type kept "could not be found" until the window was reloaded).
- Fixed, menu generator:
npm run generate:menuswrites the NLS keys of the generated commands and submenus topackage.nls.jsonagain, so regenerating the menus keeps the Chinese titles. - Fixed, Solution Explorer: the view is contributed once, to the activity bar container, and
shinobi.solutionExplorer.location'ssecondary-sidebaris applied at activation withvscode.moveViews, which moves the view to the secondary sidebar and back. A host whose core has no such container keeps the view in the side bar, without the warning the second contribution caused. - Fixed, Solution Explorer: the view no longer hides itself in a folder without
.sln/.slnxfiles; it is activated when it opens (not only by a solution in the folder) and shows "No solution in this folder" with the Create New Project... and Open Solution... buttons where the tree would be, in English and Chinese. - Fixed, Create New Project:
dotnet new's solution templates carry no type tag and were taken for project templates, so the wizard created a solution, then randotnet new slnagain in the project's folder, found no project file there and removed the whole folder, leaving nothing behind. The template is now recognised as a solution from itsSolutionclassification and creates the.slnx(.slnwith SDKs before 9.0.200, or the format picked in the wizard) without a project. The solution filter template, which also says "Solution", is not offered. - Fixed, Solution Explorer: where a view container sits is workbench state, not something a manifest can set. A container that was moved to the panel (or ended up there) is not part of either sidebar, so it can be missing from the activity bar even with the view always contributed. On activation the extension resets the container's location: it is in the activity bar (left sidebar) again; with
shinobi.solutionExplorer.location: "secondary-sidebar"its view is moved to the right sidebar, or to the left one on hosts without that container. - Added, Solution Explorer:
shinobi.solutionExplorer.locationhas a third value,manual: the extension leaves the Solution Explorer where you dragged it and does not reset its location on activation (sidebar, the default, still does, which brings back a view container stuck in the panel).
v0.2.1
Fixes from the first tests on Windows and on a 50-project solution (Cirrus.Core): the Test Explorer lists only test projects and every target framework of them, the NuGet manager finds vulnerable packages that projects only get through other packages or other frameworks and reads them in one go, Select Framework is the solution's (also the C# language context), and the log is quiet.
- Fixed, Test Explorer: a .NET Framework test app (
net472, e.g. xUnit v3) is started as its own exe (withmonoon Linux and macOS), not throughdotnet, which failed with "hostpolicy.dll not found"; libraries below aDirectory.Build.propsthat names test packages (even only under aCondition) are no longer listed as test projects: MSBuild'sIsTestProjectdecides. - Fixed, Solution Explorer: the wavy underline of nodes with warnings and errors was clipped to a dotted line by the name's
overflow: hidden; messages (infos) get the wavy line too, not a dotted one. - Added, Solution Explorer: the count and the dot next to nodes with problems are gone, the squiggly underline stays; the mouse over the name of such a node opens a small box with the name and what is below it ("1 error, 3 infos"), and a click on its text shows those problems in the Error List, narrowed to that node (a chip clears the narrowing).
- Added, Error List: columns can be resized by dragging the border of their header (double-click resets).
- Changed, Test Explorer: a multi-targeted test project is tested for every target framework (
MyTests (net8.0),MyTests (net10.0)), not only the one Select Framework or the automatic pick chose. - Fixed, Solution Explorer: the tree scrolls again (touchpad, wheel, scroll bar) when it is taller than the view: its container cut the rows off instead of letting the tree scroll.
- Changed, all views: the scroll bars are thin, without arrow buttons, with a transparent track and a translucent thumb in the theme's slider colours, like VS Code's own lists.
- Changed, log: the Output log holds what happened (opening a solution, installing a package, a failure), not a line per tree node, file change, cached package or tab click; the rest is at debug level (Developer: Set Log Level). A message below the channel's level is no longer built at all, so an object in a debug line (the whole solution, a NuGet data message) is not dumped for nothing.
- Fixed, NuGet manager and Dependencies: the transitive packages of a project that targets several frameworks were those of one framework only (
Cirrus.Core.Localisation: itsSystem.Security.Cryptography.Pkcs, which exists fornet10.0only, was missing next to the NU1902 warning), packages that only a referenced project brings in were missing (92 of 119 forCirrus.AspNetCoreonnet471; they now say "Transitively referenced by: Cirrus.Core (project)"), and for projects withnet471next tonet10.0thenet471graph was read from the wrong target (the long.NETFramework,Version=v4.7.1key comes first inproject.assets.json, the frameworks list hasnet10.0first). Transitive packages now cover every framework of every project, so the vulnerable ones show up in the list, the labels and the filter. - Fixed, Solution Explorer: files that a package's build props add to a project as hidden links (
<Visible>false</Visible>) are not listed:xunit.abstractions.dllandxunit.runner.visualstudio.testadapter.dllshowed in every test project that usesxunit.runner.visualstudio, Visual Studio does not list them either. - Fixed, Select Framework: the menu listed
net10.0afternetstandard2.0and marked it "Legacy" (onlynet8.0andnet9.0counted as current); now .NET 5 and later come first, newest first, then .NET Framework, .NET Standard and older. - Changed, Select Framework: it lists the target frameworks of all the projects, not only the startup project's, and the choice is the solution's: F5 follows when the startup project targets it, the Dependencies tree follows for the projects that target it, and the C# extension's project context of their open files (and of files as they are opened) is switched to it (
csharp.changeProjectContext), so#ifregions and diagnostics of a multi-targeted library go by that framework. - Added, NuGet: when a solution opens and a
NuGet.Configin it lists nuget.org by its V2 address (https://www.nuget.org/api/v2/, or.../api/v3/withoutindex.json, which NuGet takes for V2 and fails on) the extension offers to change it tohttps://api.nuget.org/v3/index.json: the V2 feed has no vulnerability data. Settingshinobi.nuget.offerV3Migration; the user's own config is left alone. - Fixed, NuGet manager: vulnerabilities and deprecations are read from the last restore (no restore of their own), for the whole solution in one go instead of two processes per project, one read at a time per manager, and the last complete result is kept in memory and shown at once when a manager opens or refreshes; a read that failed (no network) no longer wipes what was known. A solution on a big repository took minutes per read, and every refresh started another.
- Added, NuGet manager: a manager that is opened again (the tab was closed, or another opened) shows the lists of the last time at once, with the note "Showing the last result while the lists are read again..." and the controls off, and replaces them when the new ones are here; kept in memory for the session (not on disk).
- Changed, NuGet manager: a project's vulnerable version in the project list is shown in the colour of an error, bold, with the severities in its tooltip (also its transitive versions); the hover box over a transitive version is as wide as its hops need, up to the window, and keeps a package with its version on one line.
- Changed, NuGet manager: the details of a transitive package no longer start with the long "Transitively referenced by: …" list; hovering the version of a project in the project list shows every hop from what the project references (a package or a referenced project) down to the package, per framework. The row in the list says "Transitive, in N projects".
- Fixed, NuGet manager: the project list in the details of a package said "Not installed" for the projects that only get it through other packages; it now shows the version each gets, e.g.
9.0.11 (transitive)(several when its frameworks differ), for the top-level and the transitive row. - Changed, NuGet manager: in the solution manager a package some project references itself is listed once, as top-level, not again under Transitive packages; the versions other projects get through packages are folded into it (they flag it as vulnerable, and its project list shows
9.0.11 (transitive)for those projects). - Fixed, NuGet manager: the solution's transitive list left out every package that any project references itself, so a vulnerable
System.Security.Cryptography.Pkcs9.0.11 that 19 projects get throughMicrosoft.Data.SqlClientwas missing as soon as one project referenced 10.0.14; now a version that comes in through others and is not the version some project references stays in the Transitive packages (the referenced one is the top-level package). - Fixed, NuGet manager: a package that the projects use in several versions was labelled by the one version the list shows (the highest for transitive packages), so a vulnerable older version (
System.Security.Cryptography.Pkcs 9.0.11next to 10.0.14) had no label and was missed by the Vulnerable filter; now any version in use counts, and the details name the vulnerable versions. A faileddotnet list package --deprecated/--vulnerableis logged with the CLI's reason. - Fixed, NuGet manager: vulnerabilities were missing completely when the NuGet.Config lists nuget.org by its V2 address (
https://www.nuget.org/api/v2/, as in Cirrus.Core): that address has no vulnerability data, sodotnet list package --vulnerablefound nothing; the manager now asks nuget.org's V3 feed for them in that case. - Fixed, NuGet manager: the Vulnerable and Deprecated checkboxes also filter the transitive packages (they were not filtered, and the section stayed collapsed, so a vulnerable transitive package could not be found); with one of them on, the transitive section is open.
- Fixed, NuGet manager: a package that fails to install says why ("Cannot edit items in imported files" for a package that a
Directory.Build.propsreferences, e.g.Cirrus.RuleSetin the test projects), not only "Command failed"; the CLI prints its errors to stdout, which the message left out. - Changed, log: a package whose details one feed does not have (a 404 from a private feed for a public package) is not logged; only when no feed has it comes one warning that says what each answered (
birs: not found; nuget.org: not found, or the reason a feed could not be reached). A failed background refresh is one line (the reason, not the stack) instead of two with a stack. - Added, Run & Debug: the setting
shinobi.debug.consolepicks where the started program's console goes: the integrated terminal (as before), a console window of its own (externalTerminal) or the Debug Console. - Added, NuGet manager: Updates and Consolidate have a Package source dropdown that filters the lists to the packages one feed gives (Select all and Update Selected follow what is shown).
- Changed, NuGet manager: Update and Consolidate add the package to each project with
dotnet add package --no-restoreand restore once afterwards (the solution when more than one project or a props file changed), instead of one restore per project that restored the projects it references again each time. - Fixed, NuGet manager: a burst of changes (every project's first evaluation at start, one per project after an update) started a full refresh each, on top of each other (about 20 in 40 seconds on a 50-project solution); ...
v0.2.0
The first stable release: the Solution Explorer toolbar, feed credential and solution file fixes, a NuGet manager that fills the editor, and a tidier code base.
- Fixed, NuGet manager: the tab content fills the editor's height instead of stopping a guessed 120 px short, which left a gap at the bottom and could push buttons out of view when the panel was open.
- Fixed, solution and project files: a
.slnwith a stray line between two project blocks, or a block withoutEndProject, no longer drops the projects after it; two quick edits of the solution (drag and drop, context actions) are applied one after the other instead of one overwriting the other; a project file edited from outside with the same size and timestamp is no longer taken for our own write; removing the last item of an<ItemGroup Condition=...>removes the group; item-like text inside<![CDATA[...]]>is ignored. - Fixed, feed credentials: entering a token for a feed (
MyFeed) no longer rewrites the credentials of a feed whose name starts the same (MyFeed-Preview) and removes the first feed's own password; a token is never written into a commented-out block; a user name containing$&is stored as typed. If the credentials sit in a NuGet.Config inside your workspace or a git checkout, you are asked before a new token is saved there, and can save it to your user NuGet.Config instead. - Solution Explorer toolbar: one ▷ Start button (its arrow lists Start Without Debugging, Start with Hot Reload and Attach to Process...) instead of three start buttons; Sync with Active Document has a clearer icon and tooltip; The framework button (
net10.0 ▾) is a menu of the startup project's target frameworks and Startup Profile... instead of a quick pick. Open Solution... and Create New Project... are in the toolbar's...menu. The view's title bar reads "Solution Explorer" and has no buttons.
v0.1.3
New features, the rest of the code review and a Solution Explorer toolbar.
New
- Entity Framework: projects that reference Entity Framework Core have Add Migration, Update Database and Remove Last Migration in their context menu (
dotnet ef, with startup project and DbContext choice, and an offer to installdotnet-ef). - NuGet manager: installed versions with known vulnerabilities (severity, advisory links) or that are deprecated (with the replacement) are labelled, and the Installed tab can filter for them. Browse has a Package source dropdown (All, or one source) and every tab a Refresh button.
- Package sources like Visual Studio (opt-in setting
shinobi.nuget.packageSources): a Sources tab to add, remove, enable and disable feeds, and Package Source Mapping in the package details and in Browse. - Solution Explorer toolbar above the tree (configuration, framework or startup profile, Start, Sync, Show All Files, Collapse All) instead of title icons that VS Code hides in a narrow view. Built-in icons are VS Code's codicons (nothing is fetched from the internet any more); your file icon theme is still honored. New Dependencies > Frameworks node (
Microsoft.NETCore.App,Microsoft.AspNetCore.App), and files a project links from outside its folder count in the error markers. .nuget/NuGet.Config: Visual Studio's solution-level config is read by the NuGet manager, and the extension offers to move or copy it tonuget.config(wheredotnet restorereads it) when a solution opens or a restore fails.
Fixes
- Solution files: Add and Rename Solution Folder refuse a name a folder next to it has; Remove Solution Folder removes projects of every type and their configuration lines, also with lower-case GUIDs;
.slnxedits ignore XML comments; a.slnwith an absolute project path loads, and a project that cannot be read is skipped instead of failing the solution; a moved.slnxsolution folder stays open. - NuGet:
http://feeds work; redirects are followed without passing credentials to another host; answers have a size and time limit; folder sources no longer slow package lookups down; icons and READMEs are looked up on nuget.org only when it is a source; Browse showed the lowest version of a package several sources have, now the highest; the cache refreshes stale answers after 5 seconds, replaces private feeds' entries and is not undone by Refresh; onedotnet list packageper project; package rows no longer get wider than the list and the lists scroll. - Test Explorer: a failed build shows its first errors in the test message and Cancel stops it; a test host that crashes on start is reported at once.
- Startup project: choosing a startup project, framework or profile in quick succession ends with the last choice.
- Templates: the wizards use the SDK that
global.jsonpicks, asdotnet newwill. - Service references: Add and Update Service Reference keep edits made to the project file meanwhile.
- Solution Explorer: a file moved into a collapsed folder shows; hovering and switching editors no longer render every row; version properties of a parent
Directory.Packages.propsimported with unquotedGetPathOfFileAboveare found; the Configuration Manager and startup tabs follow Open Solution; the webviews no longer allowunsafe-eval.
0.1.2
Fixes, security hardening and the first results of the code review.
- Data safety: Delete Project no longer trashes the whole solution folder when the project sits next to the
.sln(or another project, or a git repository): only the project file goes, and the question says so. Add File and Add Folder refuse an existing name instead of emptying the file. Names with/,\,..,:,*and the like are refused when creating or renaming. Dependencies > Remove edits the project file as text (comments and formatting stay) and removes only the exact reference (Coreno longer removesMyCore), strong-named assemblies included; packages are removed the way the NuGet manager does it. - No shell:
dotnetcommands for solution edits, NuGet install/uninstall/restore, builds, tests and Add Project Reference run without a shell, so paths with&,;,$(,(or'work and cannot run anything. Add Project Reference checks for circles like the drop onto Dependencies. A successful command whose output says "error" is no longer reported as failed. - NuGet: the cache of feed responses lives in the extension's storage with hashed file names (credentials were in the file names in
/tmp), is private to the user, and does not serve old entries; a token with&,<or"is read back as typed; commented-out credentials inNuGet.Configare ignored. The package rows no longer get wider than the list for long descriptions, and the package lists scroll with the mouse wheel again. - Package READMEs can no longer show forms or cover the NuGet manager; the webviews forbid form submissions and
<base>. - Solution Explorer: the folders of
Foo.Testsexpand again when a projectFooexists (they were looked up inFoo). - Keys:
Ctrl+[,S(Sync with Active Document) no longer swallowsCtrl+[(Outdent Line) in editors andEscapein the terminal. - Packaging and release: the bundles carry their third-party licence notices; the extension declares that it needs a trusted, real-disk workspace; the release workflow builds without secrets and publishes from a separate job; runner and temp files of the Test Explorer and unloaded projects live in private folders.
- Docs: corrected claims about .NET Framework tests, Hot Reload, Attach to Process, privacy and keys.
0.1.1
Initial release. Visual Studio's tools for .NET in VS Code and VSCodium:
- Solution Explorer for
.slnand.slnx: solution folders and items, Visual Studio's file nesting (Off / Default / Web), your file icon theme, error markers, Dependencies with transitive packages, analyzers and source-generated code, Sync with Active Document, Collapse All, Visual Studio's context menus and keys; offers to convert.slnto.slnx; Unload / Reload Project, Pack on class libraries; Show All Files with Exclude From Project / Include In Project and linked files; drag and drop of projects, solution folders and files (with the namespace update after a move) - Run & Debug: Set as Startup Project with launch profiles, Open Launch Settings, Debug/Release, F5, Ctrl+F5, Debug > Start New Instance; SDK-style projects that target .NET Framework run and debug with Mono on Linux and macOS; several startup projects with Visual Studio's
.slnLaunchprofiles; Attach to Process with a picker of the running .NET programs (project, ports); offers to trust the HTTPS development certificate when anhttps://launch profile starts; Start with Hot Reload (dotnet watch, without the debugger) - Configuration Manager: solution configurations and platforms, and which configuration, platform and Build setting each project uses, written to
.slnand.slnx - Code Cleanup on the solution, a project, a folder or a file (
dotnet format: whitespace, unused usings, code style fixes) - Sync Namespaces on a project or a folder: the C# language server's "Change namespace" for every file whose namespace does not match its folders, references in other files updated
- Error List as a sortable, filterable table of errors, warnings and messages
- Tests: Test Explorer for Microsoft.Testing.Platform and VSTest projects; Run/Debug Tests from the Solution Explorer
- NuGet Package Manager: Browse, Installed with transitive packages, Updates, Consolidate; Central Package Management (
Directory.Packages.props: versions and overrides shown, changes confirmed, global packages); private feeds and expired tokens - Templates: Add New Project and Add New Item wizards for every
dotnet newtemplate - Publish: Visual Studio's Publish tab for Folder profiles
- Connected Services: WCF/SOAP service references, compatible with Visual Studio's, and gRPC references from
.protofiles or URLs - Manage User Secrets, Add Existing Item, Open in Terminal, Copy Full Path, and more
0.1.0
Initial release. Visual Studio's tools for .NET in VS Code and VSCodium:
- Solution Explorer for
.slnand.slnx: solution folders and items, Visual Studio's file nesting (Off / Default / Web), your file icon theme, error markers, Dependencies with transitive packages, analyzers and source-generated code, Sync with Active Document, Collapse All, Visual Studio's context menus and keys; offers to convert.slnto.slnx; Unload / Reload Project, Pack on class libraries; Show All Files with Exclude From Project / Include In Project and linked files; drag and drop of projects, solution folders and files (with the namespace update after a move) - Run & Debug: Set as Startup Project with launch profiles, Open Launch Settings, Debug/Release, F5, Ctrl+F5, Debug > Start New Instance; SDK-style projects that target .NET Framework run and debug with Mono on Linux and macOS; several startup projects with Visual Studio's
.slnLaunchprofiles; Attach to Process with a picker of the running .NET programs (project, ports); offers to trust the HTTPS development certificate when anhttps://launch profile starts; Start with Hot Reload (dotnet watch, without the debugger) - Configuration Manager: solution configurations and platforms, and which configuration, platform and Build setting each project uses, written to
.slnand.slnx - Code Cleanup on the solution, a project, a folder or a file (
dotnet format: whitespace, unused usings, code style fixes) - Sync Namespaces on a project or a folder: the C# language server's "Change namespace" for every file whose namespace does not match its folders, references in other files updated
- Error List as a sortable, filterable table of errors, warnings and messages
- Tests: Test Explorer for Microsoft.Testing.Platform and VSTest projects; Run/Debug Tests from the Solution Explorer
- NuGet Package Manager: Browse, Installed with transitive packages, Updates, Consolidate; Central Package Management (
Directory.Packages.props: versions and overrides shown, changes confirmed, global packages); private feeds and expired tokens - Templates: Add New Project and Add New Item wizards for every
dotnet newtemplate - Publish: Visual Studio's Publish tab for Folder profiles
- Connected Services: WCF/SOAP service references, compatible with Visual Studio's, and gRPC references from
.protofiles or URLs - Manage User Secrets, Add Existing Item, Open in Terminal, Copy Full Path, and more