Vulcan or Cavo 2.8 ?
in [Visual Objects]
|
Prev: WIN32SDK Reference
Next: Date converting
From: Geoff Schaller on 27 Jan 2008 20:49 Will, > No need to ask them, I've read most of their posts. Vulcan is > far more advanced than half finished and I expect that the key > missing parts (VoAdo is one that impinges on me - the VS > integration hasn't affected me) will be with is very soon. No. It will be months yet. Probably many months. The other factor that holds me back is the inability to migrate VO windows binaries to VS forms. Without this I cannot consider a Vulcan migration and I suspect most VO'ers are in a similar place. OLE is a show-stopper, yes, but windows to forms is a killer. I simply cannot re-write the 100's of forms that I have. Geoff
From: Will Chapman on 28 Jan 2008 03:41 Geoff Schaller wrote: > Will, > >> No need to ask them, I've read most of their posts. Vulcan is >> far more advanced than half finished and I expect that the key >> missing parts (VoAdo is one that impinges on me - the VS >> integration hasn't affected me) will be with is very soon. > > No. It will be months yet. Probably many months. I doubt that it will be many months for most of what I need. What is likely to be several months - I guess - is the Compact Framework and that is a key ingredient for me. But I can get around that in a number of ways and so time is not a show stopper. As I said above, the first stage for me is Vo2Ado and I suspect that is quite close. > The other factor that > holds me back is the inability to migrate VO windows binaries to VS > forms. Without this I cannot consider a Vulcan migration and I suspect > most VO'ers are in a similar place. OLE is a show-stopper, yes, but > windows to forms is a killer. I simply cannot re-write the 100's of > forms that I have. The forms aren't an issue with me and, as a result, whilst I accept that it must be an issue for you, I still don't grasp what all the fuss is about. Either Vulcan can offer a solution to your needs or it can't. If it can't you clearly have no option other than using - as I know you are - C# or another language. But just as my portfolio of apps is clearly more easily vulcanised than yours, then I would expect others to have similar degrees of varying vulcanisability. The only way to tell - as far as moving an app from VO2 to dotnet is concerned - is surely to taste it and see. What I can't see is how anyone can categorically tell someone else that they should ignore Vulcan and just accept that C# is the way forward. There are just too many factors involved: individual developer language skills (some can learn new syntax more easily than others); extent of reliance on legacy code in Clipper/VO; nature of legacy data and whether practicality of moving from .DBF to more modern schema (I, for example, have a load of small traders using my epos app - what a nightmare that would be to change them from .dbf); etc, etc. Cheers -- Will Chapman Save Our Waterways www.SaveOurWaterways.org.uk
From: Gary N Keefe on 28 Jan 2008 21:01 I would check out CULE.Net. It takes a Clipper app as source and then converts it to a C# solution. Gary Keefe "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 > >
From: Mullet on 29 Jan 2008 00:55
Use Advantage database server. I used it with Clipper and .Net simultaneously for years. It took me about half a day to move my Clipper application to Advantage if I am remembering correctly. Most of that was trying to figure out which compile flags to set. It has been a while but I remember very few code changes. After you have your Clipper application running on Advantage you can access your database with the Advantage ADO.Net data provider. An added advantage is no more index corruptions. If you are planning to move off of Clipper move directly to C# or VB.Net. You will need to rewrite your app anyways regardless of which tool you use. VO and Vulcan are both rewrites. Move to a tool that is actively supported by Microsoft. You won't regret it. "jotinhaPT" <carnaxide(a)tugamail.pt> wrote in message news:47925a02$0$27833$a729d347(a)news.telepac.pt... > I'm familiar with Java, which is, as far as I know, similar to C#. > About choosing a new environment, the big questions are the ability to > deal with my databases, how easy it is to develop an entire application > and the future as a programming language. For example, about Visual > Objects, there are few resources on the net, looks like that it will end > in a near future. > VO or Vulcan, as far as I know, can use some parts of the Clipper code, > without having to rewrite them, but if neither VO or Vulcan are the best > choice, I'm open to move to other language. > |