Reverse Engineer .NET Exporter -- 2

@customizedata

I have already recovered code for many executables .. Please share with me the executable along with the supported dlls so that i could check and guide further. Once code is recovered and compiled flawlessly in Visual studio then we can enhance it to cater for these requirements • a start time and end time parameter that define the export window • a list of one or more phone extensions to filter the recordings further. Have been working in .Net since 2008 Looking forward to have a chat with you to discuss further.

@anirudhat

Losing the source to a working exporter is fixable — a .NET WinForms binary decompiles cleanly, and the SDK calls you actually depend on will still be intact in the IL. I'd start by running the executable through ILSpy/dnSpy (plus de4dot if it's obfuscated) to recover the C# project, rebuild it in Visual Studio until it compiles byte-for-byte equivalent, then strip out the dialog and route the same SDK export routine through a console entry point — parameters like /start, /end and /ext with a comma-separated extension list, validated and logged. I'll keep the SDK interop untouched so behaviour stays identical, test it against your recorder server, and hand over the .sln with a toolchain doc plus a walkthrough session. Available to start immediately.

@Herculesz

Hi, This project requires precise reverse engineering of a .NET Windows Forms app to a command-line tool, with a key challenge being accurate decompilation and clean refactoring of the original executable to preserve SDK integration and export logic. I usually structure such efforts by first establishing a reliable build and debug environment, then progressively cleaning decompiled code while maintaining functional parity. My experience with complex C# systems and codebase reviews aligns well with this. The main risk is ensuring the refactored tool handles parameterized exports correctly without UI context, which I address by separating input parsing from SDK interaction. I typically design clear documentation and build instructions to enable seamless hand-off and future maintenance. Thanks, Hercules

@devendrathakur12

Hi, I’m a Senior Software Engineer with 20+ years in .NET and Windows software development. I have gone through your specific requirement for decompiled Windows utility. I built something like this for business clients, with 20+ years across .NET platforms. I would use dnSpy or ILSpy for recovery rather than rebuilding from scratch because the existing executable preserves the recorder SDK workflow. I will recover the WinForms executable into a compileable Visual Studio project and trace its SDK calls. The command line layer will accept the time window and extension filters while keeping recording export unchanged. And I’ll separate SDK access from argument parsing so future changes do not touch the recovered workflow, at least that is where I would start. Relevant .NET and Windows software samples I can send. Which recorder software and SDK version does the executable currently use? Can you provide the working executable for decompilation and the recorder server environment? Does the current utility create any config files or registry entries that must remain compatible? Free for a quick call this week? Or answer those three and I’ll map out the recovery first. Dev Singh

@shrec

Hi, I understand the goal here is to recover the existing .NET exporter and turn it into a reliable command-line tool without changing the underlying recorder SDK workflow. I can work from the existing executable to recover and clean up the code, then refactor the application so it accepts the start/end time and one or more phone extensions as command-line parameters. The existing process of fetching recordings and saving them locally can remain intact while removing the Windows Forms dependency. I’d also document the development environment, compiler settings, decompilation tools, and build process so you can reproduce the project yourself later. The final handoff would include the compile-ready source, updated executable, parameter documentation, and walkthrough. The one-month timeline fits the scope well. Best, Ivane

@vishal1145

Your recorder SDK integration will fail silently if the decompiled code loses the original COM interop signatures or marshaling attributes. That means dropped recordings with zero error logs. Quick questions - does the SDK use a licensed DLL that enforces machine binding? And are you running this on Server 2016+ where .NET Framework versions might conflict with the decompiled target? Here is the architectural approach: - .NET DECOMPILATION: Use dnSpy to recover IL code with preserved metadata, then rebuild in Visual Studio 2022 targeting the same framework version your recorder SDK requires. - COMMAND-LINE REFACTOR: Replace Windows Forms entry point with a console app that parses start/end timestamps and extension arrays, validates input before SDK calls to prevent partial exports. - BUILD DOCUMENTATION: Package the solution with a Docker-based build script and dependency manifest so you can replicate the toolchain without hunting down compiler versions. I've reverse-engineered legacy telecom integrations for two VoIP providers where the original vendors went dark. Let's schedule a 20-minute screen share so I can inspect the SDK documentation and confirm the interop layer won't break during decompilation.

@aspnetlancer

