Re: Any IDE/tools support Clipper source code with function jump

On Jul 8, 3:35 pm, Johan Nel <johan555.nel...@xxxxxxxxxxxxxxx> wrote:
Geoff,

Yes, well one of the reasons you need such extensive support is because
of the product's immaturity, but there you go. If you are happy with
that then cool but it is not a place for newcomers.

No, by support I mean direct answers to some of my questions and guidance....

Well you obviously don't play in the right circles. And you probably
don't attend user group meetings, belong to the partner program (which
is free, unlike Vulcan's) or deal with MS forums

FYI I do attend the local sadevelopers monthly meetings (which is almost
purely MS...) and belongs to the partner programme etc...

Deciphered: meaning you don't know where to look or frequent appropriate
MS forums. Heck I belong to the Advanced installer forum, sql server
forums the Help and Manual forum and more. I don't find people berating me.

Good for you.

I'm not sure this is relevant. I don't happen to believe that xHarbour
is even remotely useful in this scenario because it isn't a genuine path
to the Dot net framework. Vulcan could or may be and that was the focus
of your post. Perhaps if the correspondent doesn't want to go the full

That is not the point, you decided to attack my message related to
Vulcan, but you did not even comment on the xharbour one.  In light of
Vulcan more on par with C# in context of a .NET language, it was just
strange(bad blood)...

book then xHarbour may be at least a windows alternate but Vulcan is
something else and requires something else. Just remember, Vulcan has
also just lost its principal architect and engaged another. When a whole
dev environment relies on one new and already over-busy individual it
doesn't say a lot about the total support environment around the
product. The part-time approach to the product is way below par for what
it needs to finish its evolution. Clearly that isn't going to happen and
Vulcan will park itself into the background as yet another interesting
but less than commercially useful compiler.

Well (almost) no one know what the future holds... My experience was
that it took me 4 months (part-time basis) to totally rewrite my VO code
in .NET using Vulcan (500+ forms, 400+ reports, 300+ graphs) with full
OLAP functionality between those forms, reports and graphs).  In your
context that probably translates to a couple of million lines of code
which you "keep" in VO, I didn't...

So maybe it will get parked I don't know and you don't know, but it
stands that it allowed me to get into .NET (almost) without pain.  Even
if it gets parked, I still have the .dll's that I can integrate into any
other .NET language at that stage.

Johan

Thanks Ross, I'll try xMate with Clipper and Harbour MiniGUI as well.





Thanks Johan and Geoff, for all your discussions.

I'm a new comer to dot Net,with experience in C,C++ and Java, no
experience with xBase Language.

The legacy system is written by one 'perfect' person about 15 years ago
(may be much older). It is in CA-Clipper 5.2 with some functions
written in assembly language, also the source code doesn't have even a
line of comment/documentation. The customers do have big problem
maintain this. They are spending lots of money to call the original
author in for any problems.
I've had a look of xHarbour and Vulcan.Net when the project started.
Don't know where to start with xHarbour/Vulcan.Net. Not sure if we can
convert it successfully using xHarbour/Vulcan.Net in six months with
one developer. So we decided to move on to rewrite it in .Net in C#
and move the database to SQL. Using the source code as documents and
send emails to the original author for questions.

Like Geoff said, the customers like to use MS products to avoid this
'maintenance' problem happen again in the future. They want a
'Windows' program easy to maintenance, a database with backup and
rollback. This pointed me to dot net for the huge amount of users,
good community/documents support, generally. MS make things better
over times (C#,WPF,Silverlight). They are willing to pay for MS
products to reduce the future maintenance cost. Maybe Vulcan.Net has
good developer support but the small users base is the fact. I do have
problem getting support from DevForce EF/DevExpress.

Maybe I should post my questions earlier to here/xHarbour/Vulcan.Net
communities. You are right Johan ,if I can convert most of the things
with Vulcan.Net like all the business process and libs, I won't go for
dot Net.

In the scope, the customers have plans for a web UI so we adopt
C#,MSSQL,DevForce EF and DevExpress, develop using Visual Studio. With
the possible use of WPF/Silverlight like Geoff said.

I agree with "WPF is the future", Geoff. I'm not prefer MS products
personally. I like GNU/Linux and FreeBSD.

Could I say Vulcan.Net is much better for a developer has experience
with xBase language? I'm not saying who is right or wrong. Only which
one is much suitable for a case.

Regards,
Vincent
.

Relevant Pages

  • Re: Any IDE/tools support Clipper source code with function jump
    ... don't attend user group meetings, belong to the partner program or deal with MS forums ... That is not the point, you decided to attack my message related to Vulcan, but you did not even comment on the xharbour one. ... When a whole dev environment relies on one new and already over-busy individual it doesn't say a lot about the total support environment around the product. ... I still have the .dll's that I can integrate into any other .NET language at that stage. ...
    (comp.lang.clipper)
  • Re: Any IDE/tools support Clipper source code with function jump
    ... by support I mean direct answers to some of my questions and guidance.... ... unlike Vulcan's) or deal with MS forums ... Vulcan, but you did not even comment on the xharbour one. ... other .NET language at that stage. ...
    (comp.lang.clipper)
  • Re: Any IDE/tools support Clipper source code with function jump
    ... And you probably don't attend user group meetings, belong to the partner program or deal with MS forums ... I don't happen to believe that xHarbour is even remotely useful in this scenario because it isn't a genuine path to the Dot net framework. ... Perhaps if the correspondent doesn't want to go the full book then xHarbour may be at least a windows alternate but Vulcan is something else and requires something else. ... When a whole dev environment relies on one new and already over-busy individual it doesn't say a lot about the total support environment around the product. ...
    (comp.lang.clipper)
  • Re: various objects in my VB6 project - Calling IUnknown
    ... legacy support for EXEs is an order of scale beyond ... "Language Stability" enjoyably employs structure. ... But I'm not black and white on the matter of migration changes. ...
    (microsoft.public.vb.general.discussion)
  • Re: Architectural support for programming languages
    ... microarchitectural support in processors for operating systems to make ... The language used will match the programs, ... were adding architectural features to take their share of new market ... and run them under and OS written in C and on architecture with all ...
    (comp.arch)