We have a licensed version for 2.x and are using v 2.5 for generating the llbl files. Since, v 2.5 does not support oracle 11g, we are planning to migrate to v 3.0. We used the migration template provided by llbl http://www.llblgen.com/documentation/3.0/Designer/Migratingv2xProjectTov3.htm We followed the steps provided in the readme.txt to migrate from v 2.5 to v 3.0 but are getting the error message, have attached the screenshot of the error message, Task 'sd.tasks.base.consumerlpttemplate' aborted the process.

Please let us know if anybody has faced this issue.

Download v2.6 from the customer area, use the conversion template with that version. v2.6 can load your v2.5 project just fine, and is able to run the conversion template

Thanks, we are able to generate the llbl files. But, we are getting the error as "The type or namespace ...... could not be found (are you missing a using directive or assembly reference" Could somebody please help us out here?

When are you getting the error - when you try to generate the code from the LLBLGen project file, or when you try to compile the generated code ?

Which namespace is it complaining that it cannot find ?

Thanks

Matt

We are able to generate the code from LLBL but are getting the error during compilation. There are around 18 namespaces missing or with error. Some of them are ElementCreatorBase, IElementCreator2, DynamicRelationBase.

Sounds like you are missing the reference to the LLBLGen runtime library SD.LLBLGen.Pro.ORMSupportClasses2.0.dll. You may need to point the reference in the generated project to the file on your machine.

Matt

We are referencing SD.LLBLGen.Pro.ORMSupportClasses.NET20.dll file. Is this not the correct one? Please tell where can we get the new file if this is not a valid file. We are using .net 3.5 version for our application development.

Yes, you need SD.LLBLGen.Pro.ORMSupportClasses.NET20.dll, but the version 3. Please make sure you are using the correct version of the assemblies. If necessary, remove the references and add them again.

Where can we get the version 3 dll? Can you please provide us the path?

When you install any version of LLBLGen Pro, you get the dlls to show in the Reference Window (.NET) of visual studio.

So all you have to do is to right click on the specified project in VS. In Solution Explorer right-click the References node and select Add Reference. In the .NET tab you should find all LLBLGen Pro dlls. Just pick the correct version.

That did resolve some of the errors...we were able to bring down the error count from 15 to 7. Thanks for your help. We are getting problem in dataaccessadapter, it says return type must be 'System.Data.Common.DbConnection' to match overridden member 'SD.LLBLGen.Pro.ORMSupportClasses.DataAccessAdapterBase.CreateNewPhysicalConnection(string)' return type must be 'System.Data.Common.DbTransaction' to match overridden member 'SD.LLBLGen.Pro.ORMSupportClasses.DataAccessAdapterBase.CreateNewPhysicalTransaction()' 'SD.LLBLGen.Pro.ORMSupportClasses.EntityBase2.SetRelatedEntity(SD.LLBLGen.Pro.ORMSupportClasses.IEntity2, string)' is inaccessible due to its protection level

Can somebody help us here?

You are still referencing v2.x runtime library assemblies, you have to reference the v3.x ones of the version you're generating code with (I think you generated with v3.1, so you have to reference v3.1's ormsupportclasses dll)

We rebuild the whole process and then, we get the following error. Cannot implicitly convert type 'SD.LLBLGen.Pro.ORMSupportClasses.IValidator' to '<project name>.DAL.EntityClasses.ValidatorEntity'. An explicit conversion exists (are you missing a cast?) Does this error make any sense to anybody?

Please show us the code that refers that error. Do you have an entity named Validator?

Yes, we have an entity called validator. The generated code this.Validator = validator; throws error in the llbl file.

ULPSR wrote:

Yes, we have an entity called validator. The generated code this.Validator = validator; throws error in the llbl file.

In What Entity are you putting that code (this.Validator = validator)? I guess this.Validator is an ValidatorEntity, but validator is an IValidator, that's why the compilation error, coz there is a property in all entities called Validator, but maybe you have a related entity in this that points to a ValidatorEntity.

Is there any chance you change the related entity name Validator to something else (like TheValidator)?

I hope that makes sense. If you still run into troubles, please post you llblgenproj file so we can test it.

Thanks this issue is resolved. We are getting another issue while compiling, this should be the last in the list I hope. Really appreciate your helping out. 'PricingTool.DAO.PricingToolDataAccessAdapter.CreateNewPhysicalTransaction()': return type must be 'System.Data.Common.DbTransaction' to match overridden member 'SD.LLBLGen.Pro.ORMSupportClasses.DataAccessAdapterBase.CreateNewPhysicalTransaction()'

ULPSR wrote:

Thanks this issue is resolved.

What was it? We are curious

ULPSR wrote:

We are getting another issue while compiling, this should be the last in the list I hope. Really appreciate your helping out. 'PricingTool.DAO.PricingToolDataAccessAdapter.CreateNewPhysicalTransaction()': return type must be 'System.Data.Common.DbTransaction' to match overridden member 'SD.LLBLGen.Pro.ORMSupportClasses.DataAccessAdapterBase.CreateNewPhysicalTransaction()'

Weird. I still think you are not referencing the correct assemblies (v3.0 or v3.1). Please double check that please.

This is a related thread for similar weird errors, not sure if it helps but please check it: http://www.llblgen.com/TinyForum/Messages.aspx?ThreadID=19157

I checked all the references but could not locate the error. Still searching for solution, I rebuilt the whole solution and pointed manually each reference to the new dll files. Still no success.

ULPSR wrote:

I checked all the references but could not locate the error. Still searching for solution, I rebuilt the whole solution and pointed manually each reference to the new dll files. Still no success.

Do a textual check in the csproj files XML (load them into notepad for example), and check whether the references are ok. Also set 'specific version' to true in vs.net for the reference, to make sure the reference is OK.

If you didn't add any custom code to the generated code, you can also decide to simply re-generate the code in an empty folder.

For v2.x -> 3.x migration, be sure you look into the feature for field ordering (see manual!) to keep field ordering the same as in v2

What's the return type of: PricingTool.DAO.PricingToolDataAccessAdapter.CreateNewPhysicalTransaction() ??

This is the code scippet throwing error: protected override IDbTransaction CreateNewPhysicalTransaction() { if (_transaction == null) { return base.CreateNewPhysicalTransaction(); } else { return _transaction; } }

Please return DBTransaction not IDBTrasaction. To match the overidden function in the base class.

Changed the Idb to Db and removed those two errors but getting another error now: <projectName>.DAL.DatabaseSpecific.DataAccessAdapter' does not contain a definition for 'SchemaNameUsageSetting' Throwing error in following piece of code: base.SchemaNameUsageSetting = SchemaNameUsage.Clear; base page refers to "<PName>.DAL.DatabaseSpecific" Compared the code in the dataadapater file and found that we are missing the following code, this file is generated using the llbl. Do we need to replace this manually or is it something that has changed with v 3.1? public SchemaNameUsage SchemaNameUsageSetting { get { if(_schemaNameOverwrites!=null) { return _schemaNameOverwrites.SchemaNameUsageSetting; } else { return SchemaNameUsage.Default; } } set { if(_schemaNameOverwrites!=null) { _schemaNameOverwrites.SchemaNameUsageSetting = value; } } }

Instead DataAccessAdapter has SchemaNameOverwrites property of type SchemaNameOverwriteHashtable.