From: Ginny Caughey on 20 Nov 2005 17:14 It's the first item on the page - Reflector for .NET. There add-ins you can download that convert the C#, VB, etc. to files and even create Visual Studio projects from them. -- Ginny <jmespinosabaviera(a)yahoo.com> wrote in message news:1132524642.258363.59860(a)g43g2000cwa.googlegroups.com... > >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. >
From: BillyBob on 20 Nov 2005 17:30 It is the Vulcan stuff that is theoretical. As far as I'm concerned Vulcan is still vapourware. I'm sure it is "wonderful" but I haven't seen it and don't really care to. I converted VO to C# long ago. The IL to C# is very possible. <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: Don Caton on 20 Nov 2005 17:55 "jmespinosabaviera(a)yahoo.com" <jmespinosabaviera(a)yahoo.com> wrote in message news:1132519735.658278.191620(a)f14g2000cwb.googlegroups.com: > What is MSIL ? Do you mean I can convert automatically from VO to > Vulcan and then automatically from Vulcan to Visual Basic ? Please give > me information about this. It is an "intermediate" language, sort of like a high level assembly language that is processor-independent. All .NET languages emit IL code, which is then translated into native code by the "Just-In-Time" compiler for the platform you're running on (e.g. Windows, Windows CE, Linux). It's conceptually similar to Java, except that there only one language that generates Java bytecodes, whereas any .NET language can generate IL code. It is possible to convert IL code back to a high level language, just as it is possible to convert raw assembly language code back into a high level language, or to convert Clipper tokenized code back to Clipper source code uaing a tool like Valkyrie. However, you're not going to get back the original source code. While there is always a 1:1 translation from high level code to low level code, the same is not true going the other way. A low level code sequence in IL (or native assembly code for that matter) can translate into a potentially infinite number of high level language constructs. Reflector is an interesting tool to examine IL code. It can display the raw IL code of any .NET assembly, as well as translate it into C#, VB and Delphi code. But it's only a guess (and I've often seen it guess wrong), it isn't the original source code. If you've ever used Valkyrie to decompile Clipper code, things are very similar with decompiling IL code. -- Don
From: Karl Faller on 21 Nov 2005 03:11 Ginny, >It's the first item on the page - Reflector for .NET. There add-ins you can >download that convert the C#, VB, etc. to files and even create Visual >Studio projects from them. i wonder, sometime ago we discussed if it's possible to make a tool to convert C# code into Vulcan code to ease the "reading" of the ton of C# samples for Xbasers. IIRC, first Don thought it to be easy, but then found some hair in the soup <g>. Karl
From: jmespinosabaviera on 21 Nov 2005 06:12
Thanks to all who are responding. This seems to bring other (bad) consequences: If MSIL cab be brought back to the original code, then a hacker can obtain the source code and steal your software, I mean make some changes and the hacker can sell it as his own software, or just manipulate the routine checking for a dongle in the usb port, thus allowing piracy. From what I know I do not run this risk with my VO application. Is this MSIL code which is distributed to the customers, allowing free access to the source code ? |