Native .NET & Mobile App Dev on Aurora DX (Dedicated Rig - No Distrobox)

[AlasdairDev]

Yo. I’m running Aurora DX and I'm currently dialing in this laptop as a dedicated programming machine. Since this is my primary dev rig, I’m moving away from the container-first/Distrobox approach—I want native performance and zero friction for my main workflow.

I’m focused on Application Development, specifically C# / .NET and Android, using SQLite for local storage. Coming from a full Visual Studio background on Windows, I’m looking for the best professional-grade environment on Linux that feels production-ready and snappy.

The biggest priority is the Android Emulator / Mobile Preview. I need it running with full hardware acceleration (KVM) so it’s actually usable for testing. I don't want to mess around with nested virtualization or container overhead for this. I'm also trying to avoid the full Android Studio bloat if there's a leaner way to handle the SDKs and emulator.

Since I'm opting out of Distrobox for this build to keep things native, I have two main questions:

What setup is actually the "best" for this specific workflow on an atomic base?

How do I install it natively without breaking the immutable design or relying on containers?

I need to know how you guys are handling the .NET SDK workloads, the Android CLI tools (for the emulator/ADB), and which IDE handles this mobile stack seamlessly. I’m a BSIT student and I need this rig to be as efficient as possible for heavy project work.

Appreciate the insight.

[repires]

AI Generated: ask.projectbluefin.io

https://app.dosu.dev/e3630b91-3a35-46b9-a8d3-b0c1b3ef6331/ask?thread=dac20c97-5e26-4c77-b415-842953dd62a5

Hey! Good news — your Aurora DX setup is actually well-suited for this workflow. Here's the play-by-play:

Important framing first: On an atomic OS, "native" doesn't mean dnf install — it means Homebrew for CLI tools and Flatpak for GUI apps. Both install to userspace/sandboxed locations and never touch the immutable /usr. This is the native, sanctioned path [1]. Forget rpm-ostree install — layering is locked by default and you don't want to go there.

---

1. .NET SDK — Install via Homebrew (it's already on your system):

brew install dotnet

Done. Lives in your Homebrew prefix, no system mutation.

2. Android SDK + Emulator (without Android Studio bloat) — The SDK installs entirely in your home directory, which is perfect for an immutable OS:

# Download cmdline-tools from developer.android.com, then:
export ANDROID_HOME=$HOME/Android/Sdk
export PATH=$PATH:$ANDROID_HOME/cmdline-tools/latest/bin:$ANDROID_HOME/emulator:$ANDROID_HOME/platform-tools

sdkmanager "platform-tools" "emulator" "platforms;android-34" "system-images;android-34;google_apis;x86_64"
avdmanager create avd -n TestDevice -k "system-images;android-34;google_apis;x86_64"
emulator -avd TestDevice

Add those export lines to your ~/.bashrc or ~/.zshrc to persist them.

3. KVM / Hardware Acceleration — Already handled. Aurora DX ships with QEMU, libvirt, and KVM tooling pre-installed, and the bluefin-dx-groups service auto-adds your user to libvirt, kvm, etc. Just make sure you've run:

ujust dx-group

Then reboot. Verify with ls -la /dev/kvm and groups. The emulator will pick up KVM automatically — no nested virt, no container overhead, bare-metal acceleration.

4. IDE — JetBrains Rider is your best bet for C#/.NET + Android on Linux. It's the closest thing to full Visual Studio and handles .NET MAUI/Xamarin + Android projects natively. Install via:

ujust bbrew   # select the "ide" bundle — includes JetBrains Toolbox

Then install Rider from JetBrains Toolbox. It installs to ~/.local/share/JetBrains/ — fully userspace. Point it at your ANDROID_HOME and .NET SDK and you're set.

Alternatively, VS Code with the C# Dev Kit + Android extensions is lighter but less integrated for the mobile preview workflow.

---

TL;DR install order:

1. ujust dx-group → reboot
2. brew install dotnet
3. Download Android cmdline-tools to ~/Android/Sdk/, run sdkmanager to grab emulator + platform tools
4. ujust bbrew → install IDE bundle → install Rider from Toolbox
5. Set ANDROID_HOME in your shell profile, point Rider at it

Everything lives in $HOME or Homebrew's prefix. Zero system mutation, full KVM acceleration, no containers in the loop. This is exactly how the OS is designed to be used for dev work.

[AlasdairDev]

hello about this

5.Set ANDROID_HOME in your shell profile, point Rider at it

is this on rider settings exactly like on vscode when puting the path file?

[repires]

You can just chat with dosu. I agree with @renner0e setup a devcontainer or distrobox will make your life easier.

Dosu answer:
Yeah, similar idea but the location in Rider is different from VS Code. Two things to set up:

Android SDK path — In Rider:

1. Ctrl+Alt+S to open Settings
2. Go to Languages & Frameworks → Xamarin
3. Set the Android SDK Path field to your SDK location (e.g. ~/Android/Sdk)

[1]

It's under the Xamarin section because Rider handles Android through Xamarin/MAUI tooling — a bit different from VS Code where you'd set it in a more generic settings field.

.NET SDK — You don't need to manually configure this one. Rider auto-detects the .NET CLI path. If you want to verify or override it, it's at Settings → Build, Execution, Deployment → Toolset and Build → .NET CLI executable path.

Pro tip: Still set ANDROID_HOME in your shell profile (~/.bashrc or ~/.zshrc) regardless — Rider will often pick it up as a fallback, and you'll need it for command-line tools like adb and emulator anyway:

export ANDROID_HOME=$HOME/Android/Sdk
export PATH=$PATH:$ANDROID_HOME/platform-tools:$ANDROID_HOME/emulator

[renner0e]

I’m moving away from the container-first/Distrobox approach

you'll have a hard time here if you don't want to use containers of any kind