Visual studio 2005, LLBLGen and Intellisense....

Posts   
 
    
ivanc
User
Posts: 36
Joined: 29-Apr-2004
# Posted on: 23-Oct-2006 09:47:32   

... the things I know: 1) VS 2005 is slow 2) VS 2005 is unstable 3) VS 2005 is slow cry

...but the thing that frustrates me the most is creating filters (RelationPredicateBucket). Whenever I write something like

PredicateFactory.CompareValue(

VS hangs for about two minutes or so and works extremely slow afterwards. It is completely unusable. Each letter takes about 3 seconds to appear on the screen as I type.

There are about 400 tables in the database that we work on so that is probably the issue here.

Does anyone know how to make the intellisense work properly?

(I've searched various forums, many people reported the issue, but no one offered a solution).

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39612
Joined: 17-Aug-2003
# Posted on: 23-Oct-2006 10:32:56   

It's slow because of the many overloads. This is also the reason why the Predicatefactory is made deprecated in v2.

You should use operator overloading, e.g.: PredicateExpression filter = new PredicateExpression(); filter.Add(CustomerFields.CompanyName=="Solutions Design");

As described in the manual. Use the Predicatefactory for backwards compatibility.

Frans Bouma | Lead developer LLBLGen Pro
pilotboba
User
Posts: 434
Joined: 05-Aug-2005
# Posted on: 23-Oct-2006 15:48:24   

ivanc wrote:

... the things I know: 1) VS 2005 is slow 2) VS 2005 is unstable 3) VS 2005 is slow cry

...but the thing that frustrates me the most is creating filters (RelationPredicateBucket). Whenever I write something like

PredicateFactory.CompareValue(

VS hangs for about two minutes or so and works extremely slow afterwards. It is completely unusable. Each letter takes about 3 seconds to appear on the screen as I type.

There are about 400 tables in the database that we work on so that is probably the issue here.

Does anyone know how to make the intellisense work properly?

(I've searched various forums, many people reported the issue, but no one offered a solution).

Are you using C#? If so try turning of the editor navigation bar and word wrap. There is a know issue that makes the editor an intellesense slow when you have these items on.

BOb