Version 2.0.0.0 Final

I have a issue with LLBLGen Pro as follows - although not major, it can become extremely time consuming and bad when you have a big database upgrade, etc. If I, for example, delete a table, and do whatever has to be done in LLBLGen Pro as well as regenerate the code, the code generated gives compile errors in VS.NET (C#)

Having had a closer look, i noticed that the LLBLGen Pro deletes/removes some classes, but not all and then these classes refers to nothing. This is quite irritating and can cause that users decide not to use the app. It also leaves in some classes existing non-usercreated methods that causes compiletime errors.

Else, up to now, quite well done, it's a amazing app and code.

One last question - who on earth came up with the name. It's virtually impossible to refer to this app in meetings and general conversations due to the name that is just a bunch of abbreviation letters and not a name at all. Wow, such a good app, such a "non-user-friendly" name.

Regards Helga

Here's a further example of compiler errors that it creates: Both these methods has been listed below each other in exactly the same class. Note that i personally did not change, add or delete any code in this class:

/// <summary>Returns a new IEntityRelation object, between ProductEntity and ProductEntity over the 1:1 relation they have, using the relation between the fields:
    /// Product.ProductId - Product.ProductId
    /// </summary>
    public virtual IEntityRelation ProductEntityUsingProductId
    {
        get
        {

            IEntityRelation relation = new EntityRelation(SD.LLBLGen.Pro.ORMSupportClasses.RelationType.OneToOne);



            relation.AddEntityFieldPair(EntityFieldFactory.Create(ProductFieldIndex.ProductId), EntityFieldFactory.Create(ProductFieldIndex.ProductId));

            relation.StartEntityIsPkSide = false;
            relation.InheritanceInfoPkSideEntity = InheritanceInfoProviderSingleton.GetInstance().GetInheritanceInfo("ProductEntity", false);
            relation.InheritanceInfoFkSideEntity = InheritanceInfoProviderSingleton.GetInstance().GetInheritanceInfo("ProductEntity", true);
            return relation;
        }
    }

    /// <summary>Returns a new IEntityRelation object, between ProductEntity and ProductEntity over the 1:1 relation they have, using the relation between the fields:
    /// Product.ProductId - Product.ProductId
    /// </summary>
    public virtual IEntityRelation ProductEntityUsingProductId
    {
        get
        {

            IEntityRelation relation = new EntityRelation(SD.LLBLGen.Pro.ORMSupportClasses.RelationType.OneToOne);



            relation.AddEntityFieldPair(EntityFieldFactory.Create(ProductFieldIndex.ProductId), EntityFieldFactory.Create(ProductFieldIndex.ProductId));

            relation.StartEntityIsPkSide = false;
            relation.InheritanceInfoPkSideEntity = InheritanceInfoProviderSingleton.GetInstance().GetInheritanceInfo("ProductEntity", false);
            relation.InheritanceInfoFkSideEntity = InheritanceInfoProviderSingleton.GetInstance().GetInheritanceInfo("ProductEntity", true);
            return relation;
        }
    }

Hi,

Your error is odd, I already deleted many tables without problems. btw, do you use control software (like source safe) ?

helga wrote:

Version 2.0.0.0 Final

One last question - who on earth came up with the name. It's virtually impossible to refer to this app in meetings and general conversations due to the name that is just a bunch of abbreviation letters and not a name at all. Wow, such a good app, such a "non-user-friendly" name.

IMHO, LLBLGen is quite easy to say in french

Hi

Firstly, thanks for the french lesson - I tried in Greek and Afrikaans besides English and in all it's one heck of a lot to say

Further to your question, in this project we have not installed, as yet, any Source Control software.

It is indeed strange, but if you need to see the project and db scripts, then it might be worth the while that i send it to you. It's to good a software not to work with, but i've re-done it just now and still have the same problems.

Kind Regards Helga

helga wrote:

Version 2.0.0.0 Final

I have a issue with LLBLGen Pro as follows - although not major, it can become extremely time consuming and bad when you have a big database upgrade, etc. If I, for example, delete a table, and do whatever has to be done in LLBLGen Pro as well as regenerate the code, the code generated gives compile errors in VS.NET (C#)

Having had a closer look, i noticed that the LLBLGen Pro deletes/removes some classes, but not all and then these classes refers to nothing. This is quite irritating and can cause that users decide not to use the app. It also leaves in some classes existing non-usercreated methods that causes compiletime errors.

Please set CleanUpVSNetProject in the project properties to true, then re-generate. (After removing the files which have to be removed first). This keeps the project in sync, it will remove the files not generated again.

Else, up to now, quite well done, it's a amazing app and code.

One last question - who on earth came up with the name. It's virtually impossible to refer to this app in meetings and general conversations due to the name that is just a bunch of abbreviation letters and not a name at all. Wow, such a good app, such a "non-user-friendly" name. Regards Helga

I did. Lower Level Business logic Layer Generator. quite logical

helga wrote:

One last question - who on earth came up with the name. It's virtually impossible to refer to this app in meetings and general conversations due to the name that is just a bunch of abbreviation letters and not a name at all. Wow, such a good app, such a "non-user-friendly" name.

Regards Helga

Refer to it as "LL Cool J"

Someone in our office came up with that one and I also noticed that someone else, quite independently, also came up with the same thing on these forums - so thats official then!

OK, that seems much better - now i will just see the reaction in the development meeting - south africans does not always have the best sense of humor

Thanks Helga

Hi Ottis

Your name is logical and quite cool and very logical. The only problem we have hear everytime is the tongue twisting with "L-L-B-L-Gen-Pro" but i will take the "LL-Cool-B" suggested below or else just Gen-Pro that's easier to refer to.

Good Job and nice idea! Helga

yeah, the name isn't that pronouncable by a lot of people, so I'm also officially ordered not to suggest any names for any products now and in the future ever again .

I heard that v3.0 would be named LlblGen Pro Next Gen.

That would be LLBL N-Gen Pro (for Next Generation)

Walaa wrote:

That would be LLBL N-Gen Pro (for Next Generation)

lol I like this one