http://tewha.net Writings and links on iPhone and iPad programming Sat, 28 Jan 2012 02:21:42 +0000 hourly 1 http://wordpress.org/?v=3.3.2 http://tewha.net/software-development/disabling-intellisense/comment-page-1/#comment-56 Turning off intellisense for a project | keyongtech Sun, 18 Jan 2009 17:05:08 +0000 http://objectsatrest.com/software-development/disabling-intellisense/#comment-56 <p>[...] Re: Turning off intellisense for a project On Sep 22, 11:10*am, "Hillbilly" <someb...@somewhere.com> wrote: > IntelliSense can also be intrusive and force itself on us wasting time and > effort. I would like a way to easily and rapidly toggle it on and off > myself. Like Ctrl-I for example > > "raylopez99" <raylope...@yahoo.com> wrote in message > > news:ac5083ca-2754-4e61-95aa-3a04f4bed30e... > > > > > There is in Visual Basic (you use Attributes), but I don't know about > > C#. *Probably, if you dig deep enough into the options. > > > But why would you want to turn off IntelliSense? *That's one of the > > most useful features of a strongly typed language like C# is. > > > RL > > > Clive Dixon wrote: > >> I have a project as part of a solution which contains a very large number > >> of > >> autogenerated class files. When compiling the solution and the > >> autogenerated > >> files have changed, visual studio takes an age to recreate intellisense > >> information for the autogenerated classes. Is there any way whatsoever > >> that > >> I can turn off intellisense generation on a per-project or per-class > >> manner? > >> I had hoped that [EditorBrowsable(EditorBrowsableState.Never)] would stop > >> the generation of intellisense info for the specified item, but it > >> appears > >> to do nothing of the sort.- Hide quoted text - > > - Show quoted text - you may try to "break" it - see this (if the Whole Tomato thing is an IntelliSense competitor/alternative, then I'll have to say that I am not affiliated nor I get paid for finding this link for you :-) http://tewha.net/software-developmen...-intellisense/ [...]</p> [...] Re: Turning off intellisense for a project On Sep 22, 11:10*am, “Hillbilly” <someb…@somewhere.com> wrote: > IntelliSense can also be intrusive and force itself on us wasting time and > effort. I would like a way to easily and rapidly toggle it on and off > myself. Like Ctrl-I for example > > “raylopez99″ <raylope…@yahoo.com> wrote in message > > news:ac5083ca-2754-4e61-95aa-3a04f4bed30e… > > > > > There is in Visual Basic (you use Attributes), but I don’t know about > > C#. *Probably, if you dig deep enough into the options. > > > But why would you want to turn off IntelliSense? *That’s one of the > > most useful features of a strongly typed language like C# is. > > > RL > > > Clive Dixon wrote: > >> I have a project as part of a solution which contains a very large number > >> of > >> autogenerated class files. When compiling the solution and the > >> autogenerated > >> files have changed, visual studio takes an age to recreate intellisense > >> information for the autogenerated classes. Is there any way whatsoever > >> that > >> I can turn off intellisense generation on a per-project or per-class > >> manner? > >> I had hoped that [EditorBrowsable(EditorBrowsableState.Never)] would stop > >> the generation of intellisense info for the specified item, but it > >> appears > >> to do nothing of the sort.- Hide quoted text – > > – Show quoted text – you may try to “break” it – see this (if the Whole Tomato thing is an IntelliSense competitor/alternative, then I’ll have to say that I am not affiliated nor I get paid for finding this link for you http://tewha.net/software-developmen…-intellisense/ [...]

]]> http://tewha.net/software-development/disabling-intellisense/comment-page-1/#comment-55 Pyile » Blog Archive » Visual Studio to get faster, but no less stupid Fri, 14 Sep 2007 19:16:08 +0000 http://objectsatrest.com/software-development/disabling-intellisense/#comment-55 <p>[...] “A downside of this is that Visual Studio, while opening a solution, would wait until the background complier had a chance to run.” — I hit this daily. And, in fact, it was only on reading this that I realized that SP1 replaced feacp.dll. [...]</p> [...] “A downside of this is that Visual Studio, while opening a solution, would wait until the background complier had a chance to run.” — I hit this daily. And, in fact, it was only on reading this that I realized that SP1 replaced feacp.dll. [...]

]]>