Turning off intellisense for a project

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Clive Dixon

    #1

    Turning off intellisense for a project

    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 (EditorBrowsabl eState.Never)] would stop
    the generation of intellisense info for the specified item, but it appears
    to do nothing of the sort.


  • raylopez99

    #2
    Re: Turning off intellisense for a project

    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 (EditorBrowsabl eState.Never)] would stop
    the generation of intellisense info for the specified item, but it appears
    to do nothing of the sort.

    Comment

    • Clive Dixon

      #3
      Re: Turning off intellisense for a project

      Because firstly, every time I regenerate my autogenerated classes (created
      using a custom tool) and then recompile my solution, it takes 10-15 minutes
      for Visual Studio to recreate the intellisense info for that project. That's
      how bad my problem is. Normally I would not need to regenerate the classes
      on a regular basis, but while I am currently making lots of changes to my
      custom tool, it is slowing down my development horrendously.

      Secondly, all my autogenerated classes are interface based and will only be
      accessed via the interfaces - thus I will not be losing anything by not
      having intellisense info available for the classes.

      "raylopez99 " <raylopez99@yah oo.comwrote in message
      news:ac5083ca-2754-4e61-95aa-3a04f4bed30e@s5 0g2000hsb.googl egroups.com...
      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
      >autogenerate d class files. When compiling the solution and the
      >autogenerate d
      >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 (EditorBrowsabl eState.Never)] would stop
      >the generation of intellisense info for the specified item, but it
      >appears
      >to do nothing of the sort.

      Comment

      • Hillbilly

        #4
        Re: Turning off intellisense for a project

        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 " <raylopez99@yah oo.comwrote in message
        news:ac5083ca-2754-4e61-95aa-3a04f4bed30e@s5 0g2000hsb.googl egroups.com...
        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
        >autogenerate d class files. When compiling the solution and the
        >autogenerate d
        >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 (EditorBrowsabl eState.Never)] would stop
        >the generation of intellisense info for the specified item, but it
        >appears
        >to do nothing of the sort.

        Comment

        • Hans Kesting

          #5
          Re: Turning off intellisense for a project

          Clive Dixon wrote on 22-9-2008 :
          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 (EditorBrowsabl eState.Never)] would stop the
          generation of intellisense info for the specified item, but it appears to do
          nothing of the sort.
          In C# you have to specify an XML file where the intellisense info will
          be written to (project properties Build tab XML Documentation
          file).

          Clear the checkbox and no intellisense info should be generated.

          Hans Kesting


          Comment

          Working...