Hi, I have more than 20 years of experience in developing .Net applications. I can decompile your application and rewrite it as a console app. Looking to hear from you.

@toriquldev123

Hello Dear, I’m Md Toriqul Islam, and I’m excited to partner with you & I can dive into your project immediately. I’m an experienced .NET developer with 10+ years of experience. I have rich experience in Windows applications, .NET, reverse engineering, decompilation, SDK integration, and command-line tool development. I am skilled in C#, .NET, Windows Forms, CLI applications, SDK/API integration, executable analysis, refactoring, and Visual Studio build environments. I understand you want to recover the existing utility, refactor it into a command-line tool with time and extension filters, while preserving the recorder SDK workflow. I’m ready to start immediately and can complete the project within your one-month timeline. Looking forward to hearing from you. Best regards, Md Toriqul Islam

@sharmin283

Let me begin by sharing my empathy. I know how challenging it can be to restore applications without their original source code. As an experienced full-stack developer, I've overcome similar hurdles in numerous projects throughout my career. My expertise includes both traditional web development and modern AI engineering, making me well-versed in the intricate processes of understanding, decompiling, refining, and recompiling software like your .NET exporter. Moreover, I'm highly proficient with tools like Visual Studio and other suitable IDEs. So you can rest assured that I'll establish a clean, repeatable development environment and compile-ready source code for your project, as well as provide detailed instructions so you can maintain it on your own in the future. Furthermore, my proficiency across multiple platforms (including popular CMSs like WordPress) and backend automation will prove invaluable in streamlining your .NET exporter to operate purely from the Windows command prompt. With your remote access to the recorder server and my rigorous testing methodologies, we can ensure efficient integration and a successful hand-off within the stipulated timeframe. Choose me - together we will secure a desirable outcome for your project!

@ganeshrasekar

I can do it.

@deepthi2889

Hi, I am a Full stack developer in Microsoft technologies. I have vast experience on working on projects that suits your requirement exactly. You can check the reviews in my profile regarding the same. My area of expertise is web application development (Web API, ASP.Net web forms, MVC, classic ASP), Web Development ( Blazor, Angular) , web services (SOAP & RESTFul), MySql & Sql Server as back end (through stored procedures). I have 10 years of experience as a full time software developer. Kindly contact me, lets discuss your requirements.

@raphael602

Dear Client, I can perfectly reverse engineer the existing .NET WinForms exporter, recover and clean up the code, and refactor it into a reliable command-line utility. I have a few questions before starting: 1. Do you still have the original executable and all required recorder SDK DLLs/libraries? 2. What .NET Framework/.NET version was the existing application built with, if known? 3. What input/output format do you expect for the date/time and extension parameters? I can start working on your project right away. I look forward to the opportunity to work for you. Sincerely, Raphael

@longngoc2307

==== Hi - Truong here ==== ".NET EXPORTER REVERSE ENGINEERING" — you need the old recorder export utility recovered, rebuilt, and converted from WinForms into a reliable command-line tool. I’d first decompile and map the existing workflow, especially the recorder SDK calls, then clean the recovered C# into maintainable source. The CLI will accept start/end times and one or more extensions, while preserving the existing recording export behavior and local file handling. Can you provide the current executable and the recorder SDK/version so I can confirm the decompilation and integration approach? Looking forward to work with you.

@KarthikTechCon

Hello, I’m Karthik, a .NET developer with over 15 years of experience in software development and reverse engineering. I can help you decompile your existing .NET Windows Forms application and refactor it to run from the command prompt, meeting your specified requirements. My approach: 1. Decompilation & Cleanup: I will thoroughly decompile the executable, clean up the code, and ensure it's maintainable. 2. Command-Line Refactor: The new build will accept start and end time parameters and filter by phone extensions while retaining the original workflow. 3. Development Environment Setup: I will set up a repeatable development environment, including Visual Studio and necessary tools, to enable you to rebuild the project independently. 4. Documentation: You will receive fully compiled source code, an updated command-line executable with parameter syntax, and step-by-step build instructions. I aim to complete this within one month, followed by a hand-off session to guide you through the process. Looking forward to collaborating! Best, Karthik

@carlosd178

