Windows look/style/appearance in Visual Studio VB

  • Thread starter Thread starter BvU
  • Start date Start date
Click For Summary
The discussion revolves around a user experiencing issues with the appearance of windows in Visual Studio 2022 on Windows 10, specifically noting that the windows do not look as expected. Suggestions include checking the form border style settings, with a mention that changing the style to "None" alters the appearance but does not resolve the issue. The user expresses frustration and considers reinstalling Visual Studio, although they are hesitant due to concerns about potentially worsening the situation. It is noted that while MDI child windows appear correctly, the parent window does not, indicating a specific issue with the parent window's appearance. Despite attempts to troubleshoot, the problem persists.
BvU
Science Advisor
Homework Helper
Messages
16,213
Reaction score
4,925
Embarrassed having to ask: My windows in VS 2022 (on W10) look like

Form1a.webp


when I would like them to look like

Form1.webp


and I can't *&*&* find what caused it and how to get back

Any suggestions where to look ?

##\ ##
 
Technology news on Phys.org
You have the form border style set to single. Try other settings.
1755001694017.webp
 
Thanks for replying. But it's not that easy:

1755010385008.webp

Only one that gives a different picture is "None" (which does what it should do).

##\ ##
 
BvU said:
Only one that gives a different picture is "None" (which does what it should do).
Huh. Well, I'm out of ideas, other than perhaps re-installing VS.
 
Hesitating to do that -- afraid of making things worse -- but probably the only way out.

Funny to see that MDI child windows look as expected, but the parent window doesn't:

1755069771675.webp


formborderstyle of normal windows do follow Sizable/Fixed expectations; only the looks are wrong.

Oh, well...

[edit] No reason to be so pessimistic: download and install over 200 GB in half an hour. But the problem remains as it was... :frown:

[more edit] copy the .exe, .dll, .pdb, deps.json and runtimeconfig.json to another PC and install runtime .Net 8.0 there: still problem !

SO you think the problem sits inside one of those five files.
However: running a .exe from an old project that used to look OK also has the problem.
Makes you think the problem does NOT sit inside one of those five files.

Tried .NET 7 but no difference.

Flabberghasting ! Where to look now ?


##\ ##
 
Last edited:
Learn If you want to write code for Python Machine learning, AI Statistics/data analysis Scientific research Web application servers Some microcontrollers JavaScript/Node JS/TypeScript Web sites Web application servers C# Games (Unity) Consumer applications (Windows) Business applications C++ Games (Unreal Engine) Operating systems, device drivers Microcontrollers/embedded systems Consumer applications (Linux) Some more tips: Do not learn C++ (or any other dialect of C) as a...

Similar threads

  • · Replies 0 ·
Replies
0
Views
2K
Replies
3
Views
1K
  • · Replies 1 ·
Replies
1
Views
675
  • · Replies 16 ·
Replies
16
Views
4K
Replies
7
Views
923
  • · Replies 1 ·
Replies
1
Views
3K
Replies
4
Views
3K
  • · Replies 16 ·
Replies
16
Views
2K
  • · Replies 14 ·
Replies
14
Views
2K
  • · Replies 13 ·
Replies
13
Views
6K