3 ms·
I really hope they nail it with Rider. I am so sick of Visual Studio. It just gets slower and slower. I have a 20 core machine, with 128gb of RAM and it cons
by louthy 9y ago
I really hope they nail it with Rider. I am so sick of Visual Studio. It just gets slower and slower. I have a 20 core machine, with 128gb of RAM and it constantly seizes up for seconds at a time, various components crash randomly, and things sometimes work and sometimes not: Go To Definition for example, or pressing F2 to rename. Whatever it is that suggests I add a missing using sometimes decides it can't do that and instead prefixes the unknown type with the fully qualified name (so it has the namespace, it prefixes the type I wrote, but it can't suggest adding the using). Debugging has been broken too, where sometimes it can't even show me what my local variables are never mind other vars, and it is also much slower than it was. And god help you if you have a large code file in your project. The moment you've opened it once, that's it everything starts falling apart and slowing to a crawl. If I copy a file in a .NETCore project then I have to close the solution and re-open it for the compiler to see it. Et cetera, et cetera.
It's obvious that things that shouldn't do a lot of work, do in fact do work. Like if I press Ctrl+C on some selected text. I simply expect it to put the text into the clipboard. But sometimes it will stall, put a dialog on the screen telling me it's doing some formatting and I need to wait! What the hell is it formatting?
Every member of my team is sick of it and it's negatively affecting our productivity, so if Rider is good then bye bye Visual Studio.
- snomad 9y agoThank you for this. I have been using VS 2017 primarily for last 6 months as I enter the .net world and thought many of these complaints were me / my substandard machine.
- jedwardhawkins 9y agoYour experience with VS and your desires for Rider reflect my own. Correct me if I'm wrong, but isn't Visual Studio still a 32 bit application? That would definitely limit the utility of those 128GB.
- louthy 9y agoI tend to have a number of solutions open. But mostly I was just trying to convey that my setup isn't to blame (fastest possible ram, large amounts of it, super fast cpu, all off SSDs too). Obviously a 32bit app could run a number of sub app domains, so it can still make use of more than 2gb. I think ultimately though is it's not the resource that's the issue, it's the buggyness of the system. It just feels unfinished, and it seems there's some lazy decisions made in implementation ... the formatting error on Ctrl-C sounds like it's doing too much work; other things like if I try to download a publicly available nuget package, through the god awful UI, I have the source setup as nuget.com - it then pops up a dialog asking for my credentials to my company nuget server! If I cancel it, guess what, it fails to get the package from the web. I have a strong suspicion that it's talking to the net too often generally (I have a slow broadband connection, so I see areas that are clearly doing too many round trips). I feel it seemed to really start going downhill when Roslyn became the compiler (which I assume is running most of the tooling). I don't know if that's anything to do with it, but I assume they had to rewrite a lot of the core components when Roslyn came along. 2015 wasn't great, 2017 is really bad. Waiting several years for them to finish the project properly is taking its toll on my confidence in a product I've used in one form or another since 1994
- davkean 9y agolouthy, I'm from the VS team. Sorry to hear that you are running into this. Can you Help -> Send Feedback - Report a Problem (don't worry about the contents), and point me to the resulting feedback? I'll dig into your performance data and make sure we've got bugs/fixes for the things you are running into. Dave twitter.com/davkean