Hello, We finally decided to migrate to framework 3.5. We were using LLBLGen1, and now we are using LLBLGenPro 3.

In the old version, when the LLBL project was generated, we also had a ORMSupportClasses project were I could find the classes used by LLBL as for example : DataAccessAdapterBase.cs EntityBase.cs EntityBase2.cs EntityCollectionBase.cs EntityField.cs EntityField2.cs EntityFields.cs EntityFields2.cs FieldLikePredicate.cs .. UnitOfWork.cs UnitOfWork2.cs .. and so on.

Now, with the latest version of LLBLGen, when I generate my LLBL project, I cannot see where all these classes are generated.

Could you please inform me how does it work? Thanks

These classes are not generated, they are pre-compiled inside the referenced ORMSupportClasses...dll

Thank you,

But for example, if I want to modify or to add some new feature in one of the classes, where can I find them and modify them?

For example, if I need to modifiy EntityField2....

v3's sourcecode is in the Extra's section in the customer area.

Thank you,

So the person who got the licence for the v3, could also be able to see the source code in the customer area?

I will explain the reason for which I am asking about this:

I want to check if the current value in a column for a entityfield is DBNull (NULL). For example, in the database, I have a column with type NUMBER(18,4) who can also be NULL.

In my C# application, this is viewd as a double value and if in the database, the current value is null, in my application this will be seen as 0 value.

I have tryied the property IsNull, to check if the current value in a column for a entityfield is DBNull, but didn't get what I needed.

So, in the previous version of LLBLGen v1, we made our custom CurrentValueIsNull property who verified this thing.

Now, I wanted to add the same property in the EntityField, and EntityField2 classes.

Or is there with the new LLBLGen v3, a new property that does all that?

Thank you in advance

If a field is nullable then you should make sure it is generated as Nullable Type. By cheking the "Optional" checkBox for that field in the Designer. This way, the field will be null, if it's null in the database.

Ok, thanks.

The "Optional" checkBox is checked whenever a nullable field in the database. However, as we are migrating to .Net framework 3.5, I will retest this as soon as the project is set up.

I have another question, regarding the DAL.

Our project works with both SqlServer and Oracle Databases. Until now, using LLBLGen v1, we were generating a LLBLProject for SQLServer, and one for Oracle, and afterwards copied the specific classes in each of the two projects.

While migrating, when adding dll refrences to the project, in the RuntimeLibraries of the LLBLGen, there is the possibility to choose between .Net2 and .Net3.5.

In the .Net2 there are dlls for every type of database, like SD.LLBLGen.Pro.DQE.SqlServer.NET20, and SD.LLBLGen.Pro.ORMSupportClasses.NET20

In the .Net3.5 there is only SD.LLBLGen.Pro.ORMSupportClasses.NET3.5.

Could you indicate how does it work? The SD.LLBLGen.Pro.ORMSupportClasses.NET3.5 works with both SD.LLBLGen.Pro.DQE.SqlServer.NET20 and SD.LLBLGen.Pro.DQE.OracleODP.NET20, or I don;t need them any more?

The SD.LLBLGen.Pro.ORMSupportClasses.NET3.5 works with both SD.LLBLGen.Pro.DQE.SqlServer.NET20 and SD.LLBLGen.Pro.DQE.OracleODP.NET20

Yes it does.