Does the LLBLGen PRO 2.5 support 1.1

Posts   
 
    
scheineden
User
Posts: 7
Joined: 05-Sep-2007
# Posted on: 05-Sep-2007 09:16:39   

We have 1.1 ASP.net version (for LLBL projects)

So I just wonder if I compile the codes using 2.5 version is it going to be fine? Where could download for 1.1. version?

Walaa avatar
Walaa
Support Team
Posts: 14995
Joined: 21-Aug-2005
# Posted on: 05-Sep-2007 09:19:29   

LLBLGen Pro v.2.5 can generate code for the following .NET Framework versions:

.NET 1.0 .NET 1.1 .NET 2.0 .NET 3.0 CF .NET 1.0 CF .NET 2.0

scheineden
User
Posts: 7
Joined: 05-Sep-2007
# Posted on: 05-Sep-2007 09:22:01   

Walaa wrote:

LLBLGen Pro v.2.5 can generate code for the following .NET Framework versions:

.NET 1.0 .NET 1.1 .NET 2.0 .NET 3.0 CF .NET 1.0 CF .NET 2.0

Thanks that's was quick

scheineden
User
Posts: 7
Joined: 05-Sep-2007
# Posted on: 05-Sep-2007 09:34:03   

Hi support,

Quick question, this is my first time use the LLBLGen Pro. We have a .net project use this software.

I just wonder, I open a project solution for this. And I want to modify the Type from bit to integer.

Do I have to remap them again from database? Or I can directly choose from the list.

Currently I cant edit them at all.

Any tips or documents I can have a quick look. The documentation seems doenst help me much.

Walaa avatar
Walaa
Support Team
Posts: 14995
Joined: 21-Aug-2005
# Posted on: 05-Sep-2007 10:02:47   

I just wonder, I open a project solution for this. And I want to modify the Type from bit to integer.

Do I have to remap them again from database? Or I can directly choose from the list.

If the field has been changed in the database/schema then refresh the catalog and the LLBLGen Pro Designer will automatically detect any schema changes.

If the you want to generate a field with a type that differs from the .NET type that was automatically assigned to it (which should correspond to the database type). Then you should use a TypeConverter.

Any tips or documents I can have a quick look. The documentation seems doenst help me much.

The LLBLGen Pro documentation manual is very rich and detailed (400+ pages). Look for the following sections: "Using the designer -> Refreshing the catalog schemas" "Concepts -> Type Converters"

scheineden
User
Posts: 7
Joined: 05-Sep-2007
# Posted on: 06-Sep-2007 02:32:12   

Hi Support,

Thanks for that, the fields now auto populated based on the catalogs.

Now I faced another problems. Most of the generated codes are totally different with the previous one. The only changes i have made is only refreshing the catalogs. That's all

If we look further on below code: Old one is using the hashing and the new one is using the dictionary. And the declaration for the new one is using the partial class.

Note: The old one is using this the following version: // Code is generated using LLBLGen Pro version: 1.0.2005.1 // Code is generated on: Thursday, September 28, 2006 1:18:07 AM // Code is generated using templates: C# template set for SqlServer (1.0.2005.1) // Templates vendor: Solutions Design. // Templates version: 1.0.2005.1.111705

Currently I map them to sqlserver 2000, which I think the old code also maps to sql server 2000.

Do you have any idea about this?

For ex:

This is the old code:

// __LLBLGENPRO_USER_CODE_REGION_START AdditionalNamespaces
// __LLBLGENPRO_USER_CODE_REGION_END

/// <summary>
/// Entity class which represents the entity 'AffModules'.<br/><br/>
/// 
/// </summary>
[Serializable]
public class AffModulesEntity : EntityBase2, ISerializable
    // __LLBLGENPRO_USER_CODE_REGION_START AdditionalInterfaces
    // __LLBLGENPRO_USER_CODE_REGION_END    
{
    #region Class Member Declarations
    private static Hashtable    _customProperties;
    private static Hashtable    _fieldsCustomProperties;

This is the new code:

// __LLBLGENPRO_USER_CODE_REGION_START AdditionalNamespaces
// __LLBLGENPRO_USER_CODE_REGION_END

/// <summary>
/// Entity class which represents the entity 'AffModules'.<br/><br/>
/// 
/// </summary>
[Serializable]
public partial class AffModulesEntity : CommonEntityBase, ISerializable
    // __LLBLGENPRO_USER_CODE_REGION_START AdditionalInterfaces
    // __LLBLGENPRO_USER_CODE_REGION_END    
{
    #region Class Member Declarations


    // __LLBLGENPRO_USER_CODE_REGION_START PrivateMembers
    // __LLBLGENPRO_USER_CODE_REGION_END
    #endregion

    #region Statics
    private static Dictionary<string, string>   _customProperties;
    private static Dictionary<string, Dictionary<string, string>>   _fieldsCustomProperties;
Walaa avatar
Walaa
Support Team
Posts: 14995
Joined: 21-Aug-2005
# Posted on: 06-Sep-2007 11:31:33   

I guess you have generated code for .NET 2.0 or .NET 3.0

scheineden
User
Posts: 7
Joined: 05-Sep-2007
# Posted on: 10-Sep-2007 04:28:26   

Hi Support, any idea how to generate in the version 1.1

Do i have to choose special template to generate? When i choose the generate menu on the top, there is a list of template i can choose.

Would you be able to give a clue?smile

Walaa avatar
Walaa
Support Team
Posts: 14995
Joined: 21-Aug-2005
# Posted on: 10-Sep-2007 10:53:45   

Please check the LLBLGen Pro manual, section: "Using the designer -> Generating code"

scheineden
User
Posts: 7
Joined: 05-Sep-2007
# Posted on: 12-Sep-2007 04:41:31   

Hi Support,

Quick question, when I generate the code I have choose Template Bindings SD.TemplateBindings.SqlServerSpecific.Net1X

But why after it has been generated it use the SD.TemplateBindings.SharedTemplates.BackwardsCompatibility.Net1x

Another question is:

I have replaced the SD.LLBLGen DLL version 2.5 to replace our old SD.LLBLGen DLL version 1.0 Does this going to affect the application as many references have been missing?

Walaa avatar
Walaa
Support Team
Posts: 14995
Joined: 21-Aug-2005
# Posted on: 12-Sep-2007 12:38:08   

But why after it has been generated it use the SD.TemplateBindings.SharedTemplates.BackwardsCompatibility.Net1x

Would you please elaborate more on the symptoms?

I have replaced the SD.LLBLGen DLL version 2.5 to replace our old SD.LLBLGen DLL version 1.0 Does this going to affect the application as many references have been missing?

When re-generating the code using a newer version, you should change the references in your solution from the old LLBLGen runtime libraries to the new ones.