|
|
|
Forum Guru
 
Group: Forum Members
Last Login: 2010-03-29 14:48:07
Posts: 71,
Visits: 303
|
|
Hi, I have an web app in c# builder 2006 (.net1.1, EcoIII) I would like to change to .net3.5, (Eco for VS) but I have doubt, to migrate to ECOIV I have to do again the model, because now the model is in Together, EcoIV has ModelMaker, I read in some thread that EcoV will have a new class design, the doubt I have to re-done the class model again, is there some idea to do tools to migrate from EcoIII or EcoIV to EcoV?, when we can hope to watch EcoV in action?
any info is welcome.
regards
Frank
|
|
|
|
|
Supreme Being
Group: Administrators
Last Login: 2010-11-30 12:17:13
Posts: 1 230,
Visits: 1 382
|
|
The new designer will use the same format for saving models as the Together designer (ecopkg-files).
There will be an import tool for EcoModeler models (both model and diagram). EcoIII users will be able to import the model, but we are not planning to import the Together diagrams.
We plan to start field testing Eco5 in Q3.
/Jonas Hogstrom [CapableObjects]
|
|
|
|
|
Forum Guru
Group: Forum Members
Last Login: 2009-06-27 19:05:52
Posts: 64,
Visits: 353
|
|
| Is there any advice for those of us starting new ECO4 projects to make the ECO5 transition easier? For example, will it be easy to split classes into partial classes after import into ECO5's class designer? - Joe Hendricks
- Joe Hendricks SoftwareRunners | Life On Glen Cove
|
|
|
|
|
Supreme Being
Group: Administrators
Last Login: 2010-11-30 12:17:13
Posts: 1 230,
Visits: 1 382
|
|
We hope to make the upgrade as painless as possible. Worst case is to generate the new code and manually move the hand written code from the old classes to the new classes. I did this with an internal model, and for ~20 classes, it took maybe half an hour to move the code (after I had fixed a couple of codegen bugs :-) Now that the model import is almost done I'll start to look at the upgrading of EcoModeler generated code.
/Jonas Hogstrom [CapableObjects]
|
|
|
|