pimhwang/ILSpy - ILSpy - git.quantfans.net

Author	SHA1	Message	Date
Christoph Wille	080bee3db6	Enable CheckSdkVulnerabilities https://learn.microsoft.com/en-us/dotnet/core/tools/sdk-errors/netsdk1238	1 week ago
Siegfried Pammer	40a667fefb	Treat warnings as errors repo-wide A clean build currently has zero warnings; enforce that so new ones can't accumulate unnoticed. Set TreatWarningsAsErrors in the root Directory.Build.props rather than per project. ICSharpCode.ILSpyCmd keeps its existing TreatWarningsAsErrors=false (project-level wins over the imported default), and the three legacy net472 projects (the VS add-ins and the installer builder) opt out explicitly since they only build on Windows and aren't covered by the cross-platform CI that gates this. Assisted-by: Claude:claude-opus-4-8:Claude Code	3 months 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	3 months ago
Siegfried Pammer	d0fc0411fb	Update to C# 13 and fix field keyword	1 year ago
Siegfried Pammer	f0c80e4a80	Silence NU1510	1 year ago
Christoph Wille	1a41fd857e	Centralize EnableNUnitRunner, remove obsolete property TestingPlatformDotnetTestSupport	1 year ago
tom-englert	5be3f312ea	Add more defaults to .editorconfig to better match coding style	2 years ago
Siegfried Pammer	bd82b945ea	Revert "Accelerate local builds in Visual Studio (#3026 )" (#3063 ) This reverts commit `b482ae937f`.	3 years ago
Christoph Wille	b482ae937f	Accelerate local builds in Visual Studio (#3026 ) * Accelerate builds of SDK-style .NET projects https://github.com/dotnet/project-system/blob/main/docs/build-acceleration.md#validate-builds-are-accelerated * Verbose logging produced "Ensure projects producing the following outputs have the 'ProduceReferenceAssembly' MSBuild property set to 'true': 'D:\GitWorkspace\ILSpy\ICSharpCode.Decompiler\bin\Debug\netstandard2.0\ICSharpCode.Decompiler.dll'" - this relates to the documented problem of netstandard2.0 projects not generating the necessary reference assemblies (direct issue link https://github.com/dotnet/project-system/issues/8865) No harm for netcore projects as these produce those ref asms by default.	3 years ago