VOPS
in [Visual Objects]
|
From: Geoff Schaller on 20 Nov 2005 16:17 Ginny, > Of course you're entitled to your beliefs, but the fact is that Vulcan > converts VO code to .NET today. It isn't complete yet, but it is nearly > complete. Only some code converts over cleanly and a lot needs tweaking. But code alone isn't all. There are the editors and binaries etc. The constructs that can't convert automatically will need a conversion tool. I am waiting (now forced to wait) for that point. Until then its even too soon for you to say how successful it will be. > (For you to hold the beliefs that you do, I have to wonder if you > even tried Vulcan while you were part of VOPS.) Well you'd be wrong. But as of a month ago or so there was still too much not available for me to convert an existing application. Yes, I could write new code from scratch and use the appropriate work arounds and I am content with that. The crunch for me is when its "ready" to convert an existing application. We're not there yet. > Once you have MSIL, you can convert that to C# (or VB or Delphi) in 5 minutes if you want to. (Of course you may believe differently. <g>) I'm not sure I'm interested in MSIL nor why you raise it. The important factor for using Vulcan will be the ease of conversion from VO. It can't be perfect, we all understand that, but the degree of difficulty is important. > rewrite. But why are you waiting until next year to do so? Time <g>. We are still heavily involved in substantial clipper conversions to VO and these projects are keeping us busy. We had hoped Vulcan would have been available sooner to evaluate for other projects we have but some can't wait so they are being developed in C# right now. Geoff
From: jmespinosabaviera on 20 Nov 2005 16:34 >What Ginny is saying, is that you could theoretically compile >Vulcan >to IL and than reverse engineer it back to C#. This would in effect >allow >you to convert all your code to C#. But this conversion from MSIL to visual basic or to #C is "theoretically possible" or is "really possible", I mean is there really a tool to do this job or you and Ginny is meaning that this tool could exist.
From: Ginny Caughey on 20 Nov 2005 16:55 http://www.aisto.com/roeder/dotnet/ -- Ginny <jmespinosabaviera(a)yahoo.com> wrote in message news:1132522469.527345.83540(a)g44g2000cwa.googlegroups.com... > >What Ginny is saying, is that you could theoretically compile >Vulcan >>to IL and than reverse engineer it back to C#. This would in effect >> >allow >>you to convert all your code to C#. > > But this conversion from MSIL to visual basic or to #C is > "theoretically possible" or is "really possible", I mean is there > really a tool to do this job or you and Ginny is meaning that this tool > could exist. >
From: Gary Stark on 20 Nov 2005 17:03 jmespinosabaviera(a)yahoo.com wrote: >>What Ginny is saying, is that you could theoretically compile >Vulcan >>to IL and than reverse engineer it back to C#. This would in effect >allow >>you to convert all your code to C#. > > > But this conversion from MSIL to visual basic or to #C is > "theoretically possible" or is "really possible", I mean is there > really a tool to do this job or you and Ginny is meaning that this tool > could exist. It ?? There are quite a few. Perhaps this would be a good time for you to investigate the DotNet environment more deeply, and especially the need for code obfuscators. :) -- g. Gary Stark gstark(a)RedbacksWeb.com http://www.RedbacksWeb.com
From: jmespinosabaviera on 20 Nov 2005 17:10
>http://www.aisto.com/roeder/dotnet/ Sorry, but here I have not found a tool to convert from MSIL to Visual basic code. I have found by searching google, a tool (called salamander) but it seems that it can convert MSIL generated by VB to VB code, and MSIL generated by #C to #C code. What I do not know if these tools can convert from MSIL to a language different from the language by which they were generated and still create "clean" code, I mean code that can be understood. |