Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.clipper.visual-objects > #8942
| Path | csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail |
|---|---|
| From | "Wolfgang Riedmann" <wriedmann@gmail.com> |
| Newsgroups | comp.lang.clipper.visual-objects |
| Subject | Re: Where do we go from here? Vulcan.net status |
| Date | Fri, 5 Feb 2016 08:41:40 +0100 |
| Lines | 32 |
| Message-ID | <dhj21nF6ji2U1@mid.individual.net> (permalink) |
| References | <210c1aeb-e39e-4235-a2b0-3797ef4aad5f@googlegroups.com> |
| Mime-Version | 1.0 |
| Content-Type | text/plain; charset=iso-8859-1 |
| X-Trace | individual.net ijaprCZn0UD79oX8rSBZkAN8Cmuf4y4/Ek7+A4mYECqTEkPz0= |
| Cancel-Lock | sha1:K7AyLucB4hNd5JxF0miDBqpBuRg= |
| User-Agent | XanaNews/1.18.1.6 |
| Xref | csiph.com comp.lang.clipper.visual-objects:8942 |
Show key headers only | View raw
Hi John, if you have a lot of VO code (like I), then of course actually Vulcan.NET is the best way to go. Now, several members of the last Vulcan.NET development team have built a new company Xsharp with a new product called X#, and you should look at this product now. They have rebuilt an Xbase compiler from scratch, using a new Microsoft tecnology, and X# actually supports more .NET features than Vulcan.NET, but is missing compatibility libraries from VO, and in this early stage is also missing support for the "classic" VO datatypes like array, codeblock, etc. But they promise to make the libraries open source and also give out the compiler sources to they subscribers, so I think there will be a relative good code investment protection. My recommendation would be to continue with Vulcan.NET because it is a mature and good working product, and look at X#. If Vulcan.NET development continues, you can continue with it, but if it comes to a stop, you can continue with X#. Personally, I cannot afford that VO code will not be compilable in the .NET world, and so I'm using both. Wolfgang --
Back to comp.lang.clipper.visual-objects | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Where do we go from here? Vulcan.net status jjgregg007@gmail.com - 2016-02-04 16:45 -0800
Re: Where do we go from here? Vulcan.net status "Wolfgang Riedmann" <wriedmann@gmail.com> - 2016-02-05 08:41 +0100
Re: Where do we go from here? Vulcan.net status D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2016-02-05 12:38 +0100
Re: Where do we go from here? Vulcan.net status "Wolfgang Riedmann" <wriedmann@gmail.com> - 2016-02-07 17:39 +0100
Re: Where do we go from here? Vulcan.net status "Danilo Giuliani" <softdevo@tiscali.it> - 2016-02-07 19:41 +0100
Re: Where do we go from here? Vulcan.net status "Wolfgang Riedmann" <wriedmann@gmail.com> - 2016-02-08 06:31 +0100
Re: Where do we go from here? Vulcan.net status Robert van der Hulst <rjvanderhulst@gmail.com> - 2016-02-05 04:30 -0800
Re: Where do we go from here? Vulcan.net status chris.pyrgas@gmail.com - 2016-02-06 01:43 -0800
Re: Where do we go from here? Vulcan.net status "Marc Verkade [MITCon]" <marc@mitNOSPAMconDELETE.nl> - 2016-02-10 16:29 +0100
Re: Where do we go from here? Vulcan.net status b®ian_@g®afx_soft.com <brian@grafxsoft.com> - 2016-02-05 06:35 -0800
Re: Where do we go from here? Vulcan.net status D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2016-02-08 13:50 +0100
Re: Where do we go from here? Vulcan.net status "Jamal Assaf" <someone@example.com> - 2016-02-11 11:42 -0500
Re: Where do we go from here? Vulcan.net status Carlos Rocha <JDOTCarlosDOTRochaDOT1@SpiedBy.gmail.com> - 2016-02-11 20:20 +0000
Re: Where do we go from here? Vulcan.net status D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2016-02-12 00:28 +0100
Re: Where do we go from here? Vulcan.net status "Jamal Assaf" <someone@example.com> - 2016-02-12 16:57 -0500
Re: Where do we go from here? Vulcan.net status "Wolfgang Riedmann" <wriedmann@gmail.com> - 2016-02-13 11:39 +0100
csiph-web