ECO IV
Dmitriy Nagirnyak
http://biz.yahoo.com/bw/070905/20070905005360.html?.v=1
What a disappointment here:
What has changed for C# developers?
CodeGear RAD Studio 2007 provides a basic level of support for C# development.
You can create new projects, edit
them and compile them. More advanced features like visual design, modeling,
and ECO that were available in past
versions are no longer available in RAD Studio 2007.
We knew that, but... anyway... I cannot believe there will be no ECO in C#
Personality of RAD Studio :(
So C# developers have 4 choices about ECO:
1. Chose VS IDE and wait ECO to support Visual Studio.
2. Move to Delphi.NET.
3. Stay with ECOIII and BDS 2006.
4. Choose another persistance framework.
Which way do you choose, guys?
Please fill in the small survey for me. I don't know if I want to publish
the results. Tell me about it.
http://dcportal.argocomputing.com.au/CompleteForm.aspx?form=4:53
Cheers.
Dmitriy Nagirnyak
http://dcportal.argocomputing.com.au
http://dnagir.blogspot.com
David Compton
We have the same dilemma as you (well almost - we don't use c# but we do
develop using ECO/WinForms/DevExpress - as well as ASP.Net).
As yet we haven't decided which way to go - probably stay with ECOIII and
BDS 2006 in the short term and then evaluate using ECO with Visual Studio.
It is disappointing not to be able to move to .Net 2.0 at this stage.
We would probably choose to move to Delphi.Net (i.e. from WinForms to VCL.Net)
if DevExpress would support VCL.Net - or even if there were other comparable
3rd party components available for VCL.Net.
Whatever we do we are faced with a considerable amount of rework to move
to .Net 2.0. I will investigate products like TurnSharp for converting our
Delphi code base to c# if the ECO\Visual Studio combination proves attractive.
Regards,
David Compton
mailto:david.w...@gmail.com
Peter Morris
To migrate from C# to Pascal you can
01: Create an EcoModeler project
02: Import the EcoPkg file
03: Recreate the state machine diagrams (these are not imported)
04: Change C# property types such as int and bool to Pascal types.
05: Generate code
You'll need to re-implement the methods in the generated source.
If you have your model in EM already then you can open the C# model in the
Pascal edition and skip steps 1+2.
Your other option is to migrate to EcoModeler and VS2005.
Pete
Pawel Pawlow
> Your other option is to migrate to EcoModeler and VS2005.
>
We choose this one. Can't wait for it actually.
Pawel
Dmitriy Nagirnyak
> As yet we haven't decided which way to go - probably stay with ECOIII
> and BDS 2006 in the short term and then evaluate using ECO with Visual
> Studio.
Thanks. We probably will also stay with .NET 1.1 for now...
Not sure. All depends from CapableObjects team. When will they release ECO
for VS.
If they will not, the way to go will probably be NHibernate.
> It is disappointing not to be able to move to .Net 2.0 at this stage.
>
Really, really!
> We would probably choose to move to Delphi.Net (i.e. from WinForms to
> VCL.Net) if DevExpress would support VCL.Net - or even if there were
> other comparable 3rd party components available for VCL.Net.
>
Your dilema is "ECO or 3rd party comntorls"?
I would prefer ECO + 3rd parties :)
Really one thing keeps (personally) me with Borland (CodeGear) IDE is ECO.
No other reasons. Sorry for saying that. I'm just beeing honest :)
Even DevExpress doesn't want to support CodeGear products developing 3rd
party components.
Who then will?
No choise of IDE plug-ins: BDS is "isolated" IDE. Almost not extendable by
available components.
I know only one or two free IDE extenstion for *Delphi* IDE, thousands for
VS.
Ok. My point is clear.
ECO is the one wothwile thing. I don't care about CodeGear IDEs because *for
.NET* MS VS is the best choise.
Sorry for being too honest :)
Dmitriy Nagirnyak
> To migrate from C# to Pascal you can
Yes. We can migrate to Delphi, but probably not existing projects.
Will you?
> Your other option is to migrate to EcoModeler and VS2005.
Yes. I suppose you already use VS+EcoModeler.
Or do you also write Delphi.NET?
Peter Morris
> Yes. I suppose you already use VS+EcoModeler.
> Or do you also write Delphi.NET?
For .NET I have always preferred C#
Pawel Pawlow
I agree - do you know where I can buy some shares in CapableObjects? :-)
Pawel
Dmitriy Nagirnyak
>> ECO is the one wothwile thing...
> I agree - do you know where I can buy some shares in CapableObjects?
> :-)
Not sure about shares :)
But I can only say "THANK YOU ECO TEAM!"!
I really hope for more frequent releases of ECO.
...and dreaming a bit-imagine ECO would be an Open Source :)
Cheers.
Dmitriy