Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
31 changes: 31 additions & 0 deletions DEVELOPMENT.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,36 @@
# Development

## Debugging

Visual Studio is the preferred IDE: open `Seeker.sln`, select a Configuration (Debug / Debug Mock),
Debug > Start Debugging (F5) / Start Without Debugging (Ctrl+F5).

CLI equivalents:

```powershell
# build + fast-deploy
dotnet build .\Seeker\Seeker.csproj -p:AndroidKeyStore=false -c "Debug Mock" -t:Install

# build + fast-deploy + launch
dotnet build .\Seeker\Seeker.csproj -p:AndroidKeyStore=false -c "Debug Mock" -t:Run

# build standalone + deploy
dotnet publish .\Seeker\Seeker.csproj -p:AndroidKeyStore=false -p:EmbedAssembliesIntoApk=true -c "Debug Mock" -f net9.0-android

# view app logs
adb logcat --pid=(adb shell pidof com.companyname.andriodapp1)
```

Notes:

- Debug configs use fast deployment by default so they are not standalone apks.
Use `-p:EmbedAssembliesIntoApk=true` for standalone apks.
- `Debug` uses the real `SoulseekClient` and logs into the live
Soulseek server. `Debug Mock` uses an in process mock server `MockSoulseekClient` — search,
download, upload behavior can be controlled via keywords (`n:N`, `t:N`, `speed:N`, `failat:N`, `stall`, etc).



## Publishing

### One-shot release script
Expand Down
Loading