Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

The demos' Windows apps aren't ready for WinGet and the Microsoft Store

Open
#14,055 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@yasmoradi is already working on this.

Since Oct 21, 2026.

  • #14056 by @yasmoradi — open

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
csharp, wasm
Domain
desktop, release

Research direction

The issue names the Windows apps for AdminPanel, Sales, Todo, and BlazorUI, their CD, and their Setup.exe files, but gives no paths or test names. Start by tracing the Windows packaging and CD configuration for those apps. Done means each release has a stable installer link, all executable files are signed, publisher names use BitPlatform, and new versions reach WinGet and the Microsoft Store.

Written by the indexing model from the issue text.

Description

We want the Windows apps of AdminPanel, Sales, Todo and the BlazorUI demo on WinGet and in the Microsoft Store, and their new versions sent to both by the CD the way the Android and iOS apps reach Google Play and the App Store. Both take a link to the installer and need the file behind it to never change, and the Store needs every executable file of the app signed. Today:

  • Each app has a single Setup.exe URL that every CD overwrites.
  • The CD signs only the apps' .exe files, not their .dll files.
  • Nothing sends a new version to WinGet or the Store.
  • The apps name their package id, such as TodoSample.Client.Windows, as their publisher, in Add/Remove Programs and in their executables' company name, instead of BitPlatform, the name their installers are signed with.
Dominant language
C#
Stars
1.4k
Forks
264
Avg merge
14h 17m
Merged PRs (30d)
327

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bitfoundation/bitplatform

All issues in bitfoundation/bitplatform

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.