|
I don't drink coffee, so that's off the table (or off my desk, actually) 
Yeah, refactoring is difficult though, as I'm not even able to run half of the stuff yet 
And I guess the original programmer will be back in a few months and he won't be too happy if I "fixed" all of his stuff.
Besides, there's a lot that needs fixing first.
I'll get there, though...
|
|
|
|
|
hope u take backups before you dive in
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
Back ups are for wussies 
|
|
|
|
|
I have been in a situation like this in the past. My approach was to seemingly double the work by keeping the Original Sacred Texts version, and My Own Version with renamed variables and functions and profuse comments about what I understood.
Any logic changes that I made could be added to the Sacred Original after I was sure about them.
|
|
|
|
|
Anyone tried or using .Net MAUI yet?
If it's not broken, fix it until it is.
Everything makes sense in someone's mind.
Ya can't fix stupid.
|
|
|
|
|
What a coincidence - just posting about the GA[^]
(Sorry, I haven't tried it though)
TTFN - Kent
|
|
|
|
|
No, but it's my next port of call. I'd love to hear others' thoughts.
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, 2013
modified 13-Apr-22 12:22pm.
|
|
|
|
|
Soon you will only be able to run Visual Studio on Windows 11 or Mac OSX
|
|
|
|
|
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
|
|
|
|
|
#realJSOP wrote: we only started using VS2017 last year
We were forced to upgrade one of our products from VS2008 to VS2019 last fall. We discovered that a third-party hardware support library we use needed VS2015 or better. The upgrade went surprisingly well. It only took two of us a week to deal with most of the new compiler diagnostics.
Software Zen: delete this;
|
|
|
|
|
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
|
|
|
|
|
I do use VSCode for React / Gitops / Terraform but I will now have to look at creating a C# project out of curiosity
Every day, thousands of innocent plants are killed by vegetarians.
Help end the violence EAT BACON
|
|
|
|
|
Rider for me EVERYWHERE these days, along with the rest of the JB tools such as WebStorm, IntelliJ, DataGrip etc
I got fed up with VS's shenanegins last year, I was loosing more time on client projects dealing with VS being stupid, than I was being productive, so I jumped ship.
I've just renewed my first year licence this morning with a 20% discount for sticking with them.
What really pleases me though is the license model is fair.
If I cancel my subscription now, then for the next year I WILL continue to get updates, and as of April 13 2023, the version last released prior to that is mine to keep and use for ever.
So basically, I pay my yearly subscription, continue getting the bleeding edge, once I choose not to renew, I still get to keep and use EVERYTHING I have paid for, I can get an offline/perpetual licence that allows me to download all my previous products and install them on all my machines without having to have the toolbox app installed and logged into my JB account.
Next year if I continue, I get another 20% discount, then for each year after that it stays at that 40% discounted price.
As for the tools I get access too, it's every IDE they do, and about 5 other things too.
Oh and it runs EVERYWHERE... I have it on my windows machines, 7,8.1 and 10, I have it on Red-Hat & Debian based Linux deployments, I even have it running on an old Apple Mac laptop.
|
|
|
|
|
Do you have any articles that say this?
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Our dev team used this - we had a skunk works fungus who reputation fired by adrenaline of 20 somethings, way back in the 80s.
The impossible we do straight away
Miracles take a little longer
Developer, trainer, tester, bug smasher
|
|
|
|
|
Our dev team used this - we had a skunk works fungus who reputation fired by adrenaline of 20 somethings, way back in the 80s.
The impossible we do straight away
Miracles take a little longer
|
|
|
|
|
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
|
|
|
|
|
Man, you really, really need to retire. 
|
|
|
|
|
|
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.
|
|
|
|
|
Windows 7 was so much faster you could knock that down to 6 hours a day, 4 days a week. 
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
