Statement Completion -- Parameter Information problem

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

    Statement Completion -- Parameter Information problem

    I am writing a database program in C#.
    I have a situation when I type the '(' after typing a method call, VS goes
    into an infinite loop. I then have to exit VS.
    Has anyone else had any trouble with statement completion / parameter
    information?

    Here is a little more information.

    The problem code looks like this: CodeData.t_xxx. Addt_xxxRow...
    CodeData references a strongly typed dataset. The dataset is in an other
    assembly that I also own.

    The database is Access.

    t_xxx is the name of the table.

    Addt_xxxRow is the VS generated code to add a new typed row to the table.

    When I press the '(' key after entering the above line, VS never returns.
    My guess is that it is looking for the parameter lists and something keeps
    it from finding them.

    Windows Task Manager shows devenv.exe (VS) using > 95% of CPU time. I let
    things sit for over a half hour and still had to exit out.

    One mouse click on the client area gives me a wait cursor; then I can X out
    with a not responding popup. If I remember correctly, a second click on the
    client area locks the whole computer!

    Other processes are still working, but with some long delays for some
    functionality.

    Other methods on CodeData.t_xxx class work correctly. That is statement
    completion doesn't lock up.

    Rebuild doesn't help, nor does restarting the computer.

    I am running XP professional with all of the latest service updates.

    If anyone has seen the statement completion parameter information lockup
    before, please respond with any help.

    By typing the () first then typing the method -- no problem. Code also,
    compiles and runs correctly.

    Regards

    Chuck




  • mikeb

    #2
    Re: Statement Completion -- Parameter Information problem

    Chuck wrote:
    [color=blue]
    > I am writing a database program in C#.
    > I have a situation when I type the '(' after typing a method call, VS goes
    > into an infinite loop. I then have to exit VS.
    > Has anyone else had any trouble with statement completion / parameter
    > information?
    >
    > Here is a little more information.
    >
    > The problem code looks like this: CodeData.t_xxx. Addt_xxxRow...
    > CodeData references a strongly typed dataset. The dataset is in an other
    > assembly that I also own.
    >
    > The database is Access.
    >
    > t_xxx is the name of the table.
    >
    > Addt_xxxRow is the VS generated code to add a new typed row to the table.
    >
    > When I press the '(' key after entering the above line, VS never returns.
    > My guess is that it is looking for the parameter lists and something keeps
    > it from finding them.
    >
    > Windows Task Manager shows devenv.exe (VS) using > 95% of CPU time. I let
    > things sit for over a half hour and still had to exit out.
    >
    > One mouse click on the client area gives me a wait cursor; then I can X out
    > with a not responding popup. If I remember correctly, a second click on the
    > client area locks the whole computer!
    >
    > Other processes are still working, but with some long delays for some
    > functionality.
    >
    > Other methods on CodeData.t_xxx class work correctly. That is statement
    > completion doesn't lock up.
    >
    > Rebuild doesn't help, nor does restarting the computer.
    >
    > I am running XP professional with all of the latest service updates.
    >
    > If anyone has seen the statement completion parameter information lockup
    > before, please respond with any help.
    >
    > By typing the () first then typing the method -- no problem. Code also,
    > compiles and runs correctly.
    >[/color]

    I have not had this problem, but I have had good luck using the 'Repair'
    option on VS.NET's Setup to fix strange problems the have cropped up on
    my machine.

    --
    mikeb

    Comment

    Working...