XML Entity Specification

Posts   
 
    
BaileyK83
User
Posts: 29
Joined: 30-Dec-2006
# Posted on: 27-Mar-2007 22:14:47   

How would I go about getting an XML Specification for all the Entitys in a project

My guess would be to add some sort of task

Exactly like...

<Entity Class ="ObjectEntity" Table= "obj" > <Fields> <field Name="Name" Type="NVarChar" Size="255"> </Fields> </Entity> <Entity Class ="PersonEntity" Inherits ="ObjectEntity" Table= "objPerson" > <Fields> <field Name="Height" Type="Int" Size="4"> </Fields> </Entity>

Keep in mind my xml sucks any help would be greatly appreciated

bclubb
User
Posts: 934
Joined: 12-Feb-2004
# Posted on: 28-Mar-2007 03:00:50   

What are you going to use it for? Do the entities need to be defined exactly like this?

BaileyK83
User
Posts: 29
Joined: 30-Dec-2006
# Posted on: 28-Mar-2007 03:03:35   

I plan on using it to determine the entitys in a particular application.

No they just need to be in some sort of parseable format maybe I could even use the .lgp file.

Walaa avatar
Walaa
Support Team
Posts: 14950
Joined: 21-Aug-2005
# Posted on: 28-Mar-2007 09:35:35   

You can create your own plugin that would run in the designer. First you should check the LLBLGen Pro Manual: "Designer -> Working with plug-ins".

BaileyK83
User
Posts: 29
Joined: 30-Dec-2006
# Posted on: 06-Apr-2007 01:44:07   

I'm just now looking at all of the task/template stuff and It seems like it would make more sense and be easier to use the task/template stuff to accomplish this. Why do you suggest a plugin instead?

Walaa avatar
Walaa
Support Team
Posts: 14950
Joined: 21-Aug-2005
# Posted on: 06-Apr-2007 12:08:27   

Both can work, it depends on when do you want the output xml file simple_smile If at design time, then a plugin can do, else at code generation time, then the template\task will be the best option.