pimhwang/ILSpy - ILSpy - git.quantfans.net

Author	SHA1	Message	Date
Siegfried Pammer	931375708f	Carry all RIDs in the decompiler-test lock files ICSharpCode.Decompiler.Tests builds for the host RID (so the native Microsoft.DiaSymReader.Native assets the Windows PDB tests need are copied), which made its packages.lock.json host-specific (linux-x64 vs win-x64) and drift between Linux and Windows restores. Add an explicit <RuntimeIdentifiers> list next to the single <RuntimeIdentifier>: the lock then records every RID host-independently while the build still targets the host RID. Apply the same list to the TestRunner it pulls in. TestRunner's lock is now fully portable. The test project's lock still carries the OS-conditional DiaSymReader.Native difference in its base graph, which the *.filelist-scoped "Verify package contents" step already tolerates. Assisted-by: Claude:claude-opus-4-8:Claude Code	4 weeks ago
Siegfried Pammer	667f6ad5f8	Add pwsh dev scripts, repo-wide lock files, and CI NuGet caching Replace the Windows-only .bat helpers (clean / debugbuild / releasebuild / restore / updatedeps and BuildTools/format) with cross-platform pwsh scripts at the repo root: restore.ps1, build.ps1 (-Configuration), clean.ps1, updatedeps.ps1 and BuildTools/format.ps1, alongside the existing publish.ps1. Enable a packages.lock.json for every project by hoisting RestorePackagesWithLockFile into the root Directory.Build.props (the four core libraries set it individually before) and commit the generated locks, so restores are repeatable and CI can cache packages off them. Cache the NuGet packages folder in the three setup-dotnet workflows (build-ilspy, build-frontends, codeql-analysis), keyed on the lock files per the setup-dotnet caching guidance. Scope the Debug "Verify package contents" check to the .filelist outputs it actually generates. A project's packages.lock.json is keyed only by (framework, RID), with no host-OS axis, so a lock produced on Linux legitimately differs from one produced on Windows whenever an OS-conditional PackageReference applies (Debug+Windows pulls Microsoft.DiaSymReader). The Windows restore then rewrites those locks; that churn must not fail a step whose job is to police the VSIX/MSI file lists. Also drop the dead ILSpy.BamlDecompiler publish line from publishlocaldev.ps1, mirroring the earlier publish.ps1 fix. Assisted-by: Claude:claude-opus-4-8:Claude Code	4 weeks ago
Christoph Wille	6f1c2b6cc9	.NET 11 for Tests (#3695 ) * .NET 11 RC2 minimal changes * Heuristic for transport feed Roslyn selection * Microsoft.CodeAnalysis.NetAnalyzers from main NuGet feed * Use the VS2026 image * Switch all test projects to net11 * Extract constants * Include vsix with plain nuget.config files	3 months ago
Siegfried Pammer	77d9ee73e9	Fix IDE2000 globally	6 months ago
Peter Crabtree	e1e16b64f5	dev: Strip BOM mark from text files	10 months ago
Siegfried Pammer	e4ebe20602	Upgrade dotnet target framework to net10	1 year ago
Siegfried Pammer	a94d66561a	Move to .NET 8.0 (#3119 ) * Basics of net8.0. Breaking unit tests expected. * Missed that TestRunner project was already upgraded to net7.0 (search and replace fail) * Use Preview 6 locally * Use .NET 8.0 RTM * Final fixups --------- Co-authored-by: Christoph Wille <christoph.wille@gmail.com>	3 years ago
Daniel Grunwald	8cc186d599	Use .NET 7.0 as target framework for the tests. This will be necessary for testing newer language features such as `ref` fields.	3 years ago
Siegfried Pammer	e24b901cd1	Build self-contained test runners before running tests.	4 years ago
Siegfried Pammer	e4b63f7a35	- Make all tests async. - Use custom test runner for correctness tests. - Use .NET 6.0 framework for all Roslyn compiler tests. - Disabled tests involving new string interpolation patterns.	4 years ago