News for hackers. Stuff that matters.
Re:Project Rider – A C# IDE by interdrift on Wednesday January 13, 2016 @12:17PM (#10895854)
Altho I don't share your issues with all the 'bloating' stuff ( as others mentioned most of them can be avoided ) , I have a growing concern for the performance of VS while working with a bigger codebase (120+ projects) . It gets really really slow and full of loading screens which literally block you from doing anything. In fact you can sit there and wait 5+ minutes sometimes just to have the IDE let you do anything. Not to mention the infinite amount of times I've had Visual Studio close while I'm writing and it leaves my code in an unknown state. Oh yeah, not to forget the debugger exception which causes your debugger simply to detach even after you've spent around 5 minutes to get to the precise location of the program. Whoa, turns out I have quite a bit of hatred stored in me too! :D (VS2015)
Re:Project Rider – A C# IDE by VSTeam on Thursday January 14, 2016 @11:45AM (#10902490)
Hey interdrift, Can you ping us at [email protected]? We would like to chat with you more on your findings. Thanks
Re:Project Rider – A C# IDE by s73v3r on Wednesday January 13, 2016 @01:17PM (#10896283)
I would have to ask why you have 120+ projects. That's likely your problem; you're doing far too much within one solution.
Re:Project Rider – A C# IDE by lenkite on Thursday January 14, 2016 @01:57AM (#10900008)
120 is not that high. If you have fine-granular modules for re-use across multiple product lines, you need lots of projects. Yes, one can create several solutions for each line, but many times one needs to load all the projects especially feature teams that touch a little-bit everywhere.