Skip to content

Bump Microsoft.Data.Sqlite from 8.0.0 to 10.0.14 - #2

Closed
dependabot[bot] wants to merge 120 commits into
mainfrom
dependabot/nuget/src/IpScanner/Microsoft.Data.Sqlite-10.0.14
Closed

Bump Microsoft.Data.Sqlite from 8.0.0 to 10.0.14#2
dependabot[bot] wants to merge 120 commits into
mainfrom
dependabot/nuget/src/IpScanner/Microsoft.Data.Sqlite-10.0.14

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 29, 2026

Copy link
Copy Markdown

Updated Microsoft.Data.Sqlite from 8.0.0 to 10.0.14.

Release notes

Sourced from Microsoft.Data.Sqlite's releases.

10.0.0-preview.6.25358.103

You can build .NET 10.0 Preview 6 from the repository by cloning the release tag v10.0.0-preview.6.25358.103 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.5.25277.114

You can build .NET 10.0 Preview 5 from the repository by cloning the release tag v10.0.0-preview.5.25277.114 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.4.25258.110

You can build .NET 10.0 Preview 4 from the repository by cloning the release tag v10.0.0-preview.4.25258.110 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.3.25171.5

You can build .NET 10.0 Preview 3 from the repository by cloning the release tag v10.0.0-preview.3.25171.5 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.2.25163.2

You can build .NET 10.0 Preview 2 from the repository by cloning the release tag v10.0.0-preview.2.25163.2 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.1.25080.5

You can build .NET 10.0 Preview 1 from the repository by cloning the release tag v10.0.0-preview.1.25080.5 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.123

You can build .NET 9.0 from the repository by cloning the release tag v9.0.123 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.122

You can build .NET 9.0 from the repository by cloning the release tag v9.0.122 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.121

You can build .NET 9.0 from the repository by cloning the release tag v9.0.121 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.120

You can build .NET 9.0 from the repository by cloning the release tag v9.0.120 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached is a PGP signature for the GitHub generated tarball. You can find the public key at https://dot.net/release-key-2023

9.0.119

You can build .NET 9.0 from the repository by cloning the release tag v9.0.119 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.118

You can build .NET 9.0 from the repository by cloning the release tag v9.0.118 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached is a PGP signature for the GitHub generated tarball. You can find the public key at https://dot.net/release-key-2023

9.0.117

You can build .NET 9.0 from the repository by cloning the release tag v9.0.117 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.116

You can build .NET 9.0 from the repository by cloning the release tag v9.0.116 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.115

You can build .NET 9.0 from the repository by cloning the release tag v9.0.115 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.114

You can build .NET 9.0 from the repository by cloning the release tag v9.0.114 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached is the PGP signature for the GitHub generated tarball. You can find the public key at https://dot.net/release-key-2023

9.0.113

You can build .NET 9.0 from the repository by cloning the release tag v9.0.113 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.112

You can build .NET 9.0 from the repository by cloning the release tag v9.0.112 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.111

You can build .NET 9.0 from the repository by cloning the release tag v9.0.111 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.110

You can build .NET 9.0 from the repository by cloning the release tag v9.0.110 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.109

You can build .NET 9.0 from the repository by cloning the release tag v9.0.109 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.101

You can build .NET 9.0 from the repository by cloning the release tag v9.0.101 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.7

You can build .NET 9.0 from the repository by cloning the release tag v9.0.7 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.6

You can build .NET 9.0 from the repository by cloning the release tag v9.0.6 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.5

You can build .NET 9.0 from the repository by cloning the release tag v9.0.5 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.4

You can build .NET 9.0 from the repository by cloning the release tag v9.0.4 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.3

You can build .NET 9.0 from the repository by cloning the release tag v9.0.3 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.2

You can build .NET 9.0 from the repository by cloning the release tag v9.0.2 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.1

You can build .NET 9.0 from the repository by cloning the release tag v9.0.1 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.0

You can build .NET 9.0 from the repository by cloning the release tag v9.0.0 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.0-rc.2.24473.5

You can build NET 9.0 RC2 from the repository by cloning the release tag v9.0.0-rc.2.24473.5 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.0-rc.1.24431.7

You can build .NET 9.0 RC1 from the repository by cloning the release tag v9.0.0-rc.1.24431.7 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.0-preview.7.24405.7

