Forum:  Custom Templates

Thread:  Problem with customised TDLInterpreter


Stevenn (User)   Posted on: 25-May-2016 16:50:47.
Hi

i have been playing around with the templates and have now progressed onto the TDLInterpreter. LLBLGen Pro version: v4.2. Build: May 4th, 2016.
I made some changes (one line at the moment) and then copied the new DLL (debug) and .pdb to the LLBLGenInstallFolder\TaskPerformers but when i run the designer and try and generate my project it raises an exception:
Code:

Exception information.
=============================================================
LLBLGen Pro version: v4.2. Build: May 4th, 2016

Exception details:
=====================
Message: Could not load file or assembly 'SD.LLBLGen.Pro.TDLInterpreter, Version=4.2.0.0, Culture=neutral, PublicKeyToken=ca73b74ba4e3ff27' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
Source: SD.LLBLGen.Pro.TaskPerformers
Stack trace:
at SD.LLBLGen.Pro.TaskPerformers.CodeEmitter.CreateAndInitTDLInterpreter(String templateID, String templateBindingDefinitionName, List`1 parseResult)
at SD.LLBLGen.Pro.TaskPerformers.CodeEmitter.Perform(IGenerator executingGenerator, ITask taskDefinition, Dictionary`2 parameters)
at SD.LLBLGen.Pro.ApplicationCore.CodeGenerationMetaData.Tasks.Task.PerformElement(IGenerator executingGenerator, LogNode parentNode)
at SD.LLBLGen.Pro.ApplicationCore.CodeGenerationMetaData.Tasks.TaskGroupElement.Perform(IGenerator executingGenerator, LogNode parentNode)
at SD.LLBLGen.Pro.ApplicationCore.CodeGenerationMetaData.Tasks.TaskGroup.PerformElement(IGenerator executingGenerator, LogNode parentNode)
at SD.LLBLGen.Pro.ApplicationCore.CodeGenerationMetaData.Tasks.TaskGroupElement.Perform(IGenerator executingGenerator, LogNode parentNode)
at SD.LLBLGen.Pro.ApplicationCore.CodeGenerationMetaData.Tasks.TaskGroup.PerformElement(IGenerator executingGenerator, LogNode parentNode)
at SD.LLBLGen.Pro.ApplicationCore.CodeGenerationMetaData.Tasks.TaskGroupElement.Perform(IGenerator executingGenerator, LogNode parentNode)
at SD.LLBLGen.Pro.GeneratorCore.Generator.RunTasks(String rootNameSpaceToUse, String destinationRootFolder, String groupName)
at SD.LLBLGen.Pro.GeneratorCore.Generator.Start(ITaskGroup tasksToExecute, ApplicationConfiguration configurationSettings, Language languageToUse, Platform platformToUse, List`1 templateBindingsToUse, String templateGroupToUse, String rootNameSpaceToUse, String destinationRootFolder, Project projectDefinition, CodeGenerationCycleOutputType outputType)
at SD.LLBLGen.Pro.GeneratorCore.Generator.Start(ITaskGroup tasksToExecute, CodeGenerationCyclePreferences preferences, ApplicationConfiguration configurationSettings, Project projectDefinition)
at 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, HashSet`1 tvfCallsTouse, List`1 vsNetProjectsCreated, LogNode& tasksResultLog)

Inner exception: <null>


I am not signing the assembly. Is there somewhere that i need to change the references because i couldn't find anything?

Thanks

Steven
Otis (LLBLGen Pro Team)   Posted on: 26-May-2016 09:47:16.
You have to compile all dlls in the code generator solution together, so reference the tdlinterpreter you changed from the taskperformers project.

It's however not recommended to alter the tdl interpreter if you don't have to: use .lpt templates instead.


Stevenn (User)   Posted on: 26-May-2016 10:31:48.
Thanks Otis, that sorted it out.