Dump Windev 27 ✨ ✨

WinDev 27 uses a combination of:

A partial reconstruction script (Python):

def simple_decrypt(data, key=0x27):
    dec = bytearray()
    for i, b in enumerate(data):
        dec.append(b ^ ((key + i) & 0xFF))
    return dec

Actual decryption requires reversing WD270.DLL’s DecompressResource export. More reliable: run the app under x64dbg, set breakpoint on VirtualAlloc, and dump the decompressed buffer after the runtime decodes a form.

The syntax is similar to BASIC/Pascal.

Variables:

// Simple types
sName is string = "John"
nAge is int = 30
bActive is boolean = True
rPrice is real = 19.99
// Arrays
arrNames is array of strings
ArrayAdd(arrNames, "Alice")
// Structures
STCustomer is Structure
    Name is string
    ID is int
END

Database Access (HFSQL):

// Declaration
HDeclare("Customer", "Name, ID")
// Reading
HReadFirst(Customer, Name)
WHILE NOT HOut(Customer)
    Trace(Customer.Name)
    HReadNext(Customer, Name)
END
// Query
HExecuteSQLQuery("SELECT * FROM Customer WHERE ID > 10")

UI Controls:

// Setting a value
EDT_Input1 = "Hello World"
// Events (Typically in the "Initialization" or "Click" events of the code editor)
// Example: Button Click
Info("Button Clicked")

HFSQL Data Extraction: Exporting data from .FIC (data), .MMO (memo), and .NDX (index) files. dump windev 27

Memory Dumps: Capturing the state of a running .exe to analyze variables or logic flow.

Resource Extraction: Pulling images, icons, or internal WD libraries from the compiled binary.

WLanguage Analysis: Decompiling or "dumping" the bytecode to understand business logic. 📂 Methods for Dumping WinDev Elements 1. HFSQL Database Dumps If you need to extract data from a WinDev 27 environment:

WDMap: The native tool provided by PC SOFT to view and export .FIC files to CSV or XML.

WDSQL: Allows running SQL queries against local files to "dump" specific datasets.

HExportXML / HExportJSON: Functions within WLanguage used to programmatically dump table contents. 2. Binary & Resource Dumps

WinDev applications pack resources into the executable or external .WDK / .WDL files. WinDev 27 uses a combination of:

WDReader: A common community utility used to browse internal project resources.

Resource Hackers: General-purpose tools can sometimes view the UI structure, though WinDev's internal format is proprietary. 3. Memory & Debug Dumps To analyze a crash or hidden values:

WDDebug: The official debugger can be attached to processes to inspect memory.

Task Manager / ProcDump: Standard Windows tools to create a .DMP file for analysis in WinDbg. ⚠️ Key Considerations Proprietary Format

WinDev uses a highly proprietary compiled format. Unlike .NET (C#) or Java, which decompile into readable code easily, WinDev bytecode is specialized. "Dumping" the source code usually results in p-code that requires specific knowledge to interpret. Encryption

If the project used HFSQL encryption, a simple dump of the files will yield unreadable data. You would need the original .WDD (Analysis file) or the encryption password to make the dump useful. Legal & Ethical Use

Ensure you have the right to dump the software. Reverse engineering compiled WinDev applications often violates the End User License Agreement (EULA) unless it is for interoperability as permitted by local law. To help you more specifically, could you clarify: Actual decryption requires reversing WD270

Are you trying to dump data from a database or source code from a compiled app?

Do you have access to the original project files (.wbp, .wda)?

I can provide more technical steps once I know your exact goal.

Disclaimer: This report is for educational and defensive security purposes only. Dumping proprietary software without permission may violate software licenses (EULA) and intellectual property laws.

The most valuable part of a WinDEV 27 memory dump is the p-code interpreted by the VM. This p-code is what performs the actual business logic (calculations, loops, API calls).

To extract p-code:

No public automated decompiler exists for WinDEV 27 p-code. However, you can map instructions by correlating known WinDEV API calls (e.g., WinDev_LoadTable, HFSQL_ReadFirst) with byte patterns found in memory.