ILSpy

Commit Graph

Author	SHA1	Message	Date
ds5678	7da058d3bf	Ensure that all other projects reference the netstandard2.0 target	2 months ago
Siegfried Pammer	e0cde005f9	Carry all publish RIDs in the core-library lock files ICSharpCode.Decompiler / ILSpyX / BamlDecompiler set RestoreLockedMode but declared no RuntimeIdentifiers, so their lock files were RID-agnostic. A RID-specific 'dotnet publish -r <rid>' of ILSpy (which declares all four distribution RIDs) propagated the RID to these locked project references and failed restore with NU1004 unless --no-restore or --force-evaluate was used. Declare the same win-x64;win-arm64;linux-x64;osx-arm64 set on the three libraries and regenerate the locks so a locked-mode publish works for every platform out of the box. 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	d3e12d0ebf	Migrate from .ruleset to .editorconfig	9 months ago
Peter Crabtree	e1e16b64f5	dev: Strip BOM mark from text files	1 year ago
Siegfried Pammer	e4ebe20602	Upgrade dotnet target framework to net10	1 year ago
Christoph Wille	1263f48dc0	Use Microsoft.Sbom.Targets in Decompiler, BamlDecompiler and ILSpyX NuGets (#3346 ) https://github.com/microsoft/sbom-tool/tree/main/src/Microsoft.Sbom.Targets to embed SBOM * GeneratePackageOnBuild removed, build action now has a new step for dotnet pack * Decompiler, BamlDecompiler and ILSpyX include SBOM	2 years ago
Christoph Wille	1048cd9557	Enable repeatable package restores (#3359 ) Locking restricted to projects that create NuGet packages ICSharpCode.Decompiler ICSharpCode.ILSpyX ILSpyCmd ICSharpCode.BamlDecompiler	2 years ago
Christoph Wille	cda1f8c7f1	Make BamlDecompiler packable for eventual NuGet distribution	3 years ago
Christoph Wille	0887d3e4d5	Move KnownThings.gen.cs compile remove	3 years ago
Christoph Wille	7c259a8895	Split Baml Addin into library & addin projects	3 years ago

11 Commits (2802403c1918de8621bf9f3854ef6f8c8d2818ae)