I've seen references in various places - including this article - about the performance hit of the VB.NET background compiler (BC) for large projects.
But just how large does a project need to be for this to be an issue? We have a 12 project solution containing about 200,000+ lines of VB.NET code that doesn't seem to have any BC performance issues, even on our most modest development systems (mine is an old 1.7Ghz 1.5GB XP system). And we haven't applied any of the "tweaks" that are supposed to improve the BC's performance (because we haven't needed to!).
Is this possibly another one of those phantom "problems" that gets passed around as fact, but has very little real basis?
But even if we WERE having performance issues with the BC, I would be hard-pressed to give it up. All the other differences between VB.NET and C# such as syntax and case-sensitivity and whatever pale in comparison to the immediate feedback that the BC provides.
Last Visit: 31-Dec-99 18:00 Last Update: 22-Aug-14 1:08