Upgrading to V2.0

Posts   
 
    
hplloyd
User
Posts: 191
Joined: 29-Oct-2004
# Posted on: 06-Sep-2006 17:51:47   

Hi,

I have some custom templates I put together for V 1.2005 and that was all fine...

I am now truing to port these to the new V2.0 engine (At this stage the templates will still be used to generate .NET 1.1 code)

I am a little stuck :

I use the same templates for both SQL Server and Firebird albeit with a few differences...

I have created 3 .templatebinding files (Shared, SQL server and Firebird) and that is all fineand I can open up Template Studio 2.0, see my template binding files listed in the drop down ,and can open the individual templates for editing....

My problem comes with the next step ... I can see that I need to generate a .tasks file - How do I do this - at the moment I am trying to do it in a text editor!! whgich is painful to say the least

Also, I assume I also need to generate a .preset file, which as far as I can see is very similar to a .tasks file....

Can anyone point me in the right direction, I have read the SDK reference manual which has helped me get this far but now I am stuck

Regards

Huw

Otis avatar
Otis
LLBLGen Pro Team
Posts: 39786
Joined: 17-Aug-2003
# Posted on: 06-Sep-2006 19:09:02   

You don't need .tasks files. You can add an existing task to an existing preset (like the task which consumes a TDL template) and set the task's parameters in the preset editor in llblgen pro.

You can also edit .tasks files in vs.net. This gives you intellisense, which is very easy. Just load the .xsd for tasks (which is located in the Tasks\XSDs folder) into vs.net and your own .tasks file, and you've instant intellisense simple_smile (in vs.net 2005 that is). This is the reason why there's no tasks editor in templatestudio.

Frans Bouma | Lead developer LLBLGen Pro
hplloyd
User
Posts: 191
Joined: 29-Oct-2004
# Posted on: 06-Sep-2006 23:55:02   

Thanks, I found as you suggested that editing my task file in vs.net using the XSD file, highlighted all the errors I had and once fixed, it all works as expected....