Repository navigation
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); now one refresh runs at a time and the requests that come meanwhile share one more. The list of package sources is read once for a few seconds instead of by one
dotnet nuget list sourceprocess per few packages (178 in 80 seconds).