And so it begins...
-
Installed VS2022 on a Win7 VM, and was greeted by a dialog box that stated that I was installing VS2022 onto an unsupported OS. I suspect that VS2025 will not allow you to install onto Win7 at all. EDIT--------------------------------- ATTENTION!!! Read my post again. I am not saying MS has to maintain support for Win7 in Visual Studio. I was merely observing that "support" for installing VS on Win7 would eventually disappear, and that process has started with the warning dialog box that I encountered when installing 2022. Don't bother me with bullsh*t arguments regarding an expectation of MS maintain support for Win7, or that Win10+ "ain't that bad". That's not the point I was even remotely trying to make.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
Installed VS2022 on a Win7 VM, and was greeted by a dialog box that stated that I was installing VS2022 onto an unsupported OS. I suspect that VS2025 will not allow you to install onto Win7 at all. EDIT--------------------------------- ATTENTION!!! Read my post again. I am not saying MS has to maintain support for Win7 in Visual Studio. I was merely observing that "support" for installing VS on Win7 would eventually disappear, and that process has started with the warning dialog box that I encountered when installing 2022. Don't bother me with bullsh*t arguments regarding an expectation of MS maintain support for Win7, or that Win10+ "ain't that bad". That's not the point I was even remotely trying to make.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
Installed VS2022 on a Win7 VM, and was greeted by a dialog box that stated that I was installing VS2022 onto an unsupported OS. I suspect that VS2025 will not allow you to install onto Win7 at all. EDIT--------------------------------- ATTENTION!!! Read my post again. I am not saying MS has to maintain support for Win7 in Visual Studio. I was merely observing that "support" for installing VS on Win7 would eventually disappear, and that process has started with the warning dialog box that I encountered when installing 2022. Don't bother me with bullsh*t arguments regarding an expectation of MS maintain support for Win7, or that Win10+ "ain't that bad". That's not the point I was even remotely trying to make.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013Windows 7 reached EOL more than 2 years ago. Microsoft have enough quality problems in VS as it is now, so adding obsolete operating systems to the test matrix does not sound like an great idea to me. Or are you having the assumption supporting old operating systems is free?
-
Windows 7 reached EOL more than 2 years ago. Microsoft have enough quality problems in VS as it is now, so adding obsolete operating systems to the test matrix does not sound like an great idea to me. Or are you having the assumption supporting old operating systems is free?
lmoelleb wrote:
Windows 7 reached EOL more than 2 years ago.
I've been running Linux with Win7 in a VM for the last six years. I'm perfectly aware of Win7's current status. I choose to do that because anything newer than Win7 sucks big hairy donkey balls. I was just lamenting the fact that my ability to use teh latest/greatest dev tools on my chosen Windows platform is reaching its inevitable end.
lmoelleb wrote:
Microsoft have enough quality problems in VS as it is now, so adding obsolete operating systems to the test matrix does not sound like an great idea to me. Or are you under the strange assumption supporting old operating systems is free?
I'm been programming longer than you've been alive. I'm fully aware of Microsoft's inability to "do the right thing" since the early 80's.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
Yep. I'm glad I'm near retirement, and next year, won't care what happens to/with Visual Studio. On the other hand, I'm a DoD contractor, and we only started using VS2017 last year, so I'm good, I think.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
Installed VS2022 on a Win7 VM, and was greeted by a dialog box that stated that I was installing VS2022 onto an unsupported OS. I suspect that VS2025 will not allow you to install onto Win7 at all. EDIT--------------------------------- ATTENTION!!! Read my post again. I am not saying MS has to maintain support for Win7 in Visual Studio. I was merely observing that "support" for installing VS on Win7 would eventually disappear, and that process has started with the warning dialog box that I encountered when installing 2022. Don't bother me with bullsh*t arguments regarding an expectation of MS maintain support for Win7, or that Win10+ "ain't that bad". That's not the point I was even remotely trying to make.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013#realJSOP wrote:
Win7 VM
:laugh: :laugh:
-
lmoelleb wrote:
Windows 7 reached EOL more than 2 years ago.
I've been running Linux with Win7 in a VM for the last six years. I'm perfectly aware of Win7's current status. I choose to do that because anything newer than Win7 sucks big hairy donkey balls. I was just lamenting the fact that my ability to use teh latest/greatest dev tools on my chosen Windows platform is reaching its inevitable end.
lmoelleb wrote:
Microsoft have enough quality problems in VS as it is now, so adding obsolete operating systems to the test matrix does not sound like an great idea to me. Or are you under the strange assumption supporting old operating systems is free?
I'm been programming longer than you've been alive. I'm fully aware of Microsoft's inability to "do the right thing" since the early 80's.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013Man, you really, really need to retire. :suss:
-
lmoelleb wrote:
Windows 7 reached EOL more than 2 years ago.
I've been running Linux with Win7 in a VM for the last six years. I'm perfectly aware of Win7's current status. I choose to do that because anything newer than Win7 sucks big hairy donkey balls. I was just lamenting the fact that my ability to use teh latest/greatest dev tools on my chosen Windows platform is reaching its inevitable end.
lmoelleb wrote:
Microsoft have enough quality problems in VS as it is now, so adding obsolete operating systems to the test matrix does not sound like an great idea to me. Or are you under the strange assumption supporting old operating systems is free?
I'm been programming longer than you've been alive. I'm fully aware of Microsoft's inability to "do the right thing" since the early 80's.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013 -
Win 7 was the peak of M$ achievement. It's all downhill from there. VS 2017 works quite well under Win 10 - we still use it.
- I would love to change the world, but they won’t give me the source code.
I don't have a problem with Windows 10. I use it for work 8-10 hours a day, 5-6 days a week.
-
Installed VS2022 on a Win7 VM, and was greeted by a dialog box that stated that I was installing VS2022 onto an unsupported OS. I suspect that VS2025 will not allow you to install onto Win7 at all. EDIT--------------------------------- ATTENTION!!! Read my post again. I am not saying MS has to maintain support for Win7 in Visual Studio. I was merely observing that "support" for installing VS on Win7 would eventually disappear, and that process has started with the warning dialog box that I encountered when installing 2022. Don't bother me with bullsh*t arguments regarding an expectation of MS maintain support for Win7, or that Win10+ "ain't that bad". That's not the point I was even remotely trying to make.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013I understand why MS doesn't want to spend resources on testing VS2022 on an O/S that has reached its end of support. Realistically - why should a compiler + debugger not work on Windows 7? Is there any functionality in the IDE that requires APIs not present in Win7? Inquiring minds wish to know!
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- 6079 Smith W.
-
I would suggest you don't use Visual Studio on Mac, it's terrible. I use Rider from Jet brains instead
Every day, thousands of innocent plants are killed by vegetarians. Help end the violence EAT BACON
-
Installed VS2022 on a Win7 VM, and was greeted by a dialog box that stated that I was installing VS2022 onto an unsupported OS. I suspect that VS2025 will not allow you to install onto Win7 at all. EDIT--------------------------------- ATTENTION!!! Read my post again. I am not saying MS has to maintain support for Win7 in Visual Studio. I was merely observing that "support" for installing VS on Win7 would eventually disappear, and that process has started with the warning dialog box that I encountered when installing 2022. Don't bother me with bullsh*t arguments regarding an expectation of MS maintain support for Win7, or that Win10+ "ain't that bad". That's not the point I was even remotely trying to make.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013I finally got rid of my '88 Olds after the door handle broke and there was nothing in Pick-A-Part.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
-
I finally got rid of my '88 Olds after the door handle broke and there was nothing in Pick-A-Part.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
No winter road salt in your neighborhood? I can do about 20 years max before my car underside gets to be structurally deficient. (I'm in Minnesota.)
-
I understand why MS doesn't want to spend resources on testing VS2022 on an O/S that has reached its end of support. Realistically - why should a compiler + debugger not work on Windows 7? Is there any functionality in the IDE that requires APIs not present in Win7? Inquiring minds wish to know!
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- 6079 Smith W.
It will probably work, except MS doesn't want to "support it"; supporting means security patches; which would include "compilers", etc.
Quote:
On average, Windows 7 machines have 0.16 malware files making it not as secure as Windows 10. For home users also Microsoft has officially ended support of Windows 7. Windows 10 is 2x secure as Windows 7. Having 0.07 malware compared to Windows 7. The rate of malware is very less making it more secure.
[9 Differences between Windows 7 and Windows 10](https://ecomputertips.com/differences-between-windows-7-and-windows-10/)
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
-
No winter road salt in your neighborhood? I can do about 20 years max before my car underside gets to be structurally deficient. (I'm in Minnesota.)
Calgary never used salt to the extent you would be driving in (salty) slush like a lot of places. The body held up very well. The city is always waiting for the next "Chinook" before doing much about snow ... a west wind from the mountains that can drive temperatures up 20 degrees in a matter of hours and melt everything ... then later turn it into a skating rink.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
-
Calgary never used salt to the extent you would be driving in (salty) slush like a lot of places. The body held up very well. The city is always waiting for the next "Chinook" before doing much about snow ... a west wind from the mountains that can drive temperatures up 20 degrees in a matter of hours and melt everything ... then later turn it into a skating rink.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
I have the dubious honor of living in the city that spends most on snow removal[^]. If something was not corroded during the winter, spring potholes would surely take care of it. After 10 years cars are kept together mostly by duct tape and prayers :laugh:
Mircea
-
I would suggest you don't use Visual Studio on Mac, it's terrible. I use Rider from Jet brains instead
Every day, thousands of innocent plants are killed by vegetarians. Help end the violence EAT BACON
I've tried using VS2022 on the mac and just switched to VSCode. I've not tried Rider but some on my team have. Have you compared it to VSCode on a mac?
cheers Chris Maunder
-
Installed VS2022 on a Win7 VM, and was greeted by a dialog box that stated that I was installing VS2022 onto an unsupported OS. I suspect that VS2025 will not allow you to install onto Win7 at all. EDIT--------------------------------- ATTENTION!!! Read my post again. I am not saying MS has to maintain support for Win7 in Visual Studio. I was merely observing that "support" for installing VS on Win7 would eventually disappear, and that process has started with the warning dialog box that I encountered when installing 2022. Don't bother me with bullsh*t arguments regarding an expectation of MS maintain support for Win7, or that Win10+ "ain't that bad". That's not the point I was even remotely trying to make.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013I hope you don't expect all those thousand of little settings you've tweaked to VS so it's just right to follow you to 2022. It's like 2022 had never seen me before. Further, the settings sync doesn't. I'm running VS on 3 machines and still, after months, I'm still tweaking the settings so (a) it's like 2019, and (b) things are actually in sync.
cheers Chris Maunder
-
I don't have a problem with Windows 10. I use it for work 8-10 hours a day, 5-6 days a week.
-
Do you have any articles that say this?
The difficult we do right away... ...the impossible takes slightly longer.
