4 ms·
I disagree. For a few hundred/thousand line projects it's ok. I deal with large (1Mloc+) 10 year+ old codebases in C#/ASP.Net and it is in no way capable of ha
by gouranga 14y ago
I disagree. For a few hundred/thousand line projects it's ok.
I deal with large (1Mloc+) 10 year+ old codebases in C#/ASP.Net and it is in no way capable of handling a large project without chopping it into miniscule assemblies and having solutions for each.
The IDE is monolithic enough to have severe usability and performance problems. It doesn't scale well and therefore is a risk if you want to continue using the platform for many years.
- marshray 14y agoIt's true. I have to split off separate .slns when the code gets to be large like that. I would not try to handle 1M lines in a .sln. UI responsiveness took a huge hit after VC6 with the dotnet stuff and never really recovered.
- mst 14y agoBy that point I would have expected a few dozen web services. One could guess that insufficient of their customers have codebases like that for them to care over whichever feature requests got priority instead. But, um, ow. I feel for you.
- pm90 14y agoHonest question....which IDE setup do you use?
- gouranga 14y agoVs2010 + testdriven.net. We got rid of visual svn and resharper as they made it less reliable.