Hello, As a result of a detailed review of your project requirements, I fully understand that you need an existing .NET Windows Forms export utility recovered from the executable, cleaned up, and refactored into a command-line tool while preserving the current recorder SDK workflow. I have experience with C#, .NET, Windows desktop applications, reverse engineering/decompilation, Visual Studio, CLI utilities, SDK integration, and software documentation. In my opinion, the key challenge is recovering a stable, buildable codebase without changing the proven export logic. I would first decompile and reconstruct the project, identify SDK dependencies and configuration, then replace the WinForms input flow with command-line arguments for start time, end time, and one or more extensions. I would also set up a repeatable Visual Studio build environment, document the required decompilation/compiler toolchain, and verify the rebuilt executable directly against your recorder server. I have a couple of quick questions. • Is the current executable built for .NET Framework or .NET Core/.NET? • Do you still have the recorder SDK DLLs, documentation, and any configuration files used by the existing utility? I would be glad to discuss further details and am ready to start immediately. Best regards, Carlos

@juanestebana17

Hello! I understand you need a decompiled .NET Windows Forms export utility rebuilt into a command-line tool that accepts a start time, end time, and one or more phone extensions, while preserving the recorder SDK workflow and local file output. I have spent the last several years solving exactly this type of problem in .NET Core, Software Architecture, C Programming, and Microsoft software environments, including reverse engineering legacy Microsoft Office-era tooling, recovering compile-ready code from decompiled assemblies, and refactoring applications into clean command-line utilities for repeatable builds. I’m ready to get started, and I’m confident we can make this project a success and deliver it to a high standard. I’m committed to ensuring everything is completed professionally, efficiently, and exactly according to your requirements. Best regards!

@Tanmoy236

Warm Hello! I can reverse-engineer your existing .NET WinForms exporter, recover and clean the code, then refactor it into a reliable command-line utility while preserving the recorder SDK workflow. I have over 9 years of experience in this field. Here's how I can help: • Decompile, reconstruct and organise the existing .NET application into compile-ready source • Replace the WinForms UI with start/end time and extension parameters • Integrate and test recorder SDK calls, export handling and local file output • Provide clear CLI syntax, validation, error handling and logging • Set up a repeatable Visual Studio/toolchain environment with build documentation and hand-off I can target completion within your one-month window with milestone-based delivery. Can you provide the existing executable and recorder SDK/version details? Is the current utility built on .NET Framework or modern .NET?

@mahads31

With years of experience in software development and a comprehensive skillset including .NET, C# Programming, and C++ Programming, I am more than equipped to reverse engineer and refactor your existing export utility. Dealing with complex requirements and transforming them into scalable, efficient systems is a specialty of mine. In the context of your project, I understand the criticality of not just cleaning up recovered code but also ensuring the final build is compatible with your existing setup. I can undertake this task seamlessly by setting up a repeatable development environment with the appropriate tools, compilers, Visual Studio (or another suitable IDE) settings. On top of delivering fully decompiled and compile-ready source code as well as an updated command-line executable, I will provide step-by-step build instructions and notes on the required toolchain so you can easily replicate the process in future. Trustworthy integration testing is crucial functionality-wise for your system. Given remote access to your recorder server during development, I’ll ensure zero disruptions with an ample time frame for testing. And perhaps most importantly, my emphasis on communication and transparency will come into effect during our hand-off session wherein I'll walk you through the code and build process to ensure complete clarity on what I've delivered and how you can take it forward. Let's get started on making your ideas into concrete business solutions!

@mandavcon

As an experienced developer with a decade's worth of work and a passion for creating efficient and user-friendly software, I'm confident that I can not only meet but exceed your expectations for this project. My in-depth knowledge of .NET, .NET Core, and C# Programming - especially in working with decompilation and refactoring - make me a perfect fit for your task of reverse engineering the .NET Exorter. Throughout my career, I have regularly adapted to new technologies and kept up with the latest industry trends just as your project demands. This way, I've been able to remain ahead of the curve in terms of software architecture and development. I'm confident that this same spirit of continuous learning will enable me to successfully decompile and refactor your utility while preserving its functionality but improving the workflow by introducing command line capabilities. Finally, my commitment to thorough documentation provides for proper hand-off to ensure you can confidently use and maintain this application even afterwards. Not only will I provide fully decompiled source code and an updated executable with documented parameter syntax, but I will also include step-by-step build instructions and notes on the required toolchain necessary for you or anyone on your team to rebuild the project when needed. Your satisfaction is my priority, and I am prepared to go out of my way to ensure it.