This one is Free/Trail/Paid Versions with multiple language support. NET Core (see the tutorial)Īdditional features in DEBUG builds (for the devs) Hyperlink-based type/method/property navigationĪssembly metadata explorer (feature walkthrough) Search for types/methods/properties (learn about the options) Whole-project decompilation (csproj, not sln!) Reflector.McppLanguage This add-in extends Reflector with a Managed C++ language. NET Reflector provided as a language add-in. Reflector.DelphiLanguage The Delphi view that is used inside. NET assemblies stored in SQL Server 2005 (Yukon) databases. Our Linux/Mac/Windows PowerShell cmdlets in this repositoryįeatures Decompilation to C# (check out the language support status) Reflector.SQL2005Browser This add-in allows to browse. Our dotnet tool for Linux/Mac/Windows - check out ILSp圜md in this repository Our ICSharpCode.Decompiler NuGet for your own projects Our Linux/Mac/Windows ILSpy UI based on Avalonia - check out Our Visual Studio Code Extension repository | marketplace Our Visual Studio 2017/2019 extension marketplace Our Visual Studio 2022 extension marketplace To enable, activate the setting "Enable Decompilation Support". Go to Tools / Options / Text Editor / C# / Advanced and check "Enable navigation to decompiled source"Ĭ# for Visual Studio Code ships with decompilation support as well. In Visual Studio 2019, you have to manually enable F12 support. Since this is an older question and a lot has happened since asked I figure I would add a couple links to decompilers out there that may be of use to others looking for a solution.Ĭompletely Free & according to Git README.md as of current:Īside from the WPF UI ILSpy (downloadable via Releases, see also plugins), the following other frontends are available: Visual Studio 2022 ships with decompilation support for F12 enabled by default (using our engine v7.1). You could find someone domestically, but it would cost you more no doubt (although with the sagging dollar and poor job market you never know. A lot of it depends on what 3rd party components you used (beyond AbsoluteDatabase) and if you made any Windows API calls directly in your application.Īnother completely different option would be too look for an off shore team to maintain the application. Language migration is easier then library migration. NET Reflector and File Disassembler reverse the IL to C#. I believe they have a Delphi Win32 migration path to WinForms. You will still be using the VCL, but you can use C# instead of Object pascal.Īnother similar solution would be to port it to Oxygene by RemObjects. NET (which will be pretty easy, except for the embedded DB, unless they have a. There are others, I just can't find them right now.Īnother option would be to upgrade to a more resent version of Delphi for. NET Reflector, you can see what Microsoft used when writing the ReadXml method of the DataSet, or what they did when reading data from the configuration files.NET Reflector is also an excellent way to see the best practices for creating objects like HttpHandlers or configuration handlers because you get to see how the team at. Here is a Swedish tool that works on the same CodeDOM principle to go from Delphi to C# (and a number of other languages). I would assume the tools that go the other direction will work the same (requiring a lot of editing). I have seen a couple code DOM's that attempt to convert from Delphi to C#, but that doesn't address the library issue.ĬodeGear (formally Borland) has a tool for going from C# to Delphi that works OK. Personally I would suggest you stick with Delphi, maybe just upgrade to a new version. I am not aware of any automated tools for making that conversion. Is there an automated tool that will do the legwork of converting the code base to C#, leaving me to concentrate on the conversion on any non-standard components? I'm using an embedded database component called AbsoluteDatabase which is BDE compatible and using standard SQL throughout, and a native Delphi HTML browser component which can be swapped out with something from the Microsoft world. I'm wondering if I should jump to a more familiar stack. Many of my users are moving to Vista which may run the app in compatibility mode or may have GPF problems depending on how their PC is configured by their IT department, so I have to do some maintenance on the application. Its syntax is too different from my 'day job' languages of Java/Ruby so it takes me longer to get into the groove of writing new code, plus it is so old I have not used many interfaces so the code is not managed which seems ancient to me now! Although Delphi has served me very well in the past I now only use it for this one application and find my skills with the language diminishing. I maintain an old PC-only application written in Delphi 7.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |