ILSpy

Commit Graph

Author	SHA1	Message	Date
Siegfried Pammer	bdf7e35e14	Drop the stale net10.0-windows segment from publish-output paths ILSpy targets net10.0, not net10.0-windows; the VS add-in build paths, the installer output dir, the local-dev publish script, and the VS Code launch config still referenced the old net10.0-windows layout. Align them with the actual TFM, matching publish.ps1 and the build workflow. Assisted-by: Claude:claude-opus-4-8:Claude Code	4 weeks 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	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
Christoph Wille	b5fc0d5b06	Use releaseTag with fallback to downloadUrl in updates.xml (#3713 ) * Use releaseTag with fallback to downloadUrl in updates.xml * Add tests * Prevent arbitrary downloadUrl - must start with BaseUrl as well * Remove custom domain ilspy.net in end-user visible places	3 months ago
Christoph Wille	120154e21c	Remove Translations (#3648 )	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
Christoph Wille	a0e22b1757	IncludeInVSIX passes original name unchanged (ignores Linked)	2 years ago
Christoph Wille	4bad0c7a4b	Move license.txt to root folder LICENSE file	2 years ago
Christoph Wille	60251044cd	Adapt ILSpyInstance:Start to new command line options	2 years ago
Christoph Wille	084d02a447	Apply Central package management (requires package source mapping) (#3124 ) * Apply Central package management https://learn.microsoft.com/en-us/nuget/consume-packages/central-package-management (requires package source mapping https://learn.microsoft.com/en-us/nuget/consume-packages/package-source-mapping) * Microsoft.DiaSymReader.Converter.Xml from dotnet-tools, Microsoft.DiaSymReader.Native from nuget.org feed * Trying to sort what is on which feed for previews of Diasymreader packages * Parse the Roslyn version from Directory.packages.props * Use specific versions for Diasymreader from nuget.org to allow VS2022 addin to restore properly * Tests needs also locked references	3 years 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
Christoph Wille	a6a86a6165	Microsoft.VSSDK.BuildTools 17.6.2164 for both projects	3 years ago
Christoph Wille	fb2f98061c	Update Microsoft.VSSDK.BuildTools	3 years ago
Christoph Wille	636219d539	Enable arm64 installation	3 years ago
Christoph Wille	d43a5c94e7	Adapt GetILSpyPath and copy both x64 and arm64 ILSpy into the VSIX for VS 2022	3 years ago
Christoph Wille	040ac1ac81	Switch from default output directory to publish folder	3 years ago
Christoph Wille	9cc35cdca2	Move VS Extensions projects to a separate solution	3 years ago
Christoph Wille	ace11158a2	Use latest VS SDK (#2767 ) * Update https://www.nuget.org/packages/Microsoft.VSSDK.BuildTools to 17.3.2093 to match https://github.com/actions/runner-images/blob/main/images/win/Windows2022-Readme.md (VS Build # to version: https://docs.microsoft.com/ro-ro/visualstudio/install/visual-studio-build-numbers-and-release-dates?preserve-view=true&view=vs-2022) * Upgrade downlevel (<=2019) addin too to 17.3.2093	4 years ago
Christoph Wille	62f9061dc3	Go back to 17.1.4054 for VS SDK (maybe that breaks the build server; locally works)	4 years ago
Christoph Wille	4777cb0450	Update NuGet packages	4 years ago
Siegfried Pammer	504d16e44d	Use ReferenceAssemblyAnnotator in ILSpy.AddIn.csproj and ILSpy.AddIn.VS2022.csproj	4 years ago
Siegfried Pammer	a2b1e9a6ca	Use VSIXSourceItem to add ILSpy distribution to VSIX after ResolveProjectReferences.	4 years ago
Siegfried Pammer	c7719b1a6f	Try again to remove ILSpy.dll.config.	4 years ago
Siegfried Pammer	d5f8145a10	Convert solution-level dependencies to project-level dependencies. Solution-level dependencies are incompatible with slnf.	4 years ago
Christoph Wille	04b75be5d2	Go back to Microsoft.VSSDK.BuildTools 17.1.4054	4 years ago
Siegfried Pammer	fa451b5b87	Update nuget packages and references for VS2022.	4 years ago
Siegfried Pammer	4519c3b5c1	Remove leftovers of AppVeyor-specific configuration.	4 years ago
Siegfried Pammer	bf3b93ec76	Fix #2644 : Ignore warnings MSB3277 and VSSDK1009	4 years ago
Siegfried Pammer	1ccc63b829	Revert removal of app.config.template	4 years ago
SilverFox	2ce3419019	Fix build for VSAddIn	4 years ago
Christoph Wille	9e1c2ab7c9	Remove <Preview> from VS 2022 addin manifest	4 years ago
Christoph Wille	379cc763c0	Fix ILSpyBuildPath and .exe.config -> .dll.config. Note: should use output from dotnet publish!	4 years ago
Siegfried Pammer	9e54b44b11	Move ILSpy to net6.0-windows	4 years ago
Christoph Wille	e82dd73872	Update Microsoft.VisualStudio.SDK for 2022 extension - dependent NuGet Microsoft.VisualStudio.Setup.Configuration.Interop now available	5 years ago
Christoph Wille	582002888b	Revert "Final Microsoft.VisualStudio.SDK for 2022 extension" This reverts commit `0625f815b0`.	5 years ago
Christoph Wille	0625f815b0	Final Microsoft.VisualStudio.SDK for 2022 extension	5 years ago
Christoph Wille	5916980f48	Publisher Name fix, add tags & preview info	5 years ago
Andreas Weizel	11c107e32f	Try the opposite way: Use only project instead of build dependencies	5 years ago
Andreas Weizel	4f378f7790	Remove project reference on ILSpy from AddIns, use build dependencies instead	5 years ago
Andreas Weizel	f22343b482	Change display name of VS 2022 AddIn	5 years ago
Andreas Weizel	075c447954	Rename ILSpy.AddIn.VS17 to ILSpy.AddIn.VS2022	5 years ago

41 Commits (b6b1bf99be06def101713e5623c6e867a3a62ee2)