|
You guys have a klingon national anthem ?
|
|
|
|
|
|
It is part of the United Kingdom.
|
|
|
|
|
[^]Quote: Despite processing 16-bit TIFFs in CaptureOne and Lightroom on one screen, messing with a 100MP photo in Photoshop on another, rendering a video out in Resolve, and playing back footage in Final Cut all at the same time, the computer never had to use more than 70GB of its RAM. Even when all of the CPU cores were at full load.
Well maybe they don't need all these options:Quote: 16-core 3.2GHz Intel Xeon processor, 192GB of RAM, Afterburner Card, and not one but two Radeon Pro Vega II graphics cards with 32 total gigabytes of VRAM
And the US$ 6k monitor: for graduation ?
«One day it will have to be officially admitted that what we have christened reality is an even greater illusion than the world of dreams.» Salvador Dali
|
|
|
|
|
I once was a college student, and I did exactly none of these things on my computer back then.
But then, I studied programming, not farting around with picture- and video-editing software.
|
|
|
|
|
dandy72 wrote: I once was a college student, and I did exactly none of these things on my computer back then.
I once was a college student, and my computer could do exactly none of those things back then.Quote: - OP all at the same time, the computer never had to use more than 70GB of its RAM
about 70000 times the RAM I had (even then only 640k usable limit), 14000 times my HDD so I couldn't even swap to that.
How did we manage? defies all logic we managed to achieve anything at all?
... apart from help [some more, some less, we all shared the pain] produce the very machines and software these kids are [seemingly still dissatisfied with] today.
my heart goes out to them ... not!
(and now time for an even older fart to pipe up), LUXURY! We...
after many otherwise intelligent sounding suggestions that achieved nothing the nice folks at Technet said the only solution was to low level format my hard disk then reinstall my signature. Sadly, this still didn't fix the issue!
|
|
|
|
|
dandy72 wrote: I studied programming, not ...
And, thanks to that you are the  18-year veteran CP Lounge lizard you are today
«One day it will have to be officially admitted that what we have christened reality is an even greater illusion than the world of dreams.» Salvador Dali
|
|
|
|
|
I'd rather hang out here than on some Photoshop user forum. 
|
|
|
|
|
I always find it slightly amusing that a lot of the mac hardware reviews always talk about how fast they can do video editing.
I think we need to setup a review section where we talk about how many browser windows you can have open while cutting and pasting code into Visual Studio Code or xcode while simultaneously building a full solution including deployment packages to the different desktop OSs and 2 mobile platforms, all the time while watching Netflix on the other monitor.
That would make me sit up and listen to the review.
cheers
Chris Maunder
|
|
|
|
|
Wow, is this what every college student is doing these days? 
Thinking about college has brought back a flood of fond memories...and it cold and damp outside on this Saturday, so forgive me for being nostalgic.
Back in the late 80's I started CS classes and did well but really hated the fact that all final homework tasks (getting your program to compile and print to green-bar) had to be done in the lab. The lab was often over crowded and getting a terminal that actually worked was a challenge. There was also the unwritten rule that if an upperclassman needed it, you had to give it up...that rule got me kicked out of the lab and therefore the CS program. I quit school and got a factory job.
10 years later, tired of constant overtime and manual labor, I got an opportunity to go back to school. I didn't think twice. My dad set me up with a hand-me-down PowerMac 6100 beige box that the phone company was tossing. OS 7.5.x was absolute garbage which was why my very first computer book was 'Sad Macs Bombs and Other Disasters'!  I must have re-installed that OS a dozen or so times. Still, it was quite a learning experience in troubleshooting computer problems
Trying to remember the specs...I think it was a 66MHz PPC, 8MB ram, and a 500MB scsi hdd. (later upgraded to 32) I had MS Office on floppies. (3 dozen or so IIRC) It got me though my first year of college introductory courses, but when I started into programming courses, everything was Windows so I got my first Windows machine around '98. (AMDK2-6 350MHz, 32MB, and 4B hdd) I upgraded every component of that machine (except mobo/cpu) even adding an LS-120 drive. I also got my first version of Visual Studio. To me, this was an awakening and I knew I'd never be the same.
No more labs! I could now write, debug, and even compile my programs from home and at any time I wanted! I could study and learn at my own pace! Now, programming wasn't just about typing code into a terminal, it was now a visual experience! I was hooked! The second go-round with college went much better than the first. I was a much better student at 30 than I was at 20, though probably not as much fun! Anyway, it's been a great 20 year trip since then. Thanks for letting me share. 
"Go forth into the source" - Neal Morse
|
|
|
|
|
Most college students will only use Word, Excel, a web browser, and Fortnight.
".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: Most college students will only use Word, Excel, a web browser, and Fortnight.
Don't forget Facebook, Twitter, and whatever the a-social media platform of the day is.
|
|
|
|
|
obermd wrote: Don't forget Facebook
You're old-school. I'm told the kids are shunning Facebook, because grandma's there now...
|
|
|
|
|
Hi all,
One customer asked me to do a small C# application and wants me to use VS2019... I currently have VS2017 in my computer and I'm using it a lot even integrated into my PLC developing needs.
Will 2019 work gracefully and won't make problems with 2017?
Any consideration before installing it?
Thank you all!
|
|
|
|
|
It shouldn't be a problem: Install Visual Studio versions side-by-side - Visual Studio | Microsoft Docs[^] but it may affect file associations as .C#, /SLN, and .PRJ will be set to the last installed version. And it you open a solution / project in 2019 it may give problems when subsequently opened in 2017, though generally that's better these days than it was back in VS2008.
Certainly, I have no problems with 2019, 2013, and 2010 on this PC, though I did uninstall 2015 and 2017 before I added 2019.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Though I've not tried it, it's supposed to work.
Where I've heard problems can occur is not so much the installations, but updates to the earlier installed version. (Also, not applicable for you but in general the higher version needs to be installed before the lower - i.e. 2019 after 2017 is OK, 2015 after 2017 not.)
But consider installing a VM for the other version.
- Sure more initial farting around,
- but there will be no chance of inter-version "effects" and "fun."
- also snapshots, easy clean up and roll back.
- clones, (i.e. a pre-vs clone) - next time around skip the windows [and prefs] install work
after many otherwise intelligent sounding suggestions that achieved nothing the nice folks at Technet said the only solution was to low level format my hard disk then reinstall my signature. Sadly, this still didn't fix the issue!
|
|
|
|
|
I have had the two versions installed alongside one another for a couple of years now with no problems. Initially I used both extensively although now I'm using 2019 almost exclusively.
I installed 2017 first and I support the suggestion of others that it's best to do it in that order.
Be careful about making significant changes to a project/solution in 2019 if you want to open it subsequently in 2017, but normal code editing doesn't cause problems.
Phil
The opinions expressed in this post are not necessarily those of the author, especially if you find them impolite, inaccurate or inflammatory.
|
|
|
|
|
I installed 2017 first, thenn 2019. No problems. When I felt 2019 was stable enough, I removed 2017. No problems.
«One day it will have to be officially admitted that what we have christened reality is an even greater illusion than the world of dreams.» Salvador Dali
|
|
|
|
|
I've had no problems running them side by side in the past
Real programmers use butterflies
|
|
|
|
|
I actually have 2008, 2010, 2015, 2017 and 2019 on the same computer - all working side by side with no problem...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
|
|
|
|
|
I've got 2010, 2017, and 2019 all on the same system with no problems whatsoever. I prefer 2010 when possible due to the slower load/build times with the newer versions.
"Go forth into the source" - Neal Morse
|
|
|
|
|
I ran them both on windows 7 and just upgraded to 10 and have had no problems.
It's been 6 months since I joined the gym and there's been no progress. I'm going there tomorrow in person to find out what's really going on!
JaxCoder.com
|
|
|
|
|
There are no problems having both versions side-by-side.
If you want to open a project/solution in a particular version, it may be better to open Visual Studio first, and then open the solution inside VS. Otherwise, it will probably use the last version installed.
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
I'm retired now but when I was working, we had multiple VS20xx versions running on the same computer. Crucial to the process is not having any of the Visual Studio symbols pre-defined in your environment. Each version of the IDE should be activated from a DOS window/command line that is found in the menu tree for each compiler. Clever users (this would be you) can look at the contents of each menu item and cook up the same thing yourself and make them desktop shortcuts with your own local/personal modifications.
I haven't used VS2017 or VS2019 but I would assume that the same trick will still work.
P.S. Make absolutely sure that all remnants of any and all compilers do not exist in your environment before starting this. Type 'msdev' (or whatever it is now) at the command line and make sure it gives an error. Likewise, start from a menu item selection and verify that it gives an error.
I'm retired. There's a nap for that...
- Harvey
|
|
|
|
|
No problems here, I have 2008, 2015, 2017 and 2019 all installed and they co-exists happily with each other on W10 X64.
One thing I will say though, since VS15 all installs have shiped with the "Visual Studio Version Detector", if you set up your file associations to load with that (Particularly your SLN files) then it will examine the SLN file (Or if it's a .cs file, will look in same folder for SLN/CSPROJ) and determine if possible which Visual Studio Version to open it with.
Failing that, I have icons on my desktop for all the versions, and I just drop the SLN from explorer onto the version I want to use when loading.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
