tag:blogger.com,1999:blog-1762444900247458347.post329398862139415600..comments2023-04-22T17:45:42.702-07:00Comments on Accept no broken windows: Background compilation needs an on/off switchJames Geallhttp://www.blogger.com/profile/01687578733124838846noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-1762444900247458347.post-69679993641927276742007-06-03T09:36:00.000-07:002007-06-03T09:36:00.000-07:00The problem isn't that it shows a wavy line. In fa...The problem isn't that it shows a wavy line. In fact when I want it on, I like the fact that it does. But it isn't useful all of the time, and sometimes because of the performance issues, it is actually counter productive. I'd rather have intellisense and more importantly, text appearing when I type, and not some wavy red line. And at those times I want to be able to switch it off. So my point is not that background compilation is bad, just that no choice to switch it off is bad. <BR/><BR/>I don't want the switch to be changing the language I write code in.James Geallhttps://www.blogger.com/profile/01687578733124838846noreply@blogger.comtag:blogger.com,1999:blog-1762444900247458347.post-63553297672694419332007-06-03T08:57:00.000-07:002007-06-03T08:57:00.000-07:00I don't see the point about what is wrong with bac...I don't see the point about what is wrong with background compilation. Having a word with a red underline looks like nothing for me.<BR/><BR/>If you have not ended writting the red line will go when you end. That's all isn't it?<BR/><BR/>I mainly use Vb.Net instead C# because background compilation.Anonymousnoreply@blogger.com