pimhwang/ILSpy - ILSpy - git.quantfans.net

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
Daniel Grunwald	9b27ced6af	Avoid reference on ICSharpCode.Decompiler in VS AddIn. This way we don't need to load SRM 5 within the VS process.	6 years ago
Andreas Weizel	41e086cb26	Allow AddIn to detect framework of .NET Core assemblies correctly, if they are located in user's .nuget folder	6 years ago
dotnet format	0d9f871a4f	#2128 : Reformat the whole code base.	6 years ago
Siegfried Pammer	4b865c27e4	Fix #2076 : VS AddIn opens reference assembly.	6 years ago
Andreas Weizel	82524f391e	Fix #1720 : Support new path structure of reference assemblies with .NET Core 3.0	7 years ago
Andreas Weizel	c729922961	AddIn: Improve resolution of reference assemblies by removing code duplicates and using logic from ILSpy decompiler.	7 years ago
Siegfried Pammer	3d68da7237	Improve parsing of TargetFramework attribute in UniversalAssemblyResolver.	8 years ago
Andreas Weizel	2fb6e14339	Fixed #1164 : AddIn opens reference assembly when trying to open symbol in ILSpy	8 years ago