You can build .NET 9.0 Preview 7 from the repository by cloning the release tag v9.0.0-preview.7.24405.7 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.0-preview.6.24327.7

You can build .NET 9.0 Preview 6 from the repository by cloning the release tag v9.0.0-preview.6.24327.7 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.133

You can build .NET 8.0 from the repository by cloning the release tag v8.0.133 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.132

You can build .NET 8.0 from the repository by cloning the release tag v8.0.132 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.131

You can build .NET 8.0 from the repository by cloning the release tag v8.0.131 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.130

You can build .NET 8.0 from the repository by cloning the release tag v8.0.130 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.129

You can build .NET 8.0 from the repository by cloning the release tag v8.0.129 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.128

You can build .NET 8.0 from the repository by cloning the release tag v8.0.128 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.127

You can build .NET 8.0 from the repository by cloning the release tag v8.0.127 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.126

You can build .NET 8.0 from the repository by cloning the release tag v8.0.126 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.125

You can build .NET 8.0 from the repository by cloning the release tag v8.0.125 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.124

You can build .NET 8.0 from the repository by cloning the release tag v8.0.124 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.123

You can build .NET 8.0 from the repository by cloning the release tag v8.0.123 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.122

You can build .NET 8.0 from the repository by cloning the release tag v8.0.122 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.121

You can build .NET 8.0 from the repository by cloning the release tag v8.0.121 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.120

You can build .NET 8.0 from the repository by cloning the release tag v8.0.120 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.119

You can build .NET 8.0 from the repository by cloning the release tag v8.0.119 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.18

You can build .NET 8.0 from the repository by cloning the release tag v8.0.18 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.17

You can build .NET 8.0 from the repository by cloning the release tag v8.0.17 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.16

You can build .NET 8.0 from the repository by cloning the release tag v8.0.16 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.15

You can build .NET 8.0 from the repository by cloning the release tag v8.0.15 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.14

You can build .NET 8.0 from the repository by cloning the release tag v8.0.14 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.13

You can build .NET 8.0 from the repository by cloning the release tag v8.0.13 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.12

You can build .NET 8.0 from the repository by cloning the release tag v8.0.12 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.11

You can build .NET 8.0 from the repository by cloning the release tag v8.0.11 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.10

You can build .NET 8.0 from the repository by cloning the release tag v8.0.10 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.8

You can build .NET 8.0 from the repository by cloning the release tag v8.0.8 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

Commits viewable in compare view.

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

wbgcoding added 30 commits June 1, 2026 19:13
@wbgcoding
Add WPF IP-Scanner design spec
6e89fcb
@wbgcoding
Add WPF IP-Scanner implementation plan (31 tasks)
8b2bded
@wbgcoding
chore: scaffold WPF app + xUnit test project
86cc2d3 
Added IP-Scanner.slnx, IpScanner WPF project (net8.0-windows), and IpScanner.Tests xUnit project.
Added minimal App.xaml/MainWindow.xaml WPF entry points, PingResult model, and smoke test.
Smoke test passes (1/1). ApplicationIcon omitted until icon asset exists.
@wbgcoding
feat: add Device and NetworkInfo core models
c8adbc0
@wbgcoding
feat: add ScanConfig model and Ipv4 helpers
3be6821
@wbgcoding
feat: add ConfigManager flat-config reader
651db59
@wbgcoding
feat: add ConfigManager save with round-trip
8749edd
@wbgcoding
feat: add IcmpPinger via IcmpSendEcho P/Invoke
418133a
@wbgcoding
feat: add NetworkDetector (local IP/MAC/GW/DNS)
835cc20
@wbgcoding
feat: add ARP and NetBIOS hostname/MAC helpers
aef7466
@wbgcoding
feat: add reverse-DNS hostname resolver
085e540
@wbgcoding
feat: add group color palette (max-diversity)
52a8e27
@wbgcoding
feat: add device grouping logic
889a657
@wbgcoding
feat: add SQLite known-devices database
0a4f661
@wbgcoding
feat: add MAC vendor lookup (embedded OUI)
2b66d79
@wbgcoding
feat: add CSV exporter
5f21fc3
@wbgcoding
feat: add TXT report exporter
bb20b8b
@wbgcoding
feat: add two-phase ScanEngine with injectable pinger
c1c9add
@wbgcoding
feat: add ScanEngine progress counters
1aee3ca
@wbgcoding
feat: add MVVM ObservableObject and RelayCommand
c1cbfa1
@wbgcoding
feat: add DeviceViewModel
9c016b6
@wbgcoding
feat: add Progress/NetworkInfo/InternetHost view models
be0ec56
@wbgcoding
feat: add SettingsViewModel
4d5232c
@wbgcoding
feat: add MainViewModel scan orchestration
d86af51
@wbgcoding
feat: complete WPF UI, icon, and fix runtime bugs
4198590 
- Add MainWindow (header bars, device grid, network sidebar),
  SettingsWindow (6 tabs), Catppuccin theme, SegmentedProgressBar.
