You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right Click on Assembly and Select "Scope search to this assembly"
Enter a search term along with a selection type in the search window
Error message shown
No Search Results Found
Details
Product in use: ILSpy
Version in use: 8.0.0.7246-preview3
I have an assembly FooBar.exe which when opened in ILSpy shows it as FooBar in the Assemblies tree.
However when performing searches in the assembly, I noticed the results come up as foobar, Version=EtcEtc., Culture=EtcEtc... instead of FooBar.
It seems that there's a discrepancy between the casing of the assembly name and the assembly as it's named in the search results. Because ILSpy automatically adds the non-lowercased version (inassembly:FooBar) but it appears to be case-sensitive, it never finds any results. If I manually change it to inassembly:foobar then it works.
The text was updated successfully, but these errors were encountered:
doubledgedboard
changed the title
inassembly search filter is case sensitive and automatically suggests the wrong term
[8.0.0.7246-preview3] inassembly search filter is case sensitive and automatically suggests the wrong term
Feb 25, 2023
Steps to reproduce
Error message shown
No Search Results Found
Details
I have an assembly
FooBar.exe
which when opened in ILSpy shows it asFooBar
in the Assemblies tree.However when performing searches in the assembly, I noticed the results come up as
foobar, Version=EtcEtc., Culture=EtcEtc...
instead ofFooBar
.It seems that there's a discrepancy between the casing of the assembly name and the assembly as it's named in the search results. Because ILSpy automatically adds the non-lowercased version (
inassembly:FooBar
) but it appears to be case-sensitive, it never finds any results. If I manually change it toinassembly:foobar
then it works.The text was updated successfully, but these errors were encountered: