Selfhosting machine #17184

Closed
opened 2026-01-31 05:34:38 +00:00 by claunia · 4 comments
Owner

Originally created by @rvc11main on GitHub (Apr 7, 2022).

Welcome to my issue!

The selfhosting machine

If you change the build number using the Registry Editor, then you will selfhost builds.


What build number would you want?

  • Recommended: 22601
  • Nickel builds at Microsoft.UI.Xaml Issue: 22596, 22574
  • The only build that is on the conhost on the closed issue: 22590
Originally created by @rvc11main on GitHub (Apr 7, 2022). Welcome to my issue! ## The selfhosting machine If you change the build number using the Registry Editor, then you will _selfhost_ builds. <br/> _What_ build number would you want? - [ ] Recommended: 22601 - [ ] Nickel builds at Microsoft.UI.Xaml Issue: 22596, 22574 - [ ] The only build that is on the conhost on the closed issue: 22590
claunia added the Needs-TriageNeeds-Tag-Fix labels 2026-01-31 05:34:38 +00:00
Author
Owner

@rvc11main commented on GitHub (Apr 7, 2022):

You are grumpy at closing!

@rvc11main commented on GitHub (Apr 7, 2022): You are grumpy at closing!
Author
Owner

@zadjii-msft commented on GitHub (Apr 7, 2022):

What? I honestly have no idea what you're asking here. If you can clarify, we can reopen. You also don't need to keep filing multiple issues for what seems to be the same topic of discussion.

Just changing the build number in the registry isn't going to actually change anything about the actual binaries you're running. I would highly recommend not doing that.

@zadjii-msft commented on GitHub (Apr 7, 2022): What? I honestly have no idea what you're asking here. If you can clarify, we can reopen. You also don't need to keep filing multiple issues for what seems to be the same topic of discussion. Just changing the build number in the registry isn't going to actually change anything about the actual binaries you're running. I would highly recommend not doing that.
Author
Owner

@rvc11main commented on GitHub (Apr 8, 2022):

No, you stop CLOSING!!!!!!!!!!!!!!!!!!!!!!!!!!!!

@rvc11main commented on GitHub (Apr 8, 2022): No, you stop CLOSING!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Author
Owner

@rvc11main commented on GitHub (Apr 8, 2022):

What? I honestly have no idea what you're asking here. If you can clarify, we can reopen. You also don't need to keep filing multiple issues for what seems to be the same topic of discussion.

Just changing the build number in the registry isn't going to actually change anything about the actual binaries you're running.

I must create Microsoft software from Visual Studio 2022, and I will selfhost the builds.

I would highly recommend not doing that.

No, I would highly recommend ViVeTool for new features.
Note: Build 22579.100 has the tabbed browsing feature.

@rvc11main commented on GitHub (Apr 8, 2022): > What? I honestly have no idea what you're asking here. If you can clarify, we can reopen. You also don't need to keep filing multiple issues for what seems to be the same topic of discussion. > > Just changing the build number in the registry isn't going to actually change anything about the actual binaries you're running. I must create Microsoft software from **Visual Studio 2022**, and I will _selfhost_ the builds. > I would highly recommend not doing that. No, I would highly recommend [ViVeTool](https://github.com/thebookisclosed/ViVe/releases) for new features. **Note:** Build 22579.100 has the tabbed browsing feature.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#17184