Missing control properties

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • steve bull
    #1

    Missing control properties


    I have created a control with a property BoxStyle, an enum, which is in a dll Graphics2D.dll. Normally when the editor
    picks everything up it will give me context help eg. NewControls.Col orComboBox.BoxS tyle.fullBox prompting at each step.

    When I remove the reference to the dll and add it again the editor will do the prompt as I would expect. As soon as I
    rebuild the editor no longer recognizes the BoxStyle property and only gives me the default properties for ListBox.

    Can anyone explain what MS does? It is really annoying.

    When I load the main project I get the compilation error 'BoxStyle is either undeclared or never assigned'. If I build
    the code it runs fine. But, I really do not understand what Visual Studio's problem is.


    Any ideas would be very welcome.


    Thanks,

    Steve
    Tags: None
    • Alan Pretre
      #2
      Re: Missing control properties

      "steve bull" <bullsj@comcast .net> wrote in message
      news:elr28157b0 qc2jqiubvi9ni14 nk52f13j1@4ax.c om...[color=blue]
      > Can anyone explain what MS does? It is really annoying.[/color]

      There is a bug in VS.NET where occasionally it cannot copy the .xml file
      because it is locked. The bug is that VS.NET has locked the file and will
      not release it. If you build eventually you may see a message in the output
      saying that a file cannot be copied. This is the file you need for
      Intellisense. The only way I have found to get rid of it is to close VS.NET
      and reopen.

      -- Alan


        Comment

        • steve bull
          #3
          Re: Missing control properties



          I have tried closing VS.Net and I have even restarted the machine but I still get the problem. I have also deleted the
          dll as well so it needs to copy the new version from the latest build. The toolkit generates the correct code. Pity it
          can't execute what it generates.


          Steve




          On Tue, 10 May 2005 22:21:43 -0500, "Alan Pretre" <alanpretre@new sgroup.nospam> wrote:
          [color=blue]
          >"steve bull" <bullsj@comcast .net> wrote in message
          >news:elr28157b 0qc2jqiubvi9ni1 4nk52f13j1@4ax. com...[color=green]
          >> Can anyone explain what MS does? It is really annoying.[/color]
          >
          >There is a bug in VS.NET where occasionally it cannot copy the .xml file
          >because it is locked. The bug is that VS.NET has locked the file and will
          >not release it. If you build eventually you may see a message in the output
          >saying that a file cannot be copied. This is the file you need for
          >Intellisense . The only way I have found to get rid of it is to close VS.NET
          >and reopen.
          >
          >-- Alan
          >[/color]

            Comment

            Previous template Next
            Working...