Hi,

I've added some tasks to an existing preset to create some additional Visual Studio projects. Whenever I run the code generator it fails on the task to create a VS project by consuming an Lpt template:

Could not find cached filenames in the task cache. Giving up.

Please see the attached screen shot of the generator output. I have created a template ID and added the template file to the template binding. The designer shows True for the File Exists column for the new template.

I followed one of the stock Entity Framework templates and just renamed accordingly.

The task also fails if I give it an existing templateID.

Please could you advise where I may be going wrong here.

Which version of LLBLGen are you using? Could you please share a repro project with your templates/tasks?

Thank you for the quick response.

Walaa wrote:

Which version of LLBLGen are you using? Could you please share a repro project with your templates/tasks?

LLBLGenPro Version 3.5

I've attached a zip file with my tasks and tempates which should go here: C:\Program Files (x86)\Solutions Design\LLBLGen Pro v3.5\Frameworks\Entity Framework Unzip here should extract to folders

A project targeting Entity Framework v5 and using my SD.EntityFramework.v5.DbContextCodeFirst.preset should produce the issue I am having.

Why are sharing the entire templates and tasks folders? Did you change/customize any of the default/defacto files? If so please specify the changes otherwise, please point to the files we need to use from the files you just shared.

Thanks.

(Edit) You can also try to set requiresCleanCache="true", on the TaskGroupPreset.

Walaa wrote:

Why are sharing the entire templates and tasks folders? Did you change/customize any of the default/defacto files? If so please specify the changes otherwise, please point to the files we need to use from the files you just shared.

Thanks.

(Edit) You can also try to set requiresCleanCache="true", on the TaskGroupPreset.

I zipped up the Entity Framework folder from the LLBGenPRo installation folder - I have added my templates to that structure. I only have 1 new preset as named in my last post. Are you saying I should be putting my custom templates elsewhere? I had put them on a network share and moved them as I thought this might be the problem.

Btw I did try the requiresCleanCache but I got the same message.

Maybe it would help if you could elaborate on what the message means. The fact that even an existing template id does not work in the task I have added, would seem to indicate that something is not quite right with the template. Only obvious thing is that I do not have any VB.NET templates defined in the template binding I created.

PS SD.EntityFramework.v5.DbContextCodeFirst.preset - open this preset to get the name that shows in the dropdown list of the Code Generator dialog. If you create a new project targeting EF v5 - add single table from Northwind and use the preset you should get a project with the same message - hopefully.

Thank you for your help.

I don't understand the VSNet Project task you have on the first task group on that preset. Which files do you want on that project?

The VSNet project task is supposed to be the last in the group after some file generation tasks (so the project has some files into it.

daelmo wrote:

I don't understand the VSNet Project task you have on the first task group on that preset. Which files do you want on that project?

The VSNet project task is supposed to be the last in the group after some file generation tasks (so the project has some files into it.

Thank you! You just solved my problem. I was trying to build the tasks up step by step. As I've not created templates before this seemed to be the easiest way to go about it. I added an AssemblyInfo step to the task and now the custom step works and generates a project file.

Please close this thread. Thank you again for the excellent support that comes with LLBLGen Pro - it is second to none!

PS The error message I got is somewhat amusing as most software doesn't "give up". If the message said that files are needed that might have been more useful - a cache seems to imply something not getting initialised. Any how a little knowledge goes a long way.