How thomasrush/amazonscrape works
Project type and purpose
• This is a standalone WPF desktop application written in C# (.NET).
• Its purpose is to scrape Amazon product data, apply search and validation logic, and display sortable results in a rich UI.
File structure
• Top-level artifacts:
• AmazonScrape.sln / .csproj – the Visual Studio solution and project file
• App.xaml / App.xaml.cs – application entry point and resource declarations
• Constants.cs – global constants used across the app
• README.md – high-level description
• “Model” folder: contains two subpackages:
• Logic – business-logic classes (SearchManager, Scraper, Parser, PageManager, ItemValidator)
• Structure – domain entities and data contracts (AmazonItem, Result, SearchCriteria, ScoreDistribution)
• “UI” folder: WPF presentation layer
• Controls – custom user controls (RangeSlider, DataGridPlus, ScoreDistributionControl, etc.)
• MainWindow.xaml / MainWindow.xaml.cs – main window and its code-behind
• Resources – styles, images, resource loader
• “UtilityClasses”: reusable helper classes for range types and converters
• Configuration files: App.config, packages.config, Properties/Settings
README for additional insights
• Confirms the project is “Amazon Product scraper” with search tools and sortable results
• No further architectural details are given, so we infer a 3-layer structure: Presentation (UI), Business Logic (Model/Logic), Data/Domain (Model/Structure), plus an external HTTP layer (Amazon).
Elements
• UI → Logic.SearchManager → Logic.Scraper → External Service
• Scraper → Parser → Domain.AmazonItem
• Parser → Domain.Result → UI