ILSpy

90 Tags

71 MiB

Tree: c79aefb325

Author	SHA1	Message	Date
Christoph Wille	aab6303870	Migrate the VS extension to an SDK-style VSIX (dotnet build) and retire the VS2017/2019 add-in (#3808 ) * Migrate ILSpy.AddIn.VS2022 to SDK-style VSIX project * Retire the legacy VS2017/2019 ILSpy add-in * Build the VS extension via dotnet build on the slnx * Inline ILSpy.AddIn.Shared into ILSpy.AddIn.VS2022 * Restore the VS add-in menus broken by the SDK-style migration	2 weeks ago
Peter Crabtree	e1e16b64f5	dev: Strip BOM mark from text files	10 months ago
Andreas Weizel	6e06ee407b	Prepare separation of AddIn for VS 2019 and VS 2022 - Move most code to a shared project/shared folder	5 years ago
dotnet format	0d9f871a4f	#2128 : Reformat the whole code base.	6 years ago
Andreas Weizel	39e879377e	Fix VSIX analyzer warnings and disabled the analyzer	7 years ago
Sam Harwell	6a2eab2a52	Switch to AsyncPackage with background load	8 years ago
Andreas Weizel	84758dca5e	Re-enabled "Open code in ILSpy" command in code editor, fixed several issues.	8 years ago
Andreas Weizel	809354f175	Fixed several issues with "Open in ILSpy" menu shown on non-applicable nodes. Refactored the commands.	8 years ago
Siegfried Pammer	cf9d803f5d	Fix some more bugs in ILSpy.AddIn	8 years ago
Siegfried Pammer	3581635a2d	Refactor ILSpy.AddIn and fix some bugs	8 years ago