|
any vs2019 users..installed it..updated it to 16.1.2..after removing vs2017 .... seems faster.?..or is it just perception?
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
I'm using 16.0.3, and it seems faster to load than 2017 was, but a little slower to compile.
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
"loads faster", but is it really ready sooner?
even windows does that now, but on older machine it still runs like a slug for the next half a minute till it's really responding normally.
|
|
|
|
|
Seems to be - and I'm only running a i5/8GB - I suspect that it's the SSD that makes the load time acceptable.
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
ah well SSD, of course. I run win7/vs17 in a VM on a pure SSD linux box - it's also ready right away.
using other people machines with spinners in them, I now know the real reason they call them "hard disks" - damn hard not to get annoyed waiting for something to happen.
|
|
|
|
|
i tried on same i5/8gb but ssd...
|
|
|
|
|
lol, i have basically the same machine
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
|
|
|
|
|
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!
|
|
|
|
|
they had a load big project performance update recently.. nothing to do with removing old version...
also maybe your disk was fragmented or something...
|
|
|
|
|
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.
|
|
|
|
|
I installed in 3 weeks ago. Haven't face any issue so far. The start page is faster so it take less time to open the VS2019.
I can say they do have improved the performance.
If you are not criticized, you may not be doing much.
|
|
|
|
|
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.
|
|
|
|
|
I haven't noticed much difference really. (then again i7-5820K at 3.3Ghz and 128GB ram on a 1TB SSD   )
|
|
|
|
|
As a matter of interest, what's your motherboard?
|
|
|
|
|
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.
|
|
|
|
|
Many thanks for the specs.
|
|
|
|
|
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).
|
|
|
|
|
Vs 2017 ver. 15.9.12 blew up my existing installation of VS 2017 and I was unable to get VS 2019 installed at all, no matter what I tried.
VS 2017 stopped being able to compile projects and VS 2019 couldn't open them.
It appears that I am the only technician on the planet who had trouble with all these recent upgrades... at least according to Microsoft's Installation techs... 
I went back to VS 2015...
Steve Naidamast
Sr. Software Engineer
Black Falcon Software, Inc.
blackfalconsoftware@outlook.com
|
|
|
|
|
|
Nope, only got a fiver in my pocket.
|
|
|
|
|
|
Like 2 years ago
Director of Transmogrification Services
Shinobi of Query Language
Master of Yoda Conditional
|
|
|
|
|
Dang. RSS echo. Ah well, maybe I'll check to see how Leslie Neilsen and Abe Vigoda are doing.
TTFN - Kent
|
|
|
|
|
Lol, I wasn't going mad then in thinking he'd already died. Though I do often experience that thought when the occasional very old celebrity kicks the bucket. 
Kevin
|
|
|
|
|
Curse you, Clock King!
Or Calendar Man, I guess.
"Never attribute to malice that which can be explained by stupidity."
- Hanlon's Razor
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
