Visual Studio WTfs
-
My cow-orkers decided that we absolutely need to upgrade to VS2019. It's so much faster and blah blah blah. Well, here we are.
So I edited an XML file which is stored on a UNC path \\Somewhere\folder\abc.xml in VS2019, because I prefer the VS editor over Notepad++. Saved it, closed it.
Next, I did bad things (TM): I renamed "folder" to "folder2", and "folder1" to "folder" - also here, a file "abc.xml" does exist. Now dragged and dropped it into the VS2019 editor.
Voilà: VS2019 shows me the previous file abc.xml, and immediately marks it as changed.
Now I had to edit it in Notepad++.
Thank you, Microsoft!
-
@BernieTheBernie said in Visual Studio WTfs:
My cow-orkers decided that we absolutely need to upgrade to VS2019. It's so much faster and blah blah blah. Well, here we are.
So I edited an XML file which is stored on a UNC path \\Somewhere\folder\abc.xml in VS2019, because I prefer the VS editor over Notepad++. Saved it, closed it.
Next, I did bad things (TM): I renamed "folder" to "folder2", and "folder1" to "folder" - also here, a file "abc.xml" does exist. Now dragged and dropped it into the VS2019 editor.
Voilà: VS2019 shows me the previous file abc.xml, and immediately marks it as changed.
Now I had to edit it in Notepad++.
Thank you, Microsoft!Remember you do not really drag and drop files... you drag an drop their location... cache comes into play.
-
@TheCPUWizard said in Visual Studio WTfs:
\\Somewhere\folder\abc.xml
cache comes into play.It looks like SMB also comes into play.
-
@BernieTheBernie said in Visual Studio WTfs:
upgrade to VS2019. It's so much faster
Also another WTF, may not apply depending on the version: VS2008 project files can support shortcuts/symlinks but only if they're defined by a text editor because the UI cannot (that I've seen) actually create a redirect.
-
-
@error said in Visual Studio WTfs:
@Zenith said in Visual Studio WTfs:
VS2008 project files
You really are living in the 2000s.
Aren't we all, for the next 980 years?
-
@Zecc said in Visual Studio WTfs:
@error said in Visual Studio WTfs:
@Zenith said in Visual Studio WTfs:
VS2008 project files
You really are living in the 2000s.
Aren't we all, for the next 980 years?
No, I doubt we'll be living in 980 years.
-
@error said in Visual Studio WTfs:
@Zecc said in Visual Studio WTfs:
@error said in Visual Studio WTfs:
@Zenith said in Visual Studio WTfs:
VS2008 project files
You really are living in the 2000s.
Aren't we all, for the next 980 years?
No, I doubt we'll be living in 980 years.
Have this:
-
@error said in Visual Studio WTfs:
@Zecc said in Visual Studio WTfs:
Aren't we all, for the next 980 years?
No, I doubt we'll be living in 980 years.
I was going to say I meant "we" as a species, not as individuals; but the way
thinksthings are heading, who knows.
-
There's too much sugar in Visual Studio
***
Ah hell, it ain't the same without :@levicki:
-
@error I'd like to move but not being Indian or able to afford to live on $50K limit the opportunities to do so.
-
Today, in TIL (VS2022)...
Clicking Ctrl twice toggles 'hints' in the editor. I was wondering what the hell I had done...
vs
-
@dcon said in Visual Studio WTfs:
Clicking Ctrl twice
It's not like it's a key shortcut you'd trigger accidentally, now is it?
It's not like Ctrl is used to trigger most other keyboard shortcuts or to navigate between words.
-
Something happens when pressing Ctrl that turns the mouse pointer from its normal "arrow" shape to a "hand" shape. I think it's indeed related to hints or some sort of navigation. Whatever.
But it's also somehow broken (in VS2017) when I... do something else at the same time? Not sure if it's pressing other keys at the same time (like, I don't know, maybe for some reason I want to press C, or V at the same time as Ctrl?), or moving the mouse, or clicking, and of course now that I want to test I can't reproduce.
The result is that when that happens, the pointer stays in this "hand" state after releasing Ctrl, which subtly affect mouse behaviour (e.g. single-click does full word selection). Thankfully I just need to press/release Ctrl to fix it, so it's not too annoying, just a little bit annoying...
-
@remi said in Visual Studio WTfs:
Something happens when pressing Ctrl that turns the mouse pointer from its normal "arrow" shape to a "hand" shape. I think it's indeed related to hints or some sort of navigation. Whatever.
It turns into a "hand" shape because, besides triggering word select, it also will navigate to recognized URLs instead of the non-Ctrl behavior of letting you edit them.
-
Status: Accidentally asked File Explorer to open a small JSON file with Visual Studio.
Been waiting about two minutes so far.
-
@Zecc don't buy land.
-
Visual Studio 2022 Community Edition on Windows 11 is my "new friend" (
). I decided to write a WPF app with .Net 4.8 (to be run on Windows 7 later on). I wanted to use a Mainmethod. Did that before several times, so just do like in the past:- remove the startup from App.xaml
- add a [STAThread] static void Main to App.xaml.cs
No, Bernie, you cannot do that anymore. Despite the old app where you did so still compiles and runs fine on VS 2022 here. But with a freshly created app,
!
Instead, add a fileProgram.cs, add there yourMain, then select that in the project properties. It worx.
-
Well, then, I decided to use my BernieStyle.xaml. Included that in App.xaml as ususal. Styled a button on MainWindow.xaml, and it looks fine in the editor.
OK, compile it and start the program.
Error: Cannot find resource BernieButton.
It was found in the editor, but now during runtime it just fucks up?
And btw, VS just crashed a couple of times too...
-
@BernieTheBernie said in Visual Studio WTfs:
Visual Studio 2022
Windows 11
WPF
.Net 4.8
xaml
Oh come on, you hurt yourself on purpose, just admit it.
-
@MrL said in Visual Studio WTfs:
@BernieTheBernie said in Visual Studio WTfs:
Visual Studio 2022
Windows 11
WPF
.Net 4.8
xaml
Oh come on, you hurt yourself on purpose, just admit it.
There’s nothing wrong with starting a new project on a 15 year old framework version that’s on deck to lose security updates at any time. Just means you’ll be shooting against a stationary target instead of something that might get new
features and now need you to change things after that update.
-
@izzion said in Visual Studio WTfs:
@MrL said in Visual Studio WTfs:
@BernieTheBernie said in Visual Studio WTfs:
Visual Studio 2022
Windows 11
WPF
.Net 4.8
xaml
Oh come on, you hurt yourself on purpose, just admit it.
There’s nothing wrong with starting a new project on a 15 year old framework version that’s on deck to lose security updates at any time. Just means you’ll be shooting against a stationary target instead of something that might get new
features and now need you to change things after that update.What I meant is that all the things I listed are known problem generators. If you aim for synergy of shit, shit you will get in abundance.
-
@izzion said in Visual Studio WTfs:
There’s nothing wrong with starting a new project on a 15 year old framework version that’s on deck to lose security updates at any time.
I believe there's no official support end date for the Framework.
-
@Applied-Mediocrity said in Visual Studio WTfs:
@izzion said in Visual Studio WTfs:
There’s nothing wrong with starting a new project on a 15 year old framework version that’s on deck to lose security updates at any time.
I believe there's no official support end date for the Framework.I wouldn't want to be on either side of the bet that Framework 4.8 is going to be available in Windows 12.
-
@izzion Probably not OOBE, yes
But I'd gravitate towards "available", which still brings us, IIRC, late 2026, when the Server 2022 support runs out.
-
@Applied-Mediocrity said in Visual Studio WTfs:
@izzion Probably not OOBE, yes
But I'd gravitate towards "available", which still brings us, IIRC, late 2026, when the Server 2022 support runs out.
-
@izzion said in Visual Studio WTfs:
the bet that Framework 4.8 is going to be available in Windows 12.
I use that version because it still runs on Windows 7.
So I do not at all care for Windows 12 now.
If I really would come to the conclusion to run it on Windows 12 or later, I may have to re-compile after changing the target version. Upto now, that worked in all cases (even from Framework 1.1 to .Net 8).
-
@BernieTheBernie said in Visual Studio WTfs:
@izzion said in Visual Studio WTfs:
the bet that Framework 4.8 is going to be available in Windows 12.
I use that version because it still runs on Windows 7.
So I do not at all care for Windows 12 now.
If I really would come to the conclusion to run it on Windows 12 or later, I may have to re-compile after changing the target version. Upto now, that worked in all cases (even from Framework 1.1 to .Net 8).
Windows 7 does not prevent you from running a supported, current LTS version of .NET
PrinceCore
core/release-notes/6.0/supported-os.md at main · dotnet/core
.NET news, announcements, release notes, and more! - dotnet/core
ETA: And having taken projects from Framework 4.8 to Core 3.1, you're going to be way better off for future support to start on .NET Core 6 now. The marketing people would have you believe that .NET 5 actually had better support for just updating the target build when moving off of Framework 4.x, but there are still a significant number of breaking changes that can trip you up, more so if your app is in the desktop UI space.
-
@izzion said in Visual Studio WTfs:
@BernieTheBernie said in Visual Studio WTfs:
@izzion said in Visual Studio WTfs:
the bet that Framework 4.8 is going to be available in Windows 12.
I use that version because it still runs on Windows 7.
So I do not at all care for Windows 12 now.
If I really would come to the conclusion to run it on Windows 12 or later, I may have to re-compile after changing the target version. Upto now, that worked in all cases (even from Framework 1.1 to .Net 8).
Windows 7 does not prevent you from running a supported, current LTS version of .NET
PrinceCore
core/release-notes/6.0/supported-os.md at main · dotnet/core
.NET news, announcements, release notes, and more! - dotnet/core
Anyone still using Windows 7 isn't really concerned about pesky things like supported versions.
-
@MrL said in Visual Studio WTfs:
If you aim for synergy of shit,
shitBest Practice you will get in abundance.Fixed.
-
@loopback0 said in Visual Studio WTfs:
@izzion said in Visual Studio WTfs:
@BernieTheBernie said in Visual Studio WTfs:
@izzion said in Visual Studio WTfs:
the bet that Framework 4.8 is going to be available in Windows 12.
I use that version because it still runs on Windows 7.
So I do not at all care for Windows 12 now.
If I really would come to the conclusion to run it on Windows 12 or later, I may have to re-compile after changing the target version. Upto now, that worked in all cases (even from Framework 1.1 to .Net 8).
Windows 7 does not prevent you from running a supported, current LTS version of .NET
PrinceCore
core/release-notes/6.0/supported-os.md at main · dotnet/core
.NET news, announcements, release notes, and more! - dotnet/core
Anyone still using Windows 7 isn't really concerned about pesky things like supported versions.
Having been effectively a mercenary maintenance coder for most of the last 2 decades, I figured I'd put that out there for future-Bernie or the poor unnamed slob that has to update this application later
-
@MrL said in Visual Studio WTfs:
@BernieTheBernie said in Visual Studio WTfs:
Visual Studio 2022
Windows 11
WPF
.Net 4.8
xamlOh come on, you hurt yourself on purpose, just admit it.
Yeah, Windows Forms would have been a much better choice.
-
Once again,
y performance struck me. I wanted to debug my äpp, and Visual Studio decided to 1>C:\Program Files\Microsoft Visual Studio\2022\Community\MSBuild\Current\Bin\Roslyn\Microsoft.CSharp.Core.targets(84,5): error : Unhandled Exception: System.IO.FileLoadException: Could not load file or assembly 'Microsoft.CodeAnalysis.CSharp, Version=4.8.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The paging file is too small for this operation to complete. (Exception from HRESULT: 0x800705AF)
Vvatt?
The paging file is too small for this operation to complete.
-
@BernieTheBernie Most likely it hit some bug that caused it to try basically the equivalent of
malloc(-1).Usual Microsoft quality. Nothing to see here, move along.
-
@Bulb said in Visual Studio WTfs:
Most likely it hit some bug
Yes, of course: it is running on Windows 11.
-
@izzion said in Visual Studio WTfs:
I wouldn't want to be on either side of the bet that Framework 4.8 is going to be available in Windows 12.
I can fairly confidently bet that it won’t be; if it ships with the OS it’ll be 4.8.1 or later.
(It will be… interesting… if they put .NET Framework 4.x on the standalone-component train like 3.5 but not the VB6 runtime.)
