The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Anything that is unrelated to elephants is irrelephant Anonymous - The problem with quotes on the internet is that you can never tell if they're genuine Winston Churchill, 1944 - Never argue with a fool. Onlookers may not be able to tell the difference. Mark Twain
I'd kind of agree. It definitely starts faster than VS 2017, and feels a bit snappier in use. Beyond that it's not very different. One good thing about it.. There are a LOT of bugs (regressions) that Microsoft caused in the C++ compiler from VS 2017 update 8 onwards that are either unfixed in the latest VS 2017 compiler (15.9.12) that are fixed in VS 2019.
That said apparently MS are working to push another VS 2017 update in July to fix up all the stuff that VS 15.8 broken in C++ - and there are some significant bugs there!
I find it somewhat quicker to load but intellisense seems a little slower.
It still finds my bugs pretty quick but since I type eyes on keyboard and only stop to look at what I have actually typed and how much the intellisense has modified my typing when I run out of typing steam this might also be perception.
Additionally, they gone broke how good EF used to was.
Often I have to use the custom tool to propogate the database changes.
OR WORSE, if I use .NET CORE I gotta scaffold the buggers in the package manager console every time I make a small DB change.
i7 with 8G RAM, non-SSD Drive (need to change that):
I have both VS 2017 and VS 2019 installed. When loading the same project in each, it does feel like VS 2019 is faster in loading itself and the solution. As far as the actual build and intellisense and such, I don't see that great a difference.
On a different note, I would say that the quality of the editor and such is somewhat better. I have been moving my code to .Net Core 3.0, and it seems make this a straightforward (if not automatic) process.
ASROCK X99 Extreme4/3.1... uses the 2011 cpu socket and has 8 ram slots that can hold a 16GB module each. It's an older board but still good... I think they are up to X299 for the Intel chipset now, tho that is a 2066 socket instead of the 2011. AMD beat them to the punch by registering X399 so no idea what the next Intel x?99 will be.
VS2019 is definitely no worse than VS2017 and I like VS2017.
Updated to 16.1.3 today and the grump I had, which was slow intellisense (to the point where you have to wait 5-10 seconds for red marks to disappear - or stay), seems to have evaporated.
So, yeah, I'll adopt it (again).