Community

We have now bought CodeBreeze after the evaluation period expired, and I need to know something.

Is it envisaged to add functionality to allow for target tags (or something like target tags) to be applied at Field level (as opposed to Entity level).  I'd like to add additional information about the fields that make up my entities, and have the code generate differently based on this information.  Eg, in the default implementation (using CSLA) you get a Get[Entity] method generated on the collection class, which returns from the database a collection of all records.  I'd like to be able to amend the template to create a Get[Entity]by[FieldName] method for every field in the entity that has a certain "target tag".

Please advise if something like this will be in v1.1 or soon thereafter.

Any word on this yet?  Please advise asap, as I want to kick myself for not picking up on this one while evaluating CodeBreeze.  We have bought it now, but this is the one feature that is causing us to still use our inhouse-developed code generator, and I'd really like to make the switch to CodeBreeze.

I know I've already emailed you, but I'll go ahead and post this. 

public static List<string> GetListFilteredByTargetTagCommaDelimitedString(CodeBreeze.Business.BusinessEntity entity, string targetTagKey)
    {
        string commaDelimitedString = entity.Tags[targetTagKey].Value;
        string[] array = commaDelimitedString.Split(',');
        List<string> getObjectByFieldList = new List<string>(array);

        return getObjectByFieldList;
    }

I have a target tag called GetObjectByField so I want to be able to generate mutliple values selecting that object back so I delimit it with a comma.  I just return a list of strings that I handle in the code template.  I pass in the entity and the target tag.

In the code template, you would point to your template helper class and you would do this:

List<string> objectListByField = GetListFilteredByTargetTagCommaDelimitedString(entity, "GetObjectByField");

From here just loop through this and handle it in your template.  Granted you can handle this different ways, here is an example.

Hope this helps.

That's a good approach Joseph.  Target tags are limited to Entities/Wrappers only and only one value so you need to come up with your own parser for multiple values and you're on the right track there.

I'm not sure if multiple tag values is going in any time soon as it's a little lower on the priority list.  One of the "high" items is to place a plug-in point into the target-tag subsystem so that you can auto-create them using a source of your choice (perhaps a foreign key list or something).  This one is not coming out in 2.0 but it will be out in a subsequent release.

Thanks again for your support on these forums,

Miguel A. Castro
CodeBreeze Chief Architect - SteelBlue Solutions