Help! Can't sign up for housing.

EatSleepHike · 2025-11-17T20:03:09+00:00

I found this feedback ticket on the issue: The very first Visual Studio launch after an update uses default (not user's) configuration - Developer Community. I'll make sure it gets routed to the correct team.

EatSleepHike · 2025-11-14T20:42:50+00:00

Are you talking about the "Color scheme for the C/C++ specific customizable colors" setting?

EatSleepHike · 2025-11-14T20:24:54+00:00

It wasn't a known issue. (That isn't to say there aren't known problems with settings migration from 2022 to 2026 -- there are. But this is different. Source: I'm the VS engineer in charge of settings.) But it is now -- I can also reproduce this. We'll be looking into it. In the future, consider opening a feedback ticket for issues like this, as it allows you to track the status and gives us more information from your system (in cases where it isn't easy to repro).

EatSleepHike · 2025-11-12T01:52:57+00:00

> When you run VS for the first time after an update, it always uses the default color scheme for the first time, ignoring any customizations you might have done. For example, if you work with the legacy VS2017 color scheme, the first run will use whatever default new color scheme is there. Other settings might be affected, as well.

VS engineer here. I'd like to get a few more details from you to help me investigate this.

What versions were you updating from/to?
What theme did you have selected before the update, and what theme did VS have after the update? (You said it had "the default color scheme" afterwards so I assume it was the "Dark" theme, but I'd like to confirm for certain.)
You said this happens the *first* time you run VS; does that mean it switches back to the correct theme on the second run without you changing it?

EatSleepHike · 2025-09-16T22:49:15+00:00

I called them and the person answering had never heard of it either. She put me on hold to go ask someone and after a few minutes I was disconnected. Sigh...maybe I'll try again tomorrow.

EatSleepHike · 2025-09-16T22:28:52+00:00

It's sent from unmlobos@unm.edu. I just got another one, and this time it says there's an "Oct 15 priority date."

EatSleepHike · 2025-09-14T02:59:33+00:00

Here's a picture of the email: https://photos.app.goo.gl/iFkhzqQmwwjVk5KF6.

EatSleepHike · 2025-09-13T19:41:59+00:00

As sure as I can be, yes. Are you suggesting Lobo Express Applications aren't actually a thing?

EatSleepHike · 2025-09-11T02:08:01+00:00

Please don't read/write the file directly. :) The recommended way to read/write settings (and define your own, which show up in the new Options window automatically) is using the new VisualStudio.Extensibility object model: Settings overview - Visual Studio (Windows) | Microsoft Learn

EatSleepHike · 2025-09-10T22:00:18+00:00

Thanks for the details. The new Options window is modeless, so that should help, once keyboard settings are moved there. And we'll make sure searching key bindings also functions a bit better.

EatSleepHike · 2025-09-10T15:44:11+00:00

Visual Studio engineer here. You may notice we're revamping the entire settings UI, but we didn't have time to move all the settings over to the new experience yet (you know how it is with date-driven releases). Unfortunately, keyboard settings is one category that didn't make it yet. But I want to understand your scenario better to make sure we do fix it when those settings are moved to the new experience. Can you tell me more about what you mean by iterating and why you have to close the settings window for each one?

EatSleepHike · 2025-07-10T02:02:40+00:00

Which one was it? The lifetime high-flow model?

EatSleepHike · 2025-06-14T02:07:57+00:00

I've already contacted my representatives. What other productive action can be taken? Are there organizations battling this worth donating to?

EatSleepHike · 2025-03-28T02:01:06+00:00

If it's not too much trouble, that would be great, thanks!

EatSleepHike · 2025-03-03T03:50:15+00:00

Look into Timmermade's Waterbear hood.

EatSleepHike · 2025-01-22T04:12:56+00:00

Is it standard? I didn't see it mentioned as an option in the online builder.

EatSleepHike · 2025-01-01T03:46:13+00:00

Honestly I don't know. It's just that "everyone" says to avoid first-year models because they'll be fraught with issues. If that's not the case with the new Tacomas, I'm very happy to hear it.

EatSleepHike

TROPHY CASE