hiya,

I have downloaded the "Northwind example 1 (C# version)" I want to be able to add validatorLogic etc.

I believe that: 1) I should do this thru the llbGenPro GUI. (instead of manually hacking the genarated code) 2) the changes will be reflected in the newly generated code, after I re-generate the project.

As far as I can see, the: 1) Vis studio project is included in the download, 2) .lgp project that actually generated the code is NOT included.

Am I correct?If so, how can I obtain the .lgp project that generated the code?..I think it would be of great value to any newstarts..

cheers, yogi

yogiberr wrote:

hiya,

I have downloaded the "Northwind example 1 (C# version)" I want to be able to add validatorLogic etc.

I believe that: 1) I should do this thru the llbGenPro GUI. (instead of manually hacking the genarated code) 2) the changes will be reflected in the newly generated code, after I re-generate the project.

As far as I can see, the: 1) Vis studio project is included in the download, 2) .lgp project that actually generated the code is NOT included.

Am I correct?If so, how can I obtain the .lgp project that generated the code?..I think it would be of great value to any newstarts..

cheers, yogi

Currently, validation logic is implemented in code using IValidator and IEntityValidator. The code generator creates property validators (implementations of IValidator) for you that are not overwritten when code is regenerated. This allows you to completely customize your validation code without fear of losing it each time code is regenerated. If you wish to do entity-level validation, you will need to manually implement IEntityValidator. You can find more information in the docs at Using the generated code->Validation per field or per entity. The .lgp file is not required to validate data in the framework.

I believe in-designer validation is planned as a future enchancement, but am not sure.

Jeff...

heh heh, cheers. That's the trouble with this product, it's already doing so much of the grunt work that I'm getting greedy and believing that it'll do everything..given time, it probably will

yogiberr wrote:

heh heh, cheers. That's the trouble with this product, it's already doing so much of the grunt work that I'm getting greedy and believing that it'll do everything..given time, it probably will

I know what you mean. I'll let Frans address whether/when in-designer validation will happen. It'd be nice, at least for simple logic.

Jeff...

Thanks for helping out, Jeff .

Designer validation definition logic is scheduled for v2.0. It's still undefined in what form it will be done, as I have to do some tests with the DSL integration toolkit for vs.net 2005, though it will be productive as in: define rules on the type if the rule has to be defined on the type, and you otherwise define rules for instances, which are done like today, in validator objects.

Otis wrote:

Thanks for helping out, Jeff .

Designer validation definition logic is scheduled for v2.0. It's still undefined in what form it will be done, as I have to do some tests with the DSL integration toolkit for vs.net 2005, though it will be productive as in: define rules on the type if the rule has to be defined on the type, and you otherwise define rules for instances, which are done like today, in validator objects.

DSL = Domain Specific Language?

Yes They have released a beta of the SDK for a domain specific language, and the theory is that you can do a lot of things with it, including totally custom designers.

I'll see if I can get a demo somewhere this week at teched europe

Otis wrote:

Yes They have released a beta of the SDK for a domain specific language, and the theory is that you can do a lot of things with it, including totally custom designers.

I'll see if I can get a demo somewhere this week at teched europe

Interesting. I know the base theory surrounding DSLs, and think there's a lot of potential there for various applications, but I really don't know much. I'm interested to see how it's applied here.

Jeff...

Yeah, it has huge potential, it's just how much work needs to be done to get things up and running. I mean: writing a parser for a language... it can be hard, though if they supply a LR(n) parser generator for example, so all you have to do is supply a grammar and hook up the handlers per grammar rule to some methods, it's pretty ok

(I fiddled around a bit with the SyntaxEditor control, which allows similar functionality on a lower scale, so that's an option too)

Otis wrote:

Yeah, it has huge potential, it's just how much work needs to be done to get things up and running....

Hey Otis,

nice to revive this thread now that DSL Tools are in the VS2005 SDK.. have u played around any further? We've developed a small DSL for UI creation as a prototype, and are very happy with the template engine, validation framework, etc etc. The key pieces missing are a visual designer for model specification and first class support for template code editing - these are all on schedule for an updated release during this March.

Have you plans to integrate fully with DSL Tools - is this an active project for LLBLGen Pro? We're looking at it as a serious contender for tight integration into our development processes, and are keen to hear your plans/thoughts..

cheers nick

We've decided to wait for it to mature a bit, so v2 of llblgen pro won't use DSL tools. We expect v3 to be using it, which will be our tool for Linq. Though that's long term planning (2007+)