version 1.0.2005.1 final (self-servicing) VS2005 asp.net 2.0

hiya,

I have some generated code (which wasn't generated by llblGenPro) that allows me to do the usual stuff on an object "create/ save/ delete". I don't like the way that it's generated, it has too many manual steps.I'd rather use llblgenpro for the entire project. However, I don't have too much left to do, so I'd rather incorprate llblgenPro for the remaining work.

I have added some fields to the underlying database.I want to use llblGenPro to grab and persist thse new fields, instead of using the old framework to generate them.

Is it perfectly feasible to to the following?

<pseudoCode> call "Update" on the NON llblGenPro generated object THEN call "Update" on the llblGenPro entityCollection that deals specifically with the newly created fields?

</pseudoCode>

I hope the above doesn't sound too confused.

please let me know.

yogi

Of course you can. You can migrating step by step in a MiddleTier using the LLBLGenPro framework.

Isn't it a bit too confusing to have 2 frameworks in your app? I mean, I'm flattered that you like our work more than another framework but you have to be realistic here. You said you don't have much work left in this project, so unless you don't want to maintain the code with the other framework for a long time, wouldn't it be better (for consistency) to have all code on that other framework for this particular case? Otherwise the app uses two different frameworks which might confuse the person who has to maintain the application in the coming years ("which framework do I have to use to get this field updated?"... )

ta for the replies folks.

Frans, I suppose you are right.

cheers, yogi