When generating the code for the GUI I get always 6 Error CS0246 "Unable to find the type or name in the namespace 'EntityFieldDefinition' (Is any using directive or assembly reference missing?)" The target is Adapter .Net 2.0, C# and SQL Server 2005. All the general code is OK, but I get an empty GUI directory

Any idea where the error can be? I'm a licenced user evaluating it for widespread adoption. Thanks,

Jose

Hi Jose,

Those templetes haven't been ported to v3.0. Maybe it's due to that. I will try to reproduce the problem and see where is it.

Sorry for the late response. We are porting the templates so they would be usable in V3. We will post back shortly when they are done.

Regards,

No problem, we can wait, we are testing right now with v.2.6. Nice lovely product I must say

I have had similar issues. But I didnt had to do much with changing the templates to work with 3.0. Only thing I had to change was to remove assembly references as per the SDK for 3.0 and use includeOnly="true" in the templatebindings file

The messages in the thread http://www.llblgen.com/TinyForum/Messages.aspx?ThreadID=18167 is close enough

Thanks Naveen Adding the includeOnly="true" to the templates in the templatebinding improved the execution Right now the FolderCreators TaskGroup works fine. The FileCreators is still giving a NullReferenceException No code created so far (even the debug file has only the references)

We'll keep trying

I include the stack trace

-----[Core exception]--------------------
   en SD.LLBLGen.Pro.LptParser.DotNetTemplateEngine.CallTemplateEmitter[TElement](Assembly compiledTemplatesAssembly, String templateID, Dictionary`2 parameters, StreamWriter outputWriter, TElement currentElement)
   en SD.LLBLGen.Pro.GeneratorCore.CodeGenerationEngineBase.EmitOutputToFile[TElement](TElement currentElement, String destinationFilename, Boolean failWhenExistent, Assembly compiledTemplatesAssembly, String templateID, Dictionary`2 parameters, Boolean isPartOfSet, String outputDescription)
   en SD.LLBLGen.Pro.GeneratorCore.CodeGenerationEngineBase.EmitOutput(Dictionary`2 parameters, String fullPath, String templateID, Assembly compiledTemplatesAssembly, EmitType emitTypeToPerform, String filenameFormat, Boolean failWhenExistent)
   en SD.LLBLGen.Pro.LptParser.DotNetTemplateEngine.Perform(IGenerator executingGenerator, ITask taskDefinition, Dictionary`2 parameters)
   en SD.LLBLGen.Pro.ApplicationCore.CodeGenerationMetaData.Tasks.Task.PerformElement(IGenerator executingGenerator, LogNode parentNode)
   en SD.LLBLGen.Pro.ApplicationCore.CodeGenerationMetaData.Tasks.TaskGroupElement.Perform(IGenerator executingGenerator, LogNode parentNode)
   en SD.LLBLGen.Pro.ApplicationCore.CodeGenerationMetaData.Tasks.TaskGroup.PerformElement(IGenerator executingGenerator, LogNode parentNode)
   en SD.LLBLGen.Pro.ApplicationCore.CodeGenerationMetaData.Tasks.TaskGroupElement.Perform(IGenerator executingGenerator, LogNode parentNode)
   en SD.LLBLGen.Pro.ApplicationCore.CodeGenerationMetaData.Tasks.TaskGroup.PerformElement(IGenerator executingGenerator, LogNode parentNode)
   en SD.LLBLGen.Pro.ApplicationCore.CodeGenerationMetaData.Tasks.TaskGroupElement.Perform(IGenerator executingGenerator, LogNode parentNode)
   en SD.LLBLGen.Pro.ApplicationCore.CodeGenerationMetaData.Tasks.TaskGroup.PerformElement(IGenerator executingGenerator, LogNode parentNode)
   en SD.LLBLGen.Pro.ApplicationCore.CodeGenerationMetaData.Tasks.TaskGroupElement.Perform(IGenerator executingGenerator, LogNode parentNode)
   en SD.LLBLGen.Pro.GeneratorCore.Generator.RunTasks(String rootNameSpaceToUse, String destinationRootFolder, String groupName)
   en SD.LLBLGen.Pro.GeneratorCore.Generator.Start(ITaskGroup tasksToExecute, Project projectDefinition, Language languageToUse, Platform platformToUse, List`1 templateBindingsToUse, String templateGroupToUse, ApplicationConfiguration configurationSettings, String rootNameSpaceToUse, String destinationRootFolder, CodeGenerationCycleOutputType outputType)
   en SD.LLBLGen.Pro.GeneratorCore.Generator.Start(ITaskGroup tasksToExecute, Project projectDefinition, CodeGenerationCyclePreferences preferences, ApplicationConfiguration configurationSettings)
   en SD.LLBLGen.Pro.Gui.Classes.GuiController.PerformRunCodeGenerationCycleAction(ITaskGroup toExecute, CodeGenerationCyclePreferences codeGenerationCyclePreferences, HashSet`1 entitiesToUse, HashSet`1 spCallsToUse, HashSet`1 typedViewsToUse, HashSet`1 typedListsToUse, HashSet`1 valueTypesToUse, LogNode& tasksResultLog)

