Vulcan or Cavo 2.8 ?
in [Visual Objects]
|
Prev: WIN32SDK Reference
Next: Date converting
From: jotinhaPT on 19 Jan 2008 00:50 Hi again Today I read about the Vulcan .NET for the first time. My doubt now is: what fits better my purpose of migrating Clipper apps to Windows, CAVO 2.8 or Vulcan ? I appreciate any opinions and advices from the grupou community. TIA
From: Stephen Quinn on 19 Jan 2008 03:21 > Today I read about the Vulcan .NET for the first time. My doubt now is: what > fits better my purpose of migrating Clipper apps to Windows, CAVO 2.8 or Vulcan ? If you have no VO code and you want .NET then my recommendation would be to go straight to Visual Studio (C#) If your not wanting to go .NET right now then you'll face a learning curve with VO and then later another learning curve with C# if you change your mind. You'll need to convert your Clipper code to VO (mainly a total re-write of your interface) but you should be able to adapt your business logic to VO. -- CYA Steve
From: Alwin Nederpelt on 19 Jan 2008 03:24 I think you should use Vulcan, because this is more of the feature. On Sat, 19 Jan 2008 05:50:42 -0000, "jotinhaPT" <carnaxide(a)tugamail.pt> wrote: >Hi again > >Today I read about the Vulcan .NET for the first time. My doubt now is: what >fits better my purpose of migrating Clipper apps to Windows, CAVO 2.8 or >Vulcan ? > >I appreciate any opinions and advices from the grupou community. > >TIA
From: Will Chapman on 19 Jan 2008 03:33 jotinhaPT wrote: > Hi again > > Today I read about the Vulcan .NET for the first time. My doubt now is: > what fits better my purpose of migrating Clipper apps to Windows, CAVO > 2.8 or Vulcan ? > > I appreciate any opinions and advices from the grupou community. > Good question. The future is dotnet but that doesn't mean that VO is dead. In fact, your scenario is a good corollary - most people on this list moved from Clipper to VO several years ago but some still have customers running Clipper apps (I do). I have no plans to convert any of those to VO or dotnet but on the other hand I have no plans to write anything new in Clipper. Similarly, I expect many VO apps will remain 'current' for many years ahead and many people on this ng will still be maintaining them (or at least a mix of VO and dotnet (Vulcan and/or C# - it is possible to mix in dotnet). (Note the use of the term dotnet i.e. .NET. There are a number of ways to program in dotnet and Vulcan is based on the VO language [which was based on Clipper] but because Vulcan has only just been launched, many people on this forum have already started to program in dotnet using other languages, notably C#. Many of those people would argue that you should skip VO/Vulcan and move directly to C#. I'm not so sure.) So to partially summarise, you are really running a generation behind and it could be that you could move to VO2.8 and not need to migrate to dotnet for many years. So if your objective is simply to create a Windows version of your Clipper app then VO may well be the easiest route (Vulcan is not yet fully mature and I doubt that there are any people out there who have done a Clipper -> Vulcan conversion). On the other hand, if you want to catch up that lost generation I would recommend that you consider dotnet. Both VO and Vulcan can 'read' .prg files but you are going to have to make manual significant changes to the code before it will compile. My guess is that Vulcan will be less forgiving in this regard. Perhaps the best advice I can give you, is to download a free copy of C# Express and the trial version of Vulcan (using VIDE) and just see how easily you can convert a few of your program modules and compare that with the ease that you are progressing with VO. If budget is an issue (you have bought VO2.8 and cannot easily justify the additional investment in Vulcan) and you are already progressing well with VO2.8, I would stay on that course. It will serve you well for many years to come and as your VO2.8 code would be largely compatible with Vulcan, it would be a natural starting place to jump into dotnet in the future. Hope this helps... Cheers Will -- Will Chapman Save Our Waterways www.SaveOurWaterways.org.uk
From: GeorgeNT on 19 Jan 2008 04:45
If I was at your position, I would download the trial version of Vulcan for 60 days (includes a copy of Visual Studio 2005) and download the VIDE as well. If you look at the market, the .NET is the mainstream and the Vulcan.NET is the xBase compiler for .NET environment. I aready started developping 2 applications using Vulcan.NET. It is a strong and well defined compiler. It still missing some indegration features with VS2005 but, you have the choice to use the nice VIDE as IDE. Regards George "jotinhaPT" <carnaxide(a)tugamail.pt> wrote in message news:47918fb6$0$27804$a729d347(a)news.telepac.pt... > > Hi again > > Today I read about the Vulcan .NET for the first time. My doubt now is: > what fits better my purpose of migrating Clipper apps to Windows, CAVO 2.8 > or Vulcan ? > > I appreciate any opinions and advices from the grupou community. > > TIA > |