- Generate radar network.ico (multi-size) + wire ApplicationIcon/Window icon.
- Fix: missing Core.Export using; Dispatcher.Invoke->BeginInvoke + throttle
  (UI freeze); call DeviceGrouper.AssignGroups; add MAC/hostname enrichment
  (ARP+DNS+NetBIOS); group color mapping; FrameworkElement render.
- 47/47 tests pass; single-file exe launches.
@wbgcoding
feat: hide offline devices, color ONLINE status, restyle header buttons
72b020d 
- List shows online devices only; offline are removed live, device-count
  bar now sources online/offline/unknown from the engine (planned total).
- Status column rendered green/semibold.
- Add PillButton/AccentButton/DangerButton/GhostButton styles (rounded,
  hover/press) and apply to Scan/Stop/Settings.
@wbgcoding
style: modern dark theme across all controls
5e96002 
Add implicit styles for TextBox, ComboBox (retemplated), CheckBox,
TabControl/TabItem, DataGrid (headers/rows/cells), ScrollBar, and a
TextBlock default. Restyle SettingsWindow (header, accent/ghost/danger
buttons, rounded tabs). Removes leftover default-WPF (Aero) look.
@wbgcoding
feat: ping latency heatmap, readable scan/stop buttons, horizontal sc…
c6fcec1 
…roll

- Color Avg/Min/Max/Last cells green->red by latency threshold.
- Scan/Stop buttons: bold 13px, near-black text for contrast.
- Fixed column widths + DataGrid HorizontalScrollBarVisibility=Auto so a
  bottom scrollbar appears when the table is narrower than its columns;
  fix slim scrollbar direction for horizontal orientation.
@wbgcoding
feat: editable subnet field, dark title bar, darker settings
9079a97 
- Header subnet TextBox + Setzen: overrides auto-detect (ManualSubnet);
  prefilled with detected /24 after a scan.
- Dark native title bar via DWM immersive-dark-mode (MainWindow + Settings)
  so window chrome matches the app.
- Settings tab content darker (Bg + surface border) instead of light BgAlt.
@wbgcoding
fix: prefill subnet field with detected network, make text visible
7c96428 
- Detect current /24 at startup and write it into the header subnet box.
- TextBox: explicit foreground + VerticalContentAlignment=Center; template
  content host stretches so entered text is no longer clipped/invisible.
wbgcoding and others added 23 commits June 6, 2026 10:02
@wbgcoding
feat: known devices appear instantly at scan start
b113777 
The known-devices database was written but never read back. At scan
start the engine is now preloaded with the stored devices of the
current network (matched via gateway MAC): rows appear immediately with
their saved hostname and MAC. Stored values use the weakest resolver
rank, so every live result (ARP/DNS/mDNS/NetBIOS) replaces them during
the run.
@wbgcoding
fix: settings crashed after over-aggressive assembly stripping
b155f71 
Opening the settings loaded the ScrollViewer theme template, whose
CommandConverter resolves the WPF presentation xmlns — which eagerly
loads every assembly registered on it, including the stripped Ribbon
(System.Windows.Controls.Ribbon FileNotFoundException). Ribbon,
ReachFramework, System.Printing and WindowsFormsIntegration are back in
the bundle; only the standalone WinForms/VB/Drawing assemblies stay
stripped (56.1 MB, still -8.4 MB).

The global error handler now writes the full exception chain to
error.log next to the exe, so future field reports carry a stack trace.
@wbgcoding
feat: burst-ping freshly dropped devices to recover short dropouts
1abaedd 
When a device flips online -> offline during analysis, the engine now
probes it five more times at 500 ms intervals; the first reply puts it
straight back online. Guarded per device, stops early when another path
already recovered it, and skips failed probes in the ping counters.
@wbgcoding
release: version 2.5
bd30a0a 
End-user changelog for 2.5, refreshed README feature list, version bump.
Audit pass: TXT export hides Unknown sentinels and failed last pings
like the UI does, overrides file written as explicit UTF-8, error.log
and overrides.conf added to .gitignore.
@wbgcoding
feat: average-latency mini graph under each network in the sidebar
d041eb6 
Each network entry now shows a small history graph of its average
latency, in the same style as the internet graph including min/max
labels and time tick markers. Graph math moved into a shared
GraphSeries helper used by both the code-rendered graphs and the
template-bound network graphs. New 'show network graphs' toggle in the
Graphs settings (network_graphs_enabled, default on); the existing
master toggle and time window apply too.
@wbgcoding
feat: conf path field shows the full file, defaults move next to the exe
75736fd 
- The configuration-file setting now shows and accepts the complete file
  path (Browse uses a file dialog); only the folder is stored, the file
  name stays ip_scanner.conf.
- Default locations for the database (./scanner.db) and the conf (./)
  are next to the program file instead of the scans folder. Reports
  keep ./Scans. Existing installs are picked up via a legacy fallback
  that still finds ./Scans/ip_scanner.conf.
@wbgcoding
feat: up to 10 device latency graphs, paths normalize to ./ form
80c5a0f 
- The latency-history section is now a list of graphs: a + button at
  the bottom right adds another graph with its own device selector
  (up to 10), X removes one (at least one stays). Graphs are
  template-bound DeviceGraphViewModels sharing the GraphSeries math;
  sources live in one ObservableCollection with stable instances so
  open dropdowns and selections survive label updates.
- Paths picked or typed inside the working directory are stored and
  shown relative (./scanner.db, ./Scans, ./ip_scanner.conf).
@wbgcoding
ui: relative paths use Windows-style .\ instead of ./
5a68edc
@wbgcoding
ui: plus button hides at the graph limit, pinned devices sort first i…
3bf1169 
…n graph sources, paths display and persist as .

- The add-graph button collapses instead of disabling once 10 graphs
  exist.
- Graph source dropdowns mirror the table order (pinned first, then by
  IP) using ObservableCollection.Move so selections stay intact.
- Loaded configs normalize all stored paths to Windows-style relative
  form, so the settings fields and the conf file consistently show .  even for files written by older versions.
@wbgcoding
ui: badge and bubble text auto-contrast on dark colors
58a77c2 
Palette.ContrastOn picks white or dark text from the background's
luminance; the network badge and the settings bubbles use it so names
stay readable on any chosen color.
@wbgcoding
ux: reset to defaults requires a second click on a red confirm button
6241be4 
First click turns the reset button red asking 'Alle Einstellungen
loeschen?'; the second click within four seconds performs the reset,
otherwise the button disarms (also when the settings close).
@wbgcoding
fix: logo spin-up no longer stutters under scan load
4295357 
dt is capped at ~2 frames so dropped frames briefly slow the rotation
instead of jumping the angle; ramp slightly softened for a gentler
spin-up from the current position.
@wbgcoding
perf: logo spins on its own composition thread, graphs compute off th…
2f38538 
…e UI thread

- SpinningLogo control renders via HostVisual/VisualTarget on a
  dedicated background STA thread with its own dispatcher: the rotation
  and glow stay perfectly smooth regardless of UI-thread load during
  scans. Shut down via BeginInvokeShutdown on window close; the thread
  is a background thread so it can never hang the process.
- Graph sampling and geometry now run on a System.Threading.Timer
  worker: GraphSeries freezes the PointCollections so bindings consume
  them cross-thread; only the internet canvas and the source list are
  updated on the UI thread. Snapshot methods with a small lock keep the
  worker safe against collection changes; an Interlocked guard prevents
  overlapping ticks and the timer is disposed on close.
@wbgcoding
ui: graph line keeps clear of the max label at the top
15b2e95
@wbgcoding
release: version 2.6
62dad79 
End-user changelog, README refresh, version bump. Audit pass: sample
list in DeviceGraphViewModel is now lock-guarded (UI clears on source
change while the worker appends). Privacy audit clean, no stale files.
@wbgcoding
fix(scanner): evict stale IP entries when MAC moves to new address
584b397 
Device that changes IP appears twice: old entry from DB preload
plus new live entry — same MAC, different IP keys in _devices.

MAC->IP index in ScanEngine tracks which IP owns each MAC. When
MAC is set (Preload or enrichment), any offline entry at the old
IP is evicted and DeviceRemoved fires. MainViewModel removes the
row from the visible list and dirty set.
@wbgcoding
fix: resolve code-audit findings across scan, UI and data layers
3705dde 
Bugs / concurrency:
- ScanEngine recheck loop used the throwing dictionary indexer, which
  could crash the scan when a concurrent MAC-move eviction removed the
  entry; switch to TryGetValue.
- Serialize OnDeviceUpdated's device-field writes under lock(d) so they
  no longer race the engine's enrichment writers.
- mDNS reverse query now derives the four octets from the parsed bytes
  instead of a raw string split (abbreviated forms no longer throw).
- Analysis ping interval awaits instead of blocking a pool thread.
- SpinningLogo dispatcher handoff made volatile with a shutdown guard.
- Observe the fire-and-forget internet-ping task.

Performance:
- Apply pin/override/self metadata once at row creation, not per ping.
- UpdateProgress: reuse the engine snapshot and bucket devices per
  network in a single pass; single-pass totals average.
- GraphSeries.Compute and DeviceGrouper.GroupKey drop per-call LINQ
  allocations.

Layout:
- Totals row split into two grid columns so the threads label can no
  longer overlap the totals.
- Hostname column trims with an ellipsis and a full-value tooltip.
- Center header column gets a MinWidth so the bars stay usable.

Cleanup:
- Single hex-color validator and color palette/swatches in Core.
- HostsPerSubnet constant replaces the magic 254.
- Shared NIC enumeration helper in NetworkDetector.
- Generated config file comments rewritten in English.
- Removed dead Ipv4.PrefixToMask and stale/duplicate/German comments.
@wbgcoding
feat: check GitHub for updates on startup and self-replace the exe
bd3ffd2 
Adds UpdateService: queries the GitHub Releases API for the latest tag,
and when it is newer than the running build offers a Yes/No dialog naming
the new and installed versions. On confirmation it downloads the .exe
asset and launches a small updater script that waits for the app to exit,
swaps the single-file exe and relaunches it.

The check runs alongside the startup sweep and is silent when up to date
or offline. It can be disabled with check_for_updates = false in the conf.

Bumps version to 2.7.0.
@wbgcoding
feat: per-device graphs, 10 languages, offline-DB toggle (v2.8)
7b16b0c 
- Expandable per-row latency graph: click a device's Ø/Min/Max/Last cell to
  show its ping history under the row (full width, time ticks, follows the
  configured graph window); optional auto-open for pinned devices.
- Header "Offline (DB)" toggle to hide/show offline known devices from the DB.
- UI expanded from 2 to 10 languages (es, fr, zh, hi, ar, pt, ru, ja added)
  via embedded per-language JSON keyed by the English string; instant switch,
  Windows-language auto-detect.
- MAC resolution now covers additional local subnets (full ARP-table lookup).
- Export buttons moved above the networks; device/ping progress bars share a
  left edge across languages; table no longer shifts when the scrollbar shows.
- Row graphs open instantly with full history; row-graph and Loc thread-safety
  tightened; dead code removed.
@wbgcoding
Replace dashes in docs and sources
a250ad9
@wbgcoding
Add security policy, OpenSSF Scorecard and dependency review
939a88e
@wbgcoding
Add Dependabot version updates
5a74ad4
@dependabot
Bump Microsoft.Data.Sqlite from 8.0.0 to 10.0.14
2040727 
---
updated-dependencies:
- dependency-name: Microsoft.Data.Sqlite
  dependency-version: 10.0.14
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added .NET Pull requests that update .NET code dependencies Pull requests that update a dependency file labels Oct 29, 2026
@dependabot dependabot Bot mentioned this pull request Oct 29, 2026
Closed
@wbgcoding wbgcoding closed this Oct 29, 2026
@dependabot @github

dependabot Bot commented on behalf of github Oct 29, 2026

Copy link
Copy Markdown
Author

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot
dependabot Bot deleted the dependabot/nuget/src/IpScanner/Microsoft.Data.Sqlite-10.0.14 branch October 29, 2026 20:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file .NET Pull requests that update .NET code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@wbgcoding