The templates run over the v2.6 object model, which is completely different from v3's. I highly doubt it you will get any result from the v2.6 templates on v3 . We're nearing beta for the templates for v3. Stay tuned.

Otis, We went live (been almost 8 months now) with almost no issues with 2.6 and we are trying to use 3.0. Out of curiosity but, would there be some kind of template conversion mechanisms from 2.6 to 3.0 (like the template we could use to convert 2.6 project to 3.0 project)?

Guys, we are almost done with this (a day or two). Please stay tunned...

Hi all... any kind of updates?

Daelmo -- Any note on the templates?

David is just finishing off these templates. They should be published soon.

Matt

Hi Guys,

I'm attaching the ported templates to this post. I tested it with some Northwind examples. Please test them and give us some feedback.

This version is the same you used in v2.6, it's just ported to v3. I have some improvements in mind to be added soon to the templates. Please tell me what do you think.

(Edit) sorry for the late response.

I tried it briefly with Northwind and it worked perfect. Some minor errors in 2.6 version (eg. subsets not always correct) are solved and it seems much faster than v.2.6 too. Pretty good work. ;-) I'll get into harder testing next week and give you my feedback. Thanks for your support

Good they worked. I'm working in a new version. Please let me know if you want something else or you have some feedback

daelmo wrote:

Good they worked. I'm working in a new version. Please let me know if you want something else or you have some feedback

I'm doing some work on the templates you posted, should I stop with that and wait for those? I think I'm done with it in a few hours (fixing an issue as well in the templates) so I can mail them afterwards, so we both aren't doing unnecessary work

I found some relation errors on AdventureWorks database (OK with 2.6 version) Restricted test: Only generated entities from tables (no views, no sp) - Generation seems OK - Converting VS project to web app gives four "duplicated tag" errors - ProductInstances on ViewRelatedToUnitMeasure.ascx - BillOfMaterialInstances on ViewRelatedToProduct.ascx - CurrencyRateInstances on ViewRelatedToCurrency.ascx - SalesOrderHeaderInstances on ViewRelatedToAddress.ascx - Digging up, those relations are duplicated, but some other are missings (compared to the 2.6 version) - Once removed the duplicated elements, the code compiles without errors

I'll be waiting for the next posted version

Let's focus on the v3.0 version, the v2.6 version is left as-is. I'll run a basic AdventureWorks test.

(edit) I see your problem appearing in the v3 version indeed, a small bug in the template.

(edit) fixed the problems. Will attach a new batch for testing in a new post.

I've fixed some issues and cleaned up some code as mapping stuff wasn't necessary. Please use the attached batch to see if it fixes your problems.

Nice bug fixes. I was working in something similar but we can work on top of these now

I've uploaded a new version, to the customer area, v3.0 templates section. I also ported the templates to SelfServicing. It was not a lot of work, some templates required some if statements, but that was mainly it.

Enjoy (and again thanks to David for doing the porting! )

Hi, Finally we are ready to try the templates in a limited production environment. We'll have some budget to add functionality to the templates (and, of course, share it), and are open to suggestions (and freelancers offers. Spanish speaking a must ;-) Suggestions so far are: - Usage / personalization examples storage procedure calls data validation authorization integration with reporting tools (crystal, Reporting Services?) others? - Webservices generation templates - ...

One thing which would be good too is to use the v3.0 settings system to enable/disable features instead of custom properties, what it uses now.

Work with Daelmo in progress. New features in progress so far: - WCF 3.0 Web Services templates - v3 settings systems through conf. file - Grid export to Excel

Any futher suggestion?

Nothing leaps to mind from me but I've not had a lot of involvment in this thread - I'm sure the other chaps will add anything if they think of it.

Matt