How karamzaki/iremoval-gsm works
Project type and purpose
• From the file structure and project names (iRemoval_PRO_v2.2-csvm.sln, Form1.cs) this is a Windows desktop application (WinForms/.NET Framework 4.5.2) named “iRemovalPRO.”
• It embeds a local library called “MobileDevice” which wraps Apple’s MobileDevice/CoreFoundation APIs via P/Invoke, so the app can enumerate, connect to, restore, install apps on iOS devices over USB.
• The README provides no architectural guidance (“you dont got any eula…”), so we rely entirely on the directory layout.
File structure
• Top‑level solution/project files:
• iRemoval_PRO_v2.2-csvm.sln / .csproj – the WinForms front‑end.
• Class2.cs – an orphan helper or legacy class.
• “iRemovalPRO” folder: the WinForms UI project (Form1.cs / Form1.resx).
• “MobileDevice” subfolder (appearing under bin/Debug and under the iRemovalPRO tree): a class library project.
• Callback – delegates & event sinks for device notifications (DFU, install, restore).
• CoreFundation – P/Invoke definitions for CF* types (CFString, CFDictionary, CFURL, PROCESS_INFORMATION, etc.).
• Enumerates – strongly‑typed enums for error codes, device keys, notification types.
• Event – custom EventArgs and delegates for connect/disconnect and error events.
• Helper / Unity – utility classes for converting and mapping enums.
• Struct – marshalled structs for devices, notifications, recovery devices.
• iOSDevice, iOSDeviceManager, iOSRecoveryDevice – higher‑level classes that wrap the P/Invoke + events and expose a .NET API.
• Build output under bin/Debug/net452 and bin/Debug/MobileDevice shows the compiled assemblies and an executable config.