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
dotnet format
0d9f871a4f
#2128 : Reformat the whole code base.
6 years ago
Siegfried Pammer
40687ea8ad
#1498 : Remove Fusion API usage: Use standard file enumeration instead. This should enable us to use the GAC even with restricted access, as only the LIST permission is required.
6 years ago
Andreas Weizel
39e879377e
Fix VSIX analyzer warnings and disabled the analyzer
7 years ago
Siegfried Pammer
069e4072de
Fix compile errors after merge.
8 years ago
Andreas Weizel
a94671183e
AddIn: Added detection of non-existing assembly files when launching ILSpy, showing a warning message in those cases. In case of project output assemblies, offers building the solution.
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