-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Maui Nightly builds #7653
Comments
There already is, https://github.com/dotnet/maui/blob/main/.github/DEVELOPMENT.md Green Main builds should already be uploaded. If you run the workload steps from the Development guide, you can install them. It's also (technically) possible to download and install PR builds and install them, although that requires some "deep knowledge" (Setting up local nuget feeds and rollback files) and light hackery of the workload system. That stuff could be documented. But yeah, if your fix landed in main, you should be able to follow the Develoment guide and run it. |
@drasticactions You are a hero, thank you so much. One last question, how do I uninstall the nightly workload? I just quickly scrolled through the page you gave me but couldn't find it. |
If you use the rollback file for the GA build, that will roll it back
|
When I build execute
inside of <PATH_TO_MAUI>/maui/bin/dotnet, I get
|
Same, but that's not important because if I run VS (2022 preview) and debug the app it already uses the nightly build. Also |
Description
I would like to be able to install nightly builds based on the main branch. I had a couple of issues where it has been said "Works fine on main" and I was not able to verify. Also I reported a couple of issues which have been fixed by a PR but no maui update has been released and I am stuck.
It would be nice to get a nightly installers just like the .NET runtime repo
Public API Changes
No API change
Intended Use-Case
We are no longer stuck in development because we have to wait for a new MAUI release. Also we are able to confirm if a bug also happens in main branch or not.
The text was updated successfully, but these errors were encountered: