ILSpy — Search Feature Analysis

1. Executive Summary

The ILSpy Search subsystem provides interactive, incremental searching across all loaded assemblies. It follows a classic MVVM / strategy / factory layering pattern within a WPF application:

• SearchPane (UserControl + code-behind) acts as the UI orchestrator and owns the RunningSearch lifecycle.
• RunningSearch encapsulates one asynchronous search execution: parsing user input, selecting a strategy, running background tasks, and feeding a ConcurrentQueue.
• SearchPaneModel exposes bindable state (SearchTerm, SearchModes) and integrates with the docking system and session settings.
• AbstractSearchStrategy hierarchy (7 concrete classes) cleanly separates how each of 12 modes searches the metadata.
• SearchResultFactory produces typed results (Member, Resource, Assembly, Namespace) from domain objects.
• Inter-component coordination uses a static MessageBus<T> (pub/sub), keeping components loosely coupled.

Quality Gate Summary

2. Entity Inventory

2.1 Primary Entities (Search/ folder)

2.2 Search Strategies

2.3 Result Types

2.4 Data Models

2.5 Secondary / Supporting Entities

3. Search UI Pane — SearchPane

SearchPane is the outermost orchestrator of the search feature. It is a WPF UserControl with code-behind that manages the full search lifecycle from user input through asynchronous execution to result display and navigation.

3.1 Constants & State

3.2 Event Subscriptions (Constructor)

3.3 Key Methods

StartSearch(string searchTerm)

The central orchestration method. Called whenever the search term, mode, or assembly list changes.

// Pseudocode reconstruction from Abyss evidence
async void StartSearch(string searchTerm)
{
    currentSearch?.Cancel();                             // CRUD: D (cancel old)
    Results.Clear();                                     // CRUD: D (clear UI)

    resultsComparer = settingsService
        .DisplaySettings.SortResults
        ? SearchResult.ComparerByFitness
        : SearchResult.ComparerByName;                   // CRUD: R (read settings)

    var assemblies = assemblyTreeModel.AssemblyList
                         .GetAllAssemblies();            // CRUD: R
    var running = new RunningSearch(                     // CRUD: C (new search)
        assemblies, searchTerm, searchMode,
        language, languageVersion, apiVisibility,
        treeNodeFactory, settingsService);

    currentSearch = running;                             // CRUD: U (replace ref)
    await running.Run();
}

UpdateResults(object sender, EventArgs e)

Called by CompositionTarget.Rendering every frame. It drains currentSearch.ResultQueue until MAX_REFRESH_TIME_MS is exceeded or MAX_RESULTS is reached.

void UpdateResults(object sender, EventArgs e)
{
    var search = currentSearch;
    if (search == null) return;
    var sw = Stopwatch.StartNew();
    while (Results.Count < MAX_RESULTS && sw.ElapsedMilliseconds < MAX_REFRESH_TIME_MS)
    {
        if (!search.ResultQueue.TryTake(out var result)) break;
        // Sorted insertion or append
        Results.InsertSorted(result, resultsComparer);   // CRUD: C
    }
}

JumpToSelectedItem(bool inNewTabPage = false)

Navigates to the selected search result using the MessageBus.

void JumpToSelectedItem(bool inNewTabPage = false)
{
    var result = listBox.SelectedItem as SearchResult;   // CRUD: R
    if (result == null) return;
    MessageBus.Send(this,
        new NavigateToReferenceEventArgs(                // CRUD: C
            result.Reference, inNewTabPage));
}

4. Search Pane Model — SearchPaneModel & SearchModeModel

SearchPaneModel is the ViewModel layer for the search pane. It integrates with the docking framework (AvalonDock or equivalent) and provides bindable properties consumed by SearchPane.xaml.

4.1 Bindable Properties

4.2 The 12 Search Modes

4.3 Message Bus Subscriptions

5. Result Factory, Parsing & Strategy Selection

5.1 SearchResultFactory

The factory is instantiated per-search inside RunningSearch.Parse(), receiving the current Language and settings. This means every search execution gets a factory with a fresh language context — correct for multilingual display.

5.2 RunningSearch.Parse(string input) — Prefix Syntax

The Parse() method is the user-facing query language for the search box. It tokenizes the input using CommandLineTools.CommandLineToArgumentArray() and then scans for known prefix tokens to build a structured SearchRequest.

5.3 RunningSearch.GetSearchStrategy(SearchRequest)

A factory method (not a pattern class) inside RunningSearch that maps SearchMode to the appropriate AbstractSearchStrategy subclass:

AbstractSearchStrategy GetSearchStrategy(SearchRequest request) => request.Mode switch
{
    SearchMode.TypeAndMember => new MemberSearchStrategy(request, MemberSearchKind.TypeAndMember),
    SearchMode.Type          => new MemberSearchStrategy(request, MemberSearchKind.Type),
    SearchMode.Member        => new MemberSearchStrategy(request, MemberSearchKind.Member),
    SearchMode.Method        => new MemberSearchStrategy(request, MemberSearchKind.Method),
    SearchMode.Field         => new MemberSearchStrategy(request, MemberSearchKind.Field),
    SearchMode.Property      => new MemberSearchStrategy(request, MemberSearchKind.Property),
    SearchMode.Event         => new MemberSearchStrategy(request, MemberSearchKind.Event),
    SearchMode.Literal       => new LiteralSearchStrategy(request),
    SearchMode.Token         => new MetadataTokenSearchStrategy(request),
    SearchMode.Resource      => new ResourceSearchStrategy(request),
    SearchMode.Assembly      => new AssemblySearchStrategy(request),
    SearchMode.Namespace     => new NamespaceSearchStrategy(request),
    _                        => throw new ArgumentOutOfRangeException()
};

6. Architecture Diagrams

6.1 Class Diagram — Search Subsystem

6.2 Sequence Diagram — WF1: Search Term Entry

6.3 Sequence Diagram — WF2: Filter / Mode Change

6.4 Sequence Diagram — WF3: Result Selection & Navigation

7. CRUD Reference Table

8. Recommendations

8.1 Quality Recommendations

8.2 Security Recommendations

new Regex(pattern, RegexOptions.Compiled, matchTimeout: TimeSpan.FromSeconds(1))

if (searchTerm?.Length > 500) return;

9. Evidence Appendix — Abyss Query References

All findings in this report are grounded in Abyss code-intelligence queries against the indexed ILSpy repository (293 documents, 1,746 chunks, 1,729 SCIP-enriched). Each entry below shows the query, file evidence, and the key chunk excerpt used.