I am using llblgen 3 with some custom templates which I have just migrated from 2.6.

If I open llblgen, open my prohject and generate the code everything works fine and I get the generated code as expected.

If I run the generator for a second (or more) times I get an error message

"Code generation cycle failed"

Compilation of templates threw errors: Error CS0016, at line: 0, pos: 0: Could not write to output file 'c:\Users\brettb\AppData\Local\Temp\2D18D138-1DD2-467E-86CC-4838250611AE\LptTemplateAssembly.dll' -- 'The process cannot access the file because it is being used by another process. '

Closing down llblgen and starting again solves the problem but it is a bit annoying!

~Brett

I can't reproduce it, code generation runs fine multiple times in a row... Do you use your own task performers ?

I have my own task performer (I derived a task performer from the lpt one to support the[ProjectName] tag in the filenameFormat parameter)

I've taken all references to my task performer out but It hasn't made any difference. First run works fine, second fails.

Also I've just tested it with your standard presets and this works fine. It seems to be an issue with my tasks / presets somewhere

I think I've isolated the issue. If I remove the "debug" parameters from my task definition the problem goes away.

eg in my first .lpt I have the following

<parameter isOptional="false" name="debugBuild" defaultValue="true" /> <parameter isOptional="false" name="templateAssemblySourceFileFormat" DefaultValue="templateClassesSource.[extension]" />

Has debugging changed since 2.6?

Aha!

If you click the 'Start Generator (debug)' button in the generator configuration dialog (the middle button), you'll get a debug build automatically, so we made this easier. Do you then still run into this?

If I "Start Generator (debug)" it fails on the second attempt.

This is without those parameters in my .task file.

BrettBailey wrote:

If I "Start Generator (debug)" it fails on the second attempt.

This is without those parameters in my .task file.

OK, we'll see if we can reproduce this.

Reproduced...

(edit) fixed in next build.

Thanks!

I don't suppose you would consider adding support for the [ProjectName] tag in the filenameFormat parameter? Its a trivial bit of code but would mean I could get rid of my custom task performer

~Brett

BrettBailey wrote:

Thanks!

I don't suppose you would consider adding support for the [ProjectName] tag in the filenameFormat parameter? Its a trivial bit of code but would mean I could get rid of my custom task performer

~Brett

That's already done, use [containerName]

When you use groupusage as visualization mechanism (everything in 1 project) it's the project file. If you use groups as 1 project per group, it's the group name (as multiple projects are created)

Thanks Frans

I' don't really follow you in terms of project groups and visualization (are you talking task groups llblgen projects / vis studio projects?)

on the plus side I replaced all my [projectName] with [containerName] and I got the results I was expecting so thanks!

BrettBailey wrote:

Thanks Frans

I' don't really follow you in terms of project groups and visualization (are you talking task groups llblgen projects / vis studio projects?)

Groups in the designer. You can group entities in the designer, and generate per group code as a vs.net project instead of all entities